Skip to main content
atlassian-jira icon

Jira Connector

Sourcenpm · v0.1.0API DocsAPI ChangelogConnector Changelog

Description​

Jira is a proprietary issue tracking product developed by Atlassian that allows bug tracking and agile project management. This component manages issues, comments, projects, and users within Jira.

API Documentation​

This component was built using the Jira Cloud REST API (v3)

Connections​

Basic Authentication​

key: basic

To authenticate with Atlassian Jira using Basic Authentication, an email address and either an API token (for Jira Cloud) or password (for self-hosted Jira) is required.

Prerequisites​

  • Access to a Jira Cloud or self-hosted Jira instance
  • Administrative permissions to generate API tokens (for Jira Cloud)

Setup Steps​

For Jira Cloud:

  1. Navigate to Atlassian Account API Tokens
  2. Click Create API token
  3. Enter a label for the token and click Create
  4. Copy the generated API token value

For Self-Hosted Jira:

Use the standard account password for authentication. No additional setup is required.

Configure the Connection​

  • For Username, enter the email address associated with the Jira account
  • For API Key:
    • Jira Cloud: Enter the API token generated in the previous step
    • Self-Hosted Jira: Enter the account password
  • For Host, enter the Jira instance URL (e.g., example.atlassian.net for cloud or the self-hosted domain)
  • For Version, select the API version (typically 3 for Jira Cloud, 2 for older instances)

For more information on generating API tokens from Jira Cloud, refer to the Atlassian documentation.

InputNotesExample
Host

The hostname of the Jira instance (without https://).

your-company.atlassian.net
API Key

The Jira API token used for authentication. Cloud users must generate an API token from Atlassian Account Settings.

ATATT3xFfGF0T8gK8Example1234567890abcdefGHIJKLMNOP
Username

The Jira username or email address used for authentication.

john.doe@example.com
Version

Select the Jira API version to use for requests.

3

OAuth 2.0 Client Credentials​

key: jiraOauth2ClientCredentials

To authenticate with Atlassian Jira using OAuth 2.0 Client Credentials, an OAuth 2.0 integration must be configured in the Atlassian Admin Hub. This connection type enables service account (machine-to-machine) access without requiring user interaction.

For more information on OAuth 2.0 Client Credentials for Jira, refer to Atlassian's documentation on creating OAuth 2.0 credentials for service accounts.

Prerequisites​

  • Access to the Atlassian Admin Hub with organization administrator permissions
  • A Jira Cloud site associated with the organization

Setup Steps​

  1. Navigate to the Atlassian Admin Hub
  2. Select the organization that contains the Jira site
  3. Navigate to Directory > Service accounts
  4. Select an existing service account, or create a new one
  5. Click Create credentials and select OAuth 2.0
  6. Enter a name for the credential
  7. Configure the required scopes:
    • For basic issue management, the following scopes are recommended: 
      read:jira-user read:jira-work write:jira-work manage:jira-project manage:jira-configuration manage:jira-webhook
    • Refer to Jira OAuth 2.0 scopes documentation for a complete list of available scopes
  8. Click Create to generate the credential
  9. Copy the Client ID and Client Secret values (the secret is only shown once)
  10. Obtain the Cloud ID for the Jira site by following the Atlassian Cloud ID retrieval guide

Configure the Connection​

  • Enter the Client ID from the OAuth 2.0 credential

  • Enter the Client Secret from the OAuth 2.0 credential

  • Enter the Cloud ID of the Jira site to connect to

  • For Scopes, use the following default value:

    read:jira-user read:jira-work write:jira-work manage:jira-project manage:jira-configuration manage:jira-webhook
    • Ensure the scopes match those configured in the Atlassian Admin Hub credential
    • Refer to Jira scopes documentation for additional scope information

  • For Version, select the API version (typically 3 for Jira Cloud)

InputNotesExample
Client ID

The OAuth 2.0 Client ID generated when creating the credential in Atlassian Admin Hub.

c9e4APadFFkbtTycoNtrHKBtYgUyZWy
Client Secret

The OAuth 2.0 Client Secret generated when creating the credential in Atlassian Admin Hub.

ntDBx4ao5czkFu7Mzp5FTlYG0y3_ukxkSiPhwnTkhsdKHJITGRCGP3ZWlXTYyu
Cloud ID

The Cloud ID of the Jira site. See How to Find Your Cloud ID for instructions.

a1b2c3d4-e5f6-7890-abcd-ef1234567890
Scopes

Space-delimited list of OAuth scopes for Jira access. These must match the scopes configured when creating the OAuth 2.0 credential in Admin Hub. For more information, see Jira OAuth 2.0 Scopes.

read:jira-user read:jira-work write:jira-work manage:jira-project manage:jira-configuration manage:jira-webhook
Token URL

The OAuth 2.0 Token URL for Jira.

https://auth.atlassian.com/oauth/token
Version

Select the Jira API version to use for requests.

3

OAuth 2.0​

key: oauth2

To create an Atlassian Jira OAuth 2.0 connection, an OAuth 2.0 integration must be configured in the Atlassian Developer Console.

Jira's Cloud API supports OAuth 2.0 (3LO) flows for secure authentication. For more information on OAuth 2.0 (3LO) apps, refer to Jira's OAuth 2.0 documentation.

Prerequisites​

Setup Steps​

  1. Navigate to the Atlassian Developer Console
  2. Click Create and select OAuth 2.0 integration
  3. Enter a name for the integration
  4. After creation, locate the App details section and copy the Client ID and Client Secret values
  5. Under the Authorization section, click Configure next to OAuth 2.0 (3LO)
  6. Enter the callback URL: https://oauth2.prismatic.io/callback
  7. Navigate to the Permissions tab
  8. Add the required scopes based on the use case:
    • For basic issue management, the following scopes are recommended: 
      read:jira-user read:jira-work write:jira-work manage:jira-project manage:jira-configuration manage:jira-webhook offline_access
    • Refer to Jira OAuth 2.0 scopes documentation for a complete list of available scopes
  9. Click Save to apply the configuration

Configure the Connection​

  • For Authorize URL and Token URL, keep the pre-populated defaults (https://auth.atlassian.com/authorize?audience=api.atlassian.com&prompt=consent and https://auth.atlassian.com/oauth/token) unless instructed otherwise by Atlassian

  • Enter the Client ID from the Atlassian Developer Console

  • Enter the Client Secret from the Atlassian Developer Console

  • For Scopes, use the following default value:

    read:jira-user read:jira-work write:jira-work manage:jira-project manage:jira-configuration manage:jira-webhook offline_access
    • The offline_access scope is required to obtain a refresh token
    • Customize the scopes to match the use case requirements
    • Ensure the scopes match those configured in the Atlassian Developer Console. Mismatched scopes cause authentication failures.
    • Refer to Jira scopes documentation for additional scope information

  • For Atlassian Site Name (optional):

    • By default, the connection uses the first Jira site the authenticated user has access to
    • To specify a different site, enter the site name (e.g., example) or full URL (e.g., example.atlassian.net)

  • For Version, select the API version (typically 3 for Jira Cloud)

For additional information on developing Jira applications and OAuth 2.0 configuration, refer to the Jira OAuth 2.0 apps guide.

InputNotesExample
Atlassian Site Name

Optional site name or URL to connect to. By default, connects to the first Jira site the user has access to. Use this if multiple Jira sites are available.

your-company.atlassian.net
Authorize URL

The OAuth 2.0 Authorization URL for Jira.

https://auth.atlassian.com/authorize?audience=api.atlassian.com&prompt=consent
Client ID

The OAuth 2.0 Client ID from the Atlassian Developer Console.

c9e4APadFFkbtTycoNtrHKBtYgUyZWy
Client Secret

The OAuth 2.0 Client Secret from the Atlassian Developer Console.

ntDBx4ao5czkFu7Mzp5FTlYG0y3_ukxkSiPhwnTkhsdKHJITGRCGP3ZWlXTYyu
Scopes

Space-delimited list of OAuth scopes for Jira access. For more information, see Jira OAuth 2.0 Scopes.

read:jira-user read:jira-work write:jira-work manage:jira-project manage:jira-configuration manage:jira-webhook offline_access
Token URL

The OAuth 2.0 Token URL for Jira.

https://auth.atlassian.com/oauth/token
Version

Select the Jira API version to use for requests.

3

Triggers​

Issue Events​

Receive real-time notifications when Jira issues are created, updated, or deleted. Automatically creates and manages a webhook subscription for selected issue events when the instance is deployed, and removes the subscription when the instance is deleted. | key: issueEventsTrigger

InputNotesExample
Event Types

One or more Jira issue events that will trigger this webhook.

jira:issue_created
Field IDs Filter

An optional list of field IDs to monitor. Only changes to these specific fields will trigger the webhook. Leave empty to monitor all field changes.

summary
Connection

The Jira connection to use.

JQL Filter

JQL (Jira Query Language) filter to limit which issues trigger the webhook. For more information, see JQL Documentation.

project = PROJ AND status = Done

The Issue Events trigger manages Jira webhook subscriptions for an instance. This trigger handles the entire webhook lifecycle automatically.

How It Works​

When the trigger is used in a flow:

  • On Instance Deploy: The trigger automatically creates a webhook subscription in Jira for the selected issue events (issue creation, updates, deletions, etc.). The webhook target URL is set to the instance's unique webhook URL. For OAuth connections, the webhook is registered with an expiration date and is automatically refreshed by the trigger. For Basic Auth connections, the webhook persists indefinitely.
  • On Instance Deletion: The trigger automatically removes the webhook subscription from Jira to ensure no orphaned webhook configurations remain after instance cleanup.

Authentication Methods​

This trigger supports both OAuth 2.0 and Basic Authentication, with different webhook registration behaviors:

OAuth 2.0:

  • Webhooks expire after 30 days and require periodic refresh
  • On each invocation, the trigger refreshes the webhook when fewer than 7 days remain before it expires
  • Webhook payload structure uses the Dynamic Webhooks format
  • Requires OAuth connection with appropriate scopes

Basic Authentication:

  • Webhooks persist indefinitely without expiration
  • No automatic refresh required
  • Webhook payload structure uses the Classic Webhooks format
  • Requires Basic Auth connection with API token

Configuration Requirements​

This trigger requires a Jira connection configured in the Atlassian Jira component. The connection can be either:

  • OAuth 2.0 - Requires Client ID, Client Secret, and appropriate OAuth scopes for the events being subscribed to
  • Basic Auth - Requires Jira site URL, email address, and API token

Event Types​

When configuring the trigger, select which Jira issue events should trigger the flow.

Available Events (8)
EventDescription
jira:issue_createdTriggered when a new issue is created
jira:issue_updatedTriggered when an issue is modified
jira:issue_deletedTriggered when an issue is deleted
issue_property_setTriggered when an issue property is set or updated
issue_property_deletedTriggered when an issue property is deleted
comment_createdTriggered when a comment is added to an issue
comment_updatedTriggered when a comment is modified
comment_deletedTriggered when a comment is removed

A full list of available webhook events is available in the Jira Webhooks documentation.

Filtering Options​

The trigger provides powerful filtering capabilities to limit which issues trigger the flow:

JQL Filter (Required): Filter issues using Jira Query Language (JQL). This allows precise control over which issues trigger webhooks.

Examples:

  • project = PROJ - Only issues in the PROJ project
  • project IN (PROJ, TEST) AND status = Done - Issues in specific projects with Done status
  • assignee = currentUser() AND priority = High - High priority issues assigned to the current user

Field IDs Filter (Optional, OAuth only): Specify field IDs to monitor for changes. When provided, the webhook only triggers when those specific fields are updated. This is particularly useful for jira:issue_updated events.

Examples:

  • summary, description - Only trigger when summary or description changes
  • customfield_10029 - Only trigger when a specific custom field changes

Leave empty to trigger on any field change.

Returned Data​

The trigger returns the complete webhook payload from Jira, which varies based on the event type. All payloads include:

Common Properties:

  • webhookEvent - The event type that triggered the webhook
  • issue - Complete issue object with fields, status, priority, assignee, etc.
  • user - User who performed the action
  • changelog - For update events, lists what changed (old value, new value, field name)
Example payload for jira:issue_created event
{
  "webhookEvent": "jira:issue_created",
  "issue": {
    "id": "10001",
    "key": "PROJ-123",
    "self": "https://your-domain.atlassian.net/rest/api/3/issue/10001",
    "fields": {
      "summary": "New issue summary",
      "description": {
        "type": "doc",
        "version": 1,
        "content": [
          {
            "type": "paragraph",
            "content": [
              {
                "type": "text",
                "text": "Issue description"
              }
            ]
          }
        ]
      },
      "status": {
        "name": "To Do",
        "id": "10000"
      },
      "priority": {
        "name": "Medium",
        "id": "3"
      },
      "assignee": {
        "accountId": "5b10a2844c20165700ede21g",
        "displayName": "John Smith",
        "emailAddress": "john@example.com"
      },
      "project": {
        "id": "10000",
        "key": "PROJ",
        "name": "Example Project"
      },
      "issuetype": {
        "id": "10001",
        "name": "Task"
      },
      "created": "2024-11-10T10:30:00.000+0000",
      "updated": "2024-11-10T10:30:00.000+0000"
    }
  },
  "user": {
    "accountId": "5b10a2844c20165700ede21g",
    "displayName": "John Smith",
    "emailAddress": "john@example.com"
  },
  "timestamp": 1699614600000
}
Example payload for jira:issue_updated event
{
  "webhookEvent": "jira:issue_updated",
  "issue": {
    "id": "10001",
    "key": "PROJ-123",
    "fields": {
      "summary": "Updated issue summary",
      "status": {
        "name": "In Progress",
        "id": "10001"
      }
    }
  },
  "user": {
    "accountId": "5b10a2844c20165700ede21g",
    "displayName": "John Smith"
  },
  "changelog": {
    "items": [
      {
        "field": "status",
        "fieldtype": "jira",
        "from": "10000",
        "fromString": "To Do",
        "to": "10001",
        "toString": "In Progress"
      }
    ]
  },
  "timestamp": 1699614700000
}
Example Payload for Issue Events⤓
Loading…

New and Updated Issues​

Retrieves existing and ongoing issues from Jira. Load history once, check for changes on a schedule, or both. | key: pollChangesTrigger

InputNotesExample
Connection

The Jira connection to use.

Look-back Date

The date the initial sync starts from, in YYYY-MM-DD format. Cannot be a future date. Leave empty to start from the first recurrence with no backfill. When set, the initial sync seeds each issue created or updated on or after this date once, ignoring the visibility filters.

2026-01-01
Additional JQL Filter

Optional JQL clause appended (with AND) to the built-in updated >= last-poll filter. Use to narrow results by project, type, assignee, etc.

project = PROJ AND issuetype = Bug
Show New Issues

When true, includes issues created since the last poll in the trigger output.

true
Show Updated Issues

When true, includes issues updated since the last poll in the trigger output.

true

The New and Updated Issues polling trigger checks Jira on a configured schedule for issues that were created or modified since the last poll. Unlike webhook-based triggers, polling does not require webhook subscription management and works reliably for low-frequency monitoring scenarios.

How It Works​

On each scheduled execution, the trigger:

  1. Reads lastPolledAt and nextPageToken from the polling state. With no stored position and no Look-back Date, it starts from the current time. A stored nextPageToken is resumed only for the Additional JQL Filter it was issued for; after the filter changes, the trigger restarts from the stored last-poll timestamp.
  2. Queries Jira's /rest/api/3/search/jql endpoint for issues matching updated >= <lastPolledAt>, optionally narrowed by the Additional JQL Filter. It reads up to ten pages of 100 issues per recurrence with batching off, or one page per round with batching enabled, and stops earlier if the results end. Stopping at the limit is not an error: the nextPageToken it stops on is a complete resume point. With batching off the remaining pages arrive on later recurrences; with batching on the platform re-invokes the trigger from that token until the results end, within the same recurrence.
  3. Partitions the returned issues into created and updated buckets by comparing the issue's created timestamp against the last poll timestamp
  4. Persists the nextPageToken on every recurrence. It advances the last-poll timestamp only once the results end, because that value is the cutoff step 3 compares against, and moving it while pages are still outstanding would place it ahead of issues that have not been delivered yet. It then sets it to the time the first recurrence of that drain started, not the last: Jira cursor paging is not a snapshot, so a later time could skip issues updated while the drain was in progress. An issue updated during a multi-recurrence drain is therefore picked up again by the next drain, possibly as a duplicate updated issue.
  5. Emits the partitioned results in the trigger payload, filtered by the Show New Issues and Show Updated Issues toggles

If both Show New Issues and Show Updated Issues are disabled, the trigger skips the API call entirely, unless an initial sync is running.

Initial sync

An initial sync seeds a complete starting state, so inputs that narrow the change feed would leave gaps in it and are ignored for its duration, while inputs that shape how issues are fetched still apply. Set a Look-back Date to start one: it begins on the first recurrence, seeds each issue created or updated on or after that date exactly once, and ignores Show New Issues and Show Updated Issues. The Connection and Additional JQL Filter apply throughout.

The window has no fixed upper bound, so an issue updated while the sync is still draining is swept into the sync rather than left for the incremental recurrences. The trigger's position is the nextPageToken Jira issues and advances page by page; when the results end, the trigger commits the time the sync began as its last-poll timestamp, and every later recurrence resumes from exactly there. No field in the payload marks the handoff. With batching off the sync drains up to ten pages per scheduled recurrence and a large project therefore spans several of them; with batching on the platform drives the rounds and the sync drains inside one recurrence.

Batching

Batching is enabled per flow on this trigger: each changed record is dispatched as its own execution, or grouped by the configured batch size. Batch size and batch concurrency can both be overridden per instance. Raising concurrency increases the request volume sent to Jira.

To turn it on, select the flow's trigger, open the Flow control tab, and switch on Enable Batching. Under Batch Size, keep Trigger default or choose Custom batch size. Batch Concurrency is optional; leave it blank for no batch-level limit.

With batching off, a downstream step reads the arrays at body.data.created and body.data.updated. With batching on those fields do not exist: each execution receives one issue, or an array of them at a batch size above one, as { "changeType": "created" | "updated", "record": { ... } }. Any step reading the older shape must be updated before batching is enabled. Because batching is enabled per flow, the change is scoped to that flow and leaves other flows using this trigger untouched.

Returned Data​

With batching off, the trigger emits a payload with two arrays (created and updated), each containing issue resources from the Jira REST API.

Example Payload
{
  "data": {
    "created": [
      {
        "id": "10001",
        "key": "PROJ-123",
        "self": "https://example.atlassian.net/rest/api/3/issue/10001",
        "fields": {
          "summary": "New issue summary",
          "status": { "name": "To Do", "id": "10000" },
          "priority": { "name": "Medium", "id": "3" },
          "created": "2026-05-21T10:30:00.000+0000",
          "updated": "2026-05-21T10:30:00.000+0000"
        }
      }
    ],
    "updated": [
      {
        "id": "10002",
        "key": "PROJ-124",
        "fields": {
          "summary": "Existing issue summary",
          "status": { "name": "In Progress", "id": "10001" },
          "created": "2026-05-15T08:00:00.000+0000",
          "updated": "2026-05-21T11:05:00.000+0000"
        }
      }
    ]
  }
}

With batching on, each execution receives one tagged item instead, or an array of them when the batch size is above one.

Example Batched Item
{
  "changeType": "created",
  "record": {
    "id": "10001",
    "key": "PROJ-123",
    "fields": {
      "summary": "New issue summary",
      "status": { "name": "To Do", "id": "10000" },
      "created": "2026-05-21T10:30:00.000+0000",
      "updated": "2026-05-21T10:30:00.000+0000"
    }
  }
}

Fields shown are representative. The full response object includes additional properties.

When to Use Polling vs. Webhooks​

  • Use polling when the integration needs to run on a fixed schedule, when webhook subscription management is not desired, or when the volume of changes is low enough that polling latency is acceptable.
  • Use the Issue Events webhook trigger when near real-time delivery is required and the integration can manage subscription lifecycles.

Refer to the Jira REST API issue resource for the complete schema of returned issue fields.

Example Payload for New and Updated Issues⤓
Loading…

Data Sources​

Select Board​

Select a board. | key: selectBoard | type: picklist

InputNotesExample
Filter

The scope used to limit returned dashboards. Common values are my (dashboards owned by the current user) and favourite (dashboards starred by the current user).

my
Connection

The Jira connection to use.

Max Results

The maximum number of results to return per page.

50
Start At

The index of the first item to return in the result set (0-based).

0
Example Payload for Select Board⤓
Loading…

Select Board Version​

Select a board version. | key: selectBoardVersion | type: picklist

InputNotesExample
Board ID

The unique identifier of the Jira board.

10201
Connection

The Jira connection to use.

Max Results

The maximum number of results to return per page.

50
Start At

The index of the first item to return in the result set (0-based).

0
Example Payload for Select Board Version⤓
Loading…

Select Issue by Project​

Select an issue from the specified project. | key: selectIssue | type: picklist

InputNotesExample
Connection

The Jira connection to use.

Project ID

The unique identifier or name of the Jira project.

10201
Example Payload for Select Issue by Project⤓
Loading…

Select Issue Field​

Select an issue field from the available Jira issue fields. | key: issueFields | type: picklist

InputNotesExample
Connection

The Jira connection to use.

Only Custom Fields

When true, returns only custom fields; when false, returns all issue fields.

false
Example Payload for Select Issue Field⤓
Loading…

Select Issue Type from Project​

Select an issue type from the specified project. | key: selectIssueTypeFromProject | type: picklist

InputNotesExample
Connection

The Jira connection to use.

Project ID

The unique identifier or name of the Jira project.

10201
Issue Type Return

When true, returns the Issue Type Name; when false, returns the Issue Type ID. Defaults to ID.

false
Example Payload for Select Issue Type from Project⤓
Loading…

Select Issue Type from Projects​

Select an issue type from the specified projects. | key: selectIssueType | type: picklist

InputNotesExample
Connection

The Jira connection to use.

Project ID(s)

One or more Jira project IDs whose issue types populate the dropdown. Accepts a single ID or a selection of projects.

10201
Issue Type Return

When true, returns the Issue Type Name; when false, returns the Issue Type ID. Defaults to ID.

false
Example Payload for Select Issue Type from Projects⤓
Loading…

Select Issue Types from Projects​

Select one or many issue types from the specified projects. | key: selectIssueTypes | type: objectSelection

InputNotesExample
Connection

The Jira connection to use.

Project ID(s)

One or more Jira project IDs whose issue types populate the dropdown. Accepts a single ID or a selection of projects.

10201
Example Payload for Select Issue Types from Projects⤓
Loading…

Select Priority​

Select a priority. | key: selectPriority | type: picklist

InputNotesExample
Connection

The Jira connection to use.

Example Payload for Select Priority⤓
Loading…

Select Project​

Select a project. | key: selectProject | type: picklist

InputNotesExample
Connection

The Jira connection to use.

Example Payload for Select Project⤓
Loading…

Select Projects​

Select one or many projects. | key: selectProjects | type: objectSelection

InputNotesExample
Connection

The Jira connection to use.

Example Payload for Select Projects⤓
Loading…

Select Version​

Select a version from the specified project. | key: selectVersion | type: picklist

InputNotesExample
Connection

The Jira connection to use.

Project ID

The unique identifier or name of the Jira project.

10201
Example Payload for Select Version⤓
Loading…

Select Webhook​

Select a webhook. | key: selectWebhook | type: picklist

InputNotesExample
Connection

The Jira connection to use.

Example Payload for Select Webhook⤓
Loading…

Actions​

Add Comment​

Add a comment to an existing issue. | key: addComment

InputNotesExample
Comment

The plain-text body of the comment.

This is an example comment.
Dynamic Fields

Dynamic field key/value pairs supplied as JSON. Use a key/value config variable to configure these at deploy time. Each item must contain a key and a value.

[
  {
    "key": "name",
    "value": "Example Name"
  },
  {
    "key": "projectId",
    "value": "Example projectId"
  }
]
Values

Additional field names and their values to include when creating or updating the record. Each row is merged into the request payload.

projectId=1000,name=Example
Issue ID

The unique identifier of the Jira issue.

10201
Connection

The Jira connection to use.

Example Payload for Add Comment⤓
Loading…

Add Issue Attachment​

Add a file attachment to an issue. | key: addIssueAttachment

InputNotesExample
File

The file to upload - either string contents or a binary file

File Name

The file name, including extension, shown on the attachment in Jira.

report.pdf
Issue ID

The unique identifier of the Jira issue.

10201
Connection

The Jira connection to use.

Example Payload for Add Issue Attachment⤓
Loading…

Create Issue​

Create an issue within a given project. | key: createIssue

InputNotesExample
Additional Fields

Additional optional fields: includes Due Date, Versions, and Fix Versions.

ADF Description

The Atlassian Document Format (ADF) JSON representation of the issue description. Provide this OR Description — not both. Use the ADF playground to generate the JSON.

{
  "version": 1,
  "type": "doc",
  "content": [
    {
      "type": "paragraph",
      "content": [
        {
          "type": "text",
          "text": "Some text"
        }
      ]
    }
  ]
}
Assignee Account ID

The Atlassian account ID of the user to assign the issue to.

5b10a2844c20165700ede21g
Description

A detailed description of the issue.

The login button does not respond on mobile devices in portrait mode.
Dynamic Fields

Dynamic field key/value pairs supplied as JSON. Use a key/value config variable to configure these at deploy time. Each item must contain a key and a value.

[
  {
    "key": "name",
    "value": "Example Name"
  },
  {
    "key": "projectId",
    "value": "Example projectId"
  }
]
Values

Additional field names and their values to include when creating or updating the record. Each row is merged into the request payload.

projectId=1000,name=Example
Issue Type Name

The name of the issue type. Provide this OR Issue Type ID; one is required, not both.

Task
Issue Type ID

The ID of the issue type. Provide this OR Issue Type Name; one is required, not both.

10001
Connection

The Jira connection to use.

Labels

A list of labels to attach to the issue. Each label must not contain spaces.

performance
Priority

The ID of the priority to assign to the issue. Choose from the dropdown or enter a priority ID.

3
Project ID

The unique identifier or name of the Jira project.

10201
Reporter Account ID

The Atlassian account ID of the user reporting the issue.

5b10a2844c20165700ede21g
Summary

A short one-line title for the issue, shown in lists and search results.

Fix login page responsiveness
Example Payload for Create Issue⤓
Loading…

Create User​

Create a new user record. | key: createUser

InputNotesExample
Display Name

The full name shown for the user across Jira, such as in assignee and reporter fields.

John Doe
Dynamic Fields

Dynamic field key/value pairs supplied as JSON. Use a key/value config variable to configure these at deploy time. Each item must contain a key and a value.

[
  {
    "key": "name",
    "value": "Example Name"
  },
  {
    "key": "projectId",
    "value": "Example projectId"
  }
]
Email Address

The email address of the user.

someone@example.com
Values

Additional field names and their values to include when creating or updating the record. Each row is merged into the request payload.

projectId=1000,name=Example
Connection

The Jira connection to use.

Notifications

When true, the user will receive email notifications for relevant events.

false
Password

The password to assign to the new user account.

Username

The username for the Jira user account.

john.doe
Example Payload for Create User⤓
Loading…

Create Version​

Create a new version. | key: createVersion

InputNotesExample
Description

A short summary of what the version delivers, shown on the release page.

The login button does not respond on mobile devices in portrait mode.
Dynamic Fields

Dynamic field key/value pairs supplied as JSON. Use a key/value config variable to configure these at deploy time. Each item must contain a key and a value.

[
  {
    "key": "name",
    "value": "Example Name"
  },
  {
    "key": "projectId",
    "value": "Example projectId"
  }
]
Values

Additional field names and their values to include when creating or updating the record. Each row is merged into the request payload.

projectId=1000,name=Example
Connection

The Jira connection to use.

Project ID

The unique identifier or name of the Jira project.

10201
Project Key

The project key identifier (e.g., PROJ, ENG, SALES).

PROJ
Release Details

Status flags and schedule dates.

Version Name

The display name of the version (e.g., a release tag or date).

2019.08.18
Example Payload for Create Version⤓
Loading…

Create Webhook​

Create a webhook to send data from Jira to an instance URL. | key: createWebhook

InputNotesExample
Connection

The Jira connection to use.

Webhook Details

The webhook details payload sent to Jira's OAuth2 Webhook API or REST API. Must match the structure of the webhooks property described in the Register Dynamic Webhook endpoint.

[
  {
    "events": [
      "jira:issue_created",
      "jira:issue_updated"
    ],
    "fieldIdsFilter": [
      "summary",
      "customfield_10029"
    ],
    "jqlFilter": "project = PROJ"
  },
  {
    "events": [
      "jira:issue_deleted"
    ],
    "jqlFilter": "project IN (PROJ, EXP) AND status = done"
  },
  {
    "events": [
      "issue_property_set"
    ],
    "issuePropertyKeysFilter": [
      "my-issue-property-key"
    ],
    "jqlFilter": "project = PROJ"
  }
]
Webhook URL

The URL that Jira will POST webhook events to. Typically reference a flow's URL from the trigger payload.

https://hooks.example.com/trigger/abc123

Registering a Dynamic Webhook requires supplying a highly configurable payload called "Webhook Details". It's important to configure this for all use cases as each Jira app is only permitted to create and manage one endpoint.

Registering a Webhook Notes​

Please note that whenever trying to register a webhook, the request payload's structure is different depending on the authentication method:

{
  "name": "my first webhook via rest",
  "description": "description of my first webhook",
  "events": ["jira:issue_created", "jira:issue_updated"],
  "filters": {
    "issue-related-events-section": "Project = JRA AND resolution = Fixed"
  },
  "excludeBody": false,
  "secret": "G8j4166a5OkXRD4WbqV3"
}
[
  {
    "events": ["jira:issue_created", "jira:issue_updated"],
    "fieldIdsFilter": ["summary", "customfield_10029"],
    "jqlFilter": "project = PROJ"
  },
  {
    "events": ["jira:issue_deleted"],
    "jqlFilter": "project IN (PROJ, EXP) AND status = done"
  },
  {
    "events": ["issue_property_set"],
    "issuePropertyKeysFilter": ["my-issue-property-key"],
    "jqlFilter": "project = PROJ"
  }
]
Example Payload for Create Webhook⤓
Loading…

Delete Comment​

Delete a comment from an issue. | key: deleteComment

InputNotesExample
Comment ID

The unique identifier of the comment.

10201
Issue ID

The unique identifier of the Jira issue.

10201
Connection

The Jira connection to use.

Example Payload for Delete Comment⤓
Loading…

Delete Issue​

Delete an issue by ID. | key: deleteIssue

InputNotesExample
Issue ID

The unique identifier of the Jira issue.

10201
Connection

The Jira connection to use.

Example Payload for Delete Issue⤓
Loading…

Delete Webhook​

Delete a webhook by ID. | key: deleteWebhook

InputNotesExample
Connection

The Jira connection to use.

Webhook ID

The unique identifier of the webhook.

10001
Example Payload for Delete Webhook⤓
Loading…

Download Issue Attachments​

Download the attachment data connected to an issue. | key: downloadAttachment

InputNotesExample
Attachment IDs

A JSON array of attachments to download, each with an id and mimeType. When provided, the Issue ID input is ignored.

[
  {
    "id": "10201",
    "mimeType": "image/png"
  },
  {
    "id": "10201",
    "mimeType": "image/pdf"
  }
]
Issue ID

Providing an Issue ID will return all attachments of an Issue.

10201
Connection

The Jira connection to use.

Example Payload for Download Issue Attachments⤓
Loading…

Find Issue​

Find an issue by attribute. | key: findIssue

InputNotesExample
Fields

A comma-separated list of fields to include in each returned issue. Defaults to common navigable fields (summary, status, assignee, reporter, priority, issuetype, project, created, updated). Use *all to return every field.

summary,status,assignee,priority
Connection

The Jira connection to use.

Search Type

The field to match against: Number (issue key or ID) or Summary (text match).

Search Value

The text to look for. Matching ignores case and surrounding whitespace.

Example Payload for Find Issue⤓
Loading…

Find Project​

Find a project by attribute. | key: findProject

InputNotesExample
Connection

The Jira connection to use.

Search Type

The project field to match against: Name or Key.

Search Value

The text to look for. Matching ignores case and surrounding whitespace.

Example Payload for Find Project⤓
Loading…

Find User​

Find a user by attribute. | key: findUser

InputNotesExample
Connection

The Jira connection to use.

Search Value

The text to look for. Matching ignores case and surrounding whitespace.

Example Payload for Find User⤓
Loading…

Get Board​

Get the information and metadata of a board by ID. | key: getBoard

InputNotesExample
Board ID

The unique identifier of the Jira board.

10201
Connection

The Jira connection to use.

Example Payload for Get Board⤓
Loading…

Get Comments​

Get all comments on a given issue. | key: getComments

InputNotesExample
Issue ID

The unique identifier of the Jira issue.

10201
Connection

The Jira connection to use.

Example Payload for Get Comments⤓
Loading…

Get Current User​

Get the information and metadata of the current user. | key: getCurrentUser

InputNotesExample
Connection

The Jira connection to use.

Example Payload for Get Current User⤓
Loading…

Get Issue​

Get the information and metadata of an issue. | key: getIssue

InputNotesExample
Issue ID

The unique identifier of the Jira issue.

10201
Connection

The Jira connection to use.

Example Payload for Get Issue⤓
Loading…

Get Project​

Get the information and metadata of a project. | key: getProject

InputNotesExample
Connection

The Jira connection to use.

Project ID

The unique identifier or name of the Jira project.

10201
Example Payload for Get Project⤓
Loading…

Get Status List​

Return a list of statuses for a project. | key: getStatusList

InputNotesExample
Connection

The Jira connection to use.

Pagination

Page and page-size controls.

Project ID

The unique identifier or name of the Jira project.

10201
Example Payload for Get Status List⤓
Loading…

Get User​

Get the information and metadata of a user by ID. | key: getUser

InputNotesExample
Account ID

The unique Atlassian account ID of the user.

5b10a2844c20165700ede21g
Expand

A comma-separated list of additional fields to include in the response. Values come from the _expandable property of the resource.

body, version, history
Connection

The Jira connection to use.

Example Payload for Get User⤓
Loading…

Get Version​

Get the information and metadata of an existing version. | key: getVersion

InputNotesExample
Connection

The Jira connection to use.

Version ID

The unique identifier of the version.

10201
Example Payload for Get Version⤓
Loading…

List Assignable Users for Project​

Return a list of users assignable to the given project. | key: listAssignableUsers

InputNotesExample
Connection

The Jira connection to use.

Pagination

Page and page-size controls.

Project Key

The project key identifier (e.g., PROJ, ENG, SALES).

PROJ
Example Payload for List Assignable Users for Project⤓
Loading…

List Board Sprints​

List all sprints within a board. | key: listBoardsSprints

InputNotesExample
Board ID

The unique identifier of the Jira board.

10201
Connection

The Jira connection to use.

Pagination

Page and page-size controls.

Example Payload for List Board Sprints⤓
Loading…

List Boards​

Retrieve a list of existing boards. | key: listBoards

InputNotesExample
Filter

The scope used to limit returned dashboards. Common values are my (dashboards owned by the current user) and favourite (dashboards starred by the current user).

my
Connection

The Jira connection to use.

Pagination

Page and page-size controls.

Example Payload for List Boards⤓
Loading…

List Issue Attachments​

Return a list of attachments for a given issue. | key: listIssueAttachments

InputNotesExample
Issue ID

The unique identifier of the Jira issue.

10201
Connection

The Jira connection to use.

Example Payload for List Issue Attachments⤓
Loading…

List Issue Custom Fields​

List all configured custom issue fields. | key: listIssueCustomFields

InputNotesExample
Connection

The Jira connection to use.

Example Payload for List Issue Custom Fields⤓
Loading…

List Issue Fields​

List all non-custom issue fields. | key: listIssueFields

InputNotesExample
Connection

The Jira connection to use.

Example Payload for List Issue Fields⤓
Loading…

List Issue Link Types​

List all available issue link types. | key: listIssueLinkTypes

InputNotesExample
Connection

The Jira connection to use.

Example Payload for List Issue Link Types⤓
Loading…

List Issue Transitions​

Return a list of available transitions for an issue. | key: listIssueTransitions

InputNotesExample
Issue ID

The unique identifier of the Jira issue.

10201
Connection

The Jira connection to use.

Example Payload for List Issue Transitions⤓
Loading…

List Issue Types​

Return a list of issue types. | key: listIssueTypes

InputNotesExample
Connection

The Jira connection to use.

Example Payload for List Issue Types⤓
Loading…

List Issue Worklogs​

Return a list of worklogs for an issue. | key: listIssueWorklogs

InputNotesExample
Issue ID

The unique identifier of the Jira issue.

10201
Connection

The Jira connection to use.

Example Payload for List Issue Worklogs⤓
Loading…

List Issues by Project​

Return a list of issues for a specific project. | key: listIssues

InputNotesExample
Fields

A comma-separated list of fields to include in each returned issue. Defaults to common navigable fields (summary, status, assignee, reporter, priority, issuetype, project, created, updated). Use *all to return every field.

summary,status,assignee,priority
Connection

The Jira connection to use.

Pagination

Cursor and page-size controls for paging through results.

Project ID

The unique identifier or name of the Jira project.

10201
Example Payload for List Issues by Project⤓
Loading…

List Priorities​

Return a list of all priorities. | key: listPriorities

InputNotesExample
Connection

The Jira connection to use.

Pagination

Page and page-size controls.

Example Payload for List Priorities⤓
Loading…

List Projects​

Retrieve a list of all projects. | key: listProjects

InputNotesExample
Connection

The Jira connection to use.

Pagination

Page and page-size controls.

Example Payload for List Projects⤓
Loading…

List Versions​

Return a list of all versions for a project. | key: listVersions

InputNotesExample
Connection

The Jira connection to use.

Pagination

Page and page-size controls.

Project ID

The unique identifier or name of the Jira project.

10201
Example Payload for List Versions⤓
Loading…

List Webhooks​

List all configured webhooks, including those for other integrations. | key: listWebhooks

InputNotesExample
Fetch All

When true, automatically fetches all pages of results using pagination.

false
Connection

The Jira connection to use.

Example Payload for List Webhooks⤓
Loading…

Query​

Search the entire Jira site using a JQL query. | key: queryV3

InputNotesExample
Expand

A comma-separated list of additional fields to include in the response. Values come from the _expandable property of the resource.

body, version, history
Connection

The Jira connection to use.

Max Results

The maximum number of results to return per page.

50
Search

The JQL query to run, sent to Jira unchanged. For syntax, see JQL Documentation.

status IN ("To Do", "In Progress", "Closed")
Example Payload for Query⤓
Loading…

Raw Request​

Send a raw HTTP request to Jira. | key: rawRequest

InputNotesExample
Connection

The Jira connection to use.

Data

The HTTP body payload to send to the URL.

{"exampleKey": "Example Data"}
File Data

File Data to be sent as a multipart form upload.

[{key: "example.txt", value: "My File Contents"}]
File Data File Names

File names to apply to the file data inputs. Keys must match the file data keys above.

Form Data

The Form Data to be sent as a multipart form upload.

[{"key": "Example Key", "value": new Buffer("Hello World")}]
Header

A list of headers to send with the request.

User-Agent: curl/7.64.1
Max Retry Count

The maximum number of retries to attempt. Specify 0 for no retries.

0
Method

The HTTP method to use.

Query Parameter

A list of query parameters to send with the request. This is the portion at the end of the URL similar to ?key1=value1&key2=value2.

Response Type

The type of data you expect in the response. You can request json, text, or binary data.

json
Retry On All Errors

If true, retries on all erroneous responses regardless of type. This is helpful when retrying after HTTP 429 or other 3xx or 4xx errors. Otherwise, only retries on HTTP 5xx and network errors.

false
Retry Delay (ms)

The delay in milliseconds between retries. This is used when 'Use Exponential Backoff' is disabled.

0
Timeout

The maximum time that a client will await a response to its request

2000
URL

The path only, such as /rest/api/3/project/recent. The base URL https://api.atlassian.com/ex/jira/{cloudId} is already included, so to call https://api.atlassian.com/ex/jira/{cloudId}/rest/api/3/project/recent, enter only /rest/api/3/project/recent.

/sobjects/Account
Use Exponential Backoff

Specifies whether to use a pre-defined exponential backoff strategy for retries. When enabled, 'Retry Delay (ms)' is ignored.

false

Refresh Webhook​

Refresh a webhook expiration by ID. | key: refreshWebhook

InputNotesExample
Connection

The Jira connection to use.

Webhook ID

The unique identifier of the webhook whose expiration date to extend.

10001
Example Payload for Refresh Webhook⤓
Loading…

Search Issues​

Return a list of issues that match the given string of text. | key: searchIssues

InputNotesExample
Fields

A comma-separated list of fields to include in each returned issue. Defaults to common navigable fields (summary, status, assignee, reporter, priority, issuetype, project, created, updated). Use *all to return every field.

summary,status,assignee,priority
Connection

The Jira connection to use.

Project Key

The project key identifier (e.g., PROJ, ENG, SALES).

PROJ
Search

The text to match against records when searching.

login bug
Example Payload for Search Issues⤓
Loading…

Search Projects​

Return a list of projects that match the given string of text. | key: searchProjects

InputNotesExample
Connection

The Jira connection to use.

Search

The text to match against records when searching.

login bug
Example Payload for Search Projects⤓
Loading…

Search Users​

Return a list of users that match the given string of text. | key: searchUsers

InputNotesExample
Connection

The Jira connection to use.

Search

The text to match against records when searching.

login bug
Example Payload for Search Users⤓
Loading…

Transition Issue​

Transition an existing issue by ID. | key: transitionIssue

InputNotesExample
Issue ID

The unique identifier of the Jira issue.

10201
Connection

The Jira connection to use.

Transition ID

The unique identifier of the issue transition.

21
Example Payload for Transition Issue⤓
Loading…

Update Comment​

Update the contents and metadata of an existing comment. | key: updateComment

InputNotesExample
Comment

The plain-text body of the comment.

This is an example comment.
Comment ID

The unique identifier of the comment.

10201
Dynamic Fields

Dynamic field key/value pairs supplied as JSON. Use a key/value config variable to configure these at deploy time. Each item must contain a key and a value.

[
  {
    "key": "name",
    "value": "Example Name"
  },
  {
    "key": "projectId",
    "value": "Example projectId"
  }
]
Values

Additional field names and their values to include when creating or updating the record. Each row is merged into the request payload.

projectId=1000,name=Example
Issue ID

The unique identifier of the Jira issue.

10201
Connection

The Jira connection to use.

Example Payload for Update Comment⤓
Loading…

Update Issue​

Update an existing issue within a given project. | key: updateIssue

InputNotesExample
Additional Fields

Additional optional fields: includes Due Date, Versions, and Fix Versions.

ADF Description

The Atlassian Document Format (ADF) JSON representation of the issue description. Provide this OR Description — not both. Use the ADF playground to generate the JSON.

{
  "version": 1,
  "type": "doc",
  "content": [
    {
      "type": "paragraph",
      "content": [
        {
          "type": "text",
          "text": "Some text"
        }
      ]
    }
  ]
}
Assignee Account ID

The Atlassian account ID of the user to assign the issue to.

5b10a2844c20165700ede21g
Description

A detailed description of the issue.

The login button does not respond on mobile devices in portrait mode.
Dynamic Fields

Dynamic field key/value pairs supplied as JSON. Use a key/value config variable to configure these at deploy time. Each item must contain a key and a value.

[
  {
    "key": "name",
    "value": "Example Name"
  },
  {
    "key": "projectId",
    "value": "Example projectId"
  }
]
Values

Additional field names and their values to include when creating or updating the record. Each row is merged into the request payload.

projectId=1000,name=Example
Issue ID

The unique identifier of the Jira issue.

10201
Issue Type Name

The human-readable name of the issue type to assign to the issue. Provide this field OR Issue Type ID — not both.

Task
Issue Type ID

The unique identifier of the issue type to assign to the issue. Provide this field OR Issue Type Name — not both.

10001
Connection

The Jira connection to use.

Labels

A list of labels to attach to the issue. Each label must not contain spaces.

performance
Priority

The ID of the priority to assign to the issue. Choose from the dropdown or enter a priority ID.

3
Project ID

The unique identifier or name of the Jira project.

10201
Reporter Account ID

The Atlassian account ID of the user reporting the issue.

5b10a2844c20165700ede21g
Summary

A short one-line title for the issue, shown in lists and search results.

Fix login page responsiveness
Example Payload for Update Issue⤓
Loading…

Update Version​

Update an existing version by ID. | key: updateVersion

InputNotesExample
Description

A short summary of what the version delivers, shown on the release page.

The login button does not respond on mobile devices in portrait mode.
Dynamic Fields

Dynamic field key/value pairs supplied as JSON. Use a key/value config variable to configure these at deploy time. Each item must contain a key and a value.

[
  {
    "key": "name",
    "value": "Example Name"
  },
  {
    "key": "projectId",
    "value": "Example projectId"
  }
]
Values

Additional field names and their values to include when creating or updating the record. Each row is merged into the request payload.

projectId=1000,name=Example
Connection

The Jira connection to use.

Project ID

The unique identifier or name of the Jira project.

10201
Project Key

The project key identifier (e.g., PROJ, ENG, SALES).

PROJ
Release Details

Status flags and schedule dates.

Version ID

The unique identifier of the version.

10201
Version Name

The display name of the version (e.g., a release tag or date).

2019.08.18
Example Payload for Update Version⤓
Loading…

Changelog​

2026-11-11​

Refactored internal code

2026-11-10​

Published the component as an npm package, so code-native integrations can install it and call its actions, triggers and data sources from code with TypeScript types

2026-10-30​

Restructured action inputs into structured objects, added output schemas and inline action calling, and fixed several issue, project, user, and version actions:

  • Updated the Get Status List, List Assignable Users for Project, List Board Sprints, List Boards, List Issues by Project, List Priorities, List Projects, and List Versions actions to group their paging inputs into Pagination
  • Updated Create Issue and Update Issue to group their due date and version inputs into Additional Fields
  • Updated Create Version and Update Version to group their status flags and schedule dates into Release Details
  • Added output schemas to 38 actions for improved field mapping during configuration
  • Added inline action calling support to 43 actions for improved example output during configuration
  • Fixed Create Issue and Update Issue failing when Fix Versions was set; the value is now sent as the list of versions Jira expects
  • Fixed Create User failing on every request; it now calls Jira's user endpoint
  • Fixed Update Version failing on every request; it now calls Jira's version update endpoint
  • Fixed Search Issues and the Summary search of Find Issue failing when the search text contained a double quote mark or a backslash
  • Fixed Find Issue returning an empty result when a Number search failed on authentication, permissions, rate limits, or a server error; these errors are now reported
  • Fixed Find Project ignoring Search Type, which returned projects whose key matched a Name search or whose name matched a Key search; it now matches only the selected attribute

2026-10-20​

  • Added opt-in batching to the New and Updated Issues trigger, dispatching each changed issue individually or in configured batches so large backlogs drain in one recurrence; enabling it changes the shape a downstream step receives
  • Added an optional Look-back Date input to the New and Updated Issues trigger for performing an initial sync of issues. The initial sync begins on the first recurrence and backfills every issue modified on or after the specified date, seeding each once and ignoring the visibility filters; later recurrences are unaffected. Leave it empty to start from the first recurrence with no backfill
  • Fixed the New and Updated Issues trigger never delivering the issues beyond the page limit when more issues changed between recurrences than one recurrence could read; the remainder is now delivered on later recurrences
  • Fixed the New and Updated Issues trigger returning few or no issues for Jira accounts in a time zone west of UTC and repeatedly returning the same issues for accounts in a time zone east of UTC; it now filters by date in the account's time zone

2026-05-26​

Added the New and Updated Issues polling trigger that monitors Jira on a configured schedule using the /search/jql endpoint with a JQL updated filter. Results are partitioned into created and updated buckets based on each issue's created timestamp

2026-04-30​

Updated spectral version

2026-04-23​

Modernized authentication and connection setup with no change to connection behavior or configuration

2026-04-08​

Made webhook creation idempotent to prevent duplicate webhooks on redeploy

2026-02-26​

Added Select Version inline data source for selecting project versions to enable dynamic dropdown selection

2026-02-04​

Added OAuth 2.0 Client Credentials connection type for service account and machine-to-machine authentication scenarios

2025-12-10​

Added Issue Events trigger with automatic webhook lifecycle management for issue, comment, and attachment events

2025-11-04​

Enhanced issue search and pagination capabilities:

  • Migrated Search Issues and Find Issue actions to JQL endpoint for improved query reliability
  • Added Fields input to control which issue fields are returned across search actions
  • Improved Find Issue action with corrected JQL query syntax
  • Replaced List Issues action with List Issues by Project to fulfill JQL requirements
  • Replaced Select Issue data source with Select Issue by Project to fulfill JQL requirements
  • Removed Query (Deprecated) action

2025-04-25​

Added inline data sources for boards, issues, priorities, and webhooks to enhance integration capabilities