> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gradial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting to External Ticketing Systems

> Connect Gradial to Jira, Workfront, Wrike, Asana, or monday.com to automatically ingest tickets, execute work, and sync results back to your workflow.

Once connected, Gradial monitors your ticketing system for matching tickets, executes the requested work, and writes results — previews, links, status updates — back to the original ticket. Your team keeps working in the tools they already use.

***

## Before you begin

You'll need:

* **Admin access** to your Gradial organization
* **Service account credentials** for the target ticketing system — a dedicated integration account, not a personal user
* **Knowledge of which projects or folders** you want to sync into Gradial

***

## Choose your platform

<CardGroup cols={3}>
  <Card title="Jira" icon="atlassian" href="/docs/integrations-administration-and-setup/how-gradial-works-with-ticketing-systems/jira">
    Supports Jira Cloud (Email + API Token or Forge OAuth) and Jira Server / Data Center (PAT).
  </Card>

  <Card title="Workfront" icon="diagram-project" href="/docs/integrations-administration-and-setup/how-gradial-works-with-ticketing-systems/workfront">
    Supports API Key and OAuth 2.0 JWT (Server-to-Server) for Adobe-identity environments.
  </Card>

  <Card title="Wrike" icon="w" href="/docs/integrations-administration-and-setup/how-gradial-works-with-ticketing-systems/Wrike-Integration">
    Connects via Personal Access Token generated from the Wrike service account.
  </Card>

  <Card title="Asana" icon="circle-check" href="/docs/integrations-administration-and-setup/how-gradial-works-with-ticketing-systems/asana">
    Connects via Personal Access Token or OAuth 2.0 from the Asana service account.
  </Card>

  <Card title="monday.com" icon="m" href="/docs/integrations-administration-and-setup/how-gradial-works-with-ticketing-systems/monday">
    Connects via API token generated from a dedicated monday.com service user.
  </Card>

  <Card title="Azure DevOps" icon="microsoft">
    Coming soon. Contact your Gradial team for early access.
  </Card>
</CardGroup>

***

## After connecting

Once a platform is connected, two things need to be configured:

1. **Routes** — define which tickets Gradial ingests, how they're organized, and where they appear in Gradial workspaces. See [Routing Tickets →](/docs/integrations-administration-and-setup/how-gradial-works-with-ticketing-systems/routing-tickets)

2. **Creating tickets from Gradial** — for work that originates in Gradial and needs to be tracked externally. See [Creating Tickets from Gradial →](/docs/integrations-administration-and-setup/how-gradial-works-with-ticketing-systems/creating-tickets-from-gradial)