Jira

Read and write Jira Cloud projects, issues, subtasks, links, comments and worklogs.

Keep delivery work, customer requests and time tracking aligned with business systems.

Build a flow with Jira Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

comments

Add issue comment
Destination
Not retried automatically
Adds a plain-text comment to an issue.
List issue comments
Source
Comments on an issue, oldest first.

fields

List fields and custom fields
Source
System and custom field definitions with their types, for mapping custom fields.

issue links

Link issues (dependency)
Destination
Duplicate protected
Creates an issue link such as Blocks or Relates between two issues.

issues

Create issue or subtask
Destination
Not retried automatically
Creates an issue; provide a parent key and a subtask issue type to create a subtask.
List issues
Source
Incremental
Issues in a project ordered by last update, including subtasks, links and requested custom fields.
Update issue
Destination
Duplicate protected
Updates supplied fields on an existing issue. Omitted fields are unchanged.

projects

List projects
Source
Projects visible to the API account.

transitions

Change issue status
Destination
Not retried automatically
Moves an issue through its workflow using a transition ID.
List available status transitions
Source
Workflow transitions the API account can perform on an issue.

users

Find users
Source
Active users matching a name or email fragment, for assignee mapping.

versions

Create version (milestone)
Destination
Not retried automatically
Creates a project version with optional start and release dates.
List versions (milestones)
Source
Project versions with release dates, used as milestones.

worklogs

Log work
Destination
Not retried automatically
Records time spent on an issue.
List worklogs
Source
Time logged against an issue.

Authentication

Atlassian account email and API token

Plans and access

All Jira Cloud plans, including Free. Results follow the permissions of the Atlassian account that owns the API token.

Test environment

Free Jira Cloud sites and Atlassian developer sites can be used for testing.

Rate limits

Cost-based points and burst limits per tenant; HTTP 429 with Retry-After.

Provider events

Jira webhooks for issue, comment and worklog events. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

Attachment metadata is read; file contents are not transferred.
Descriptions and comments are converted between plain text and Atlassian Document Format; rich formatting is not preserved.
Issue creation has no provider idempotency key; uncertain creates are not repeated automatically.