Jira connection
The saved link to a Jira site. In the connection picker it is Jira.
Powers these nodes
Fields
| Field | Required | Description |
|---|---|---|
| Name | Yes | A name for the connection. |
| Site URL | Yes | The Jira site URL, for example https://your-org.atlassian.net. |
| Auth | Yes | How it authenticates—API Token or OAuth 2.0 (3LO). |
API Token
| Field | Required | Description |
|---|---|---|
| Yes | The email address of the Atlassian account that owns the token. | |
| API Token | Yes | A token generated at id.atlassian.com, under Security and then API tokens. Stored encrypted and never logged. |
Prefer a service account over a personal one for anything running in production, so the connection does not break when a person's access changes.
There is no Connect button on this method—fill the fields in and save.
OAuth 2.0 (3LO)
| Field | Required | Description |
|---|---|---|
| Client ID | Yes | The client id of your Atlassian OAuth 2.0 (3LO) app. |
| Client Secret | No | The app's client secret. Stored encrypted and never logged. |
Enter the credentials, save, then click Connect to authorize the app.
Choose OAuth if you want Jira triggers to register their webhooks by themselves: Atlassian limits its dynamic-webhook endpoint to OAuth apps, so an API token connection needs an administrator to set each webhook up by hand. Once connected, a Registered Webhooks tab lists what the app has registered for this connection, with a delete action per row for cleaning up any that outlived their trigger.
An administrator may have to register the OAuth app with Atlassian and hand you its client id and secret before you can fill this in.
The connection's authentication method and site URL cannot be changed while OAuth is connected, or while registered webhooks exist.