Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Jira Cloud

Issue tracking and project management

CategoryProductivity
Authenticationcustom
Version0.4.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Jira Cloud with Flows360

Issue tracking and project management

Use the Jira Cloud connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 17 actions and 9 triggers.

Available actions

  • Create Issue
  • Update Issue
  • Find User
  • Search Issues
  • Assign Issue
  • Add Attachment to Issue
  • Get Issue Attachment
  • Add Watcher to Issue
  • Plus 9 additional declared actions.

Available triggers

  • New Issue
  • Updated Issue
  • Updated Issue Status
  • New Comment
  • Issue Assigned
  • New Attachment on Issue
  • Plus 3 additional declared triggers.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Jira Cloud
  • Package: @activepieces/piece-jira-cloud@0.4.0
  • Exact artifact digest: sha256:f410246ff6f0184cf4818cfec93ccca0f98add12f337f89d542d22cff883e15e
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Issue (create_issue), Creates a new issue in a project. Classification: read.
  • Update Issue (update_issue), Updates an existing issue. Classification: read.
  • Find User (find-user), Finds an existing user. Classification: read.
  • Search Issues (search_issues), Search for issues with JQL Classification: read.
  • Assign Issue (assign_issue), Assigns an issue to a user. Classification: read.
  • Add Attachment to Issue (add_issue_attachment), Adds an attachment to an issue. Classification: read.
  • Get Issue Attachment (get-issue-attachment), Retrieves an attachment from an issue. Classification: read.
  • Add Watcher to Issue (add-watcher-to-issue), Adds a new watcher to an issue. Classification: read.
  • Add Issue Comment (add_issue_comment), Adds a comment to an issue. Classification: read.
  • Update Issue Comment (update_issue_comment), Updates a comment to a specific issue. Classification: read.
  • Link Issues (link-issues), Creates a link between two issues. Classification: read.
  • List Issue Comments (list_issue_comments), Returns all comments for an issue. Classification: read.
  • Delete Issue Comment (delete_issue_comment), Deletes a comment on a specific issue. Classification: read.
  • Markdown to Jira format (markdownToJiraFormat), Convert Markdown-formatted text to Jira's ADF syntax for use in comments and descriptions etc Classification: read.
  • Get Issue (get_issue), Get issue data. Classification: read.
  • Transition Issue (transition_issue), Moves an issue to a new status by executing a workflow transition. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Issue, polling.
  • Updated Issue, polling.
  • Updated Issue Status, polling.
  • New Comment, polling.
  • Issue Assigned, polling.
  • New Attachment on Issue, polling.
  • New Issue Type, polling.
  • New Project, polling.
  • New Priority, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects26
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Instance URL Required
  • Email Required
  • API Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Issue Yes No Creates a new issue in a project.
Update Issue Yes No Updates an existing issue.
Find User Yes No Finds an existing user.
Search Issues Yes No Search for issues with JQL
Assign Issue Yes No Assigns an issue to a user.
Add Attachment to Issue Yes No Adds an attachment to an issue.
Get Issue Attachment Yes No Retrieves an attachment from an issue.
Add Watcher to Issue Yes No Adds a new watcher to an issue.
Add Issue Comment Yes No Adds a comment to an issue.
Update Issue Comment Yes No Updates a comment to a specific issue.
Link Issues Yes No Creates a link between two issues.
List Issue Comments Yes No Returns all comments for an issue.
Delete Issue Comment Yes No Deletes a comment on a specific issue.
Markdown to Jira format Yes No Convert Markdown-formatted text to Jira's ADF syntax for use in comments and descriptions etc
Get Issue Yes No Get issue data.
Transition Issue Yes No Moves an issue to a new status by executing a workflow transition.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Issue Yes No polling trigger declared by the pinned package.
Updated Issue Yes No polling trigger declared by the pinned package.
Updated Issue Status Yes No polling trigger declared by the pinned package.
New Comment Yes No polling trigger declared by the pinned package.
Issue Assigned Yes No polling trigger declared by the pinned package.
New Attachment on Issue Yes No polling trigger declared by the pinned package.
New Issue Type Yes No polling trigger declared by the pinned package.
New Project Yes No polling trigger declared by the pinned package.
New Priority Yes No polling trigger declared by the pinned package.

Setup

Setup

  1. Add the Jira Cloud connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Instance URL (instanceUrl), required.
  • Email (email), required.
  • API Token (apiToken), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-jira-cloud@0.4.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 17 actions and 9 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Jira Cloud connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-jira-cloud@0.4.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com