Issue tracking and project management
Jira Cloud currently provides 3 triggers that can start a workflow and 16 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
New Issue
Triggers when a new issue is created
Updated Issue
Triggers when an issue is updated
Updated Issue Status
Triggers when an issue status is updated
Create Issue
Creates a new issue in a project.
Update Issue
Updates an existing issue.
Find User
Finds an existing user.
Search Issues
Search for issues with JQL
Assign Issue
Assigns an issue to a user.
Add Attachment to Issue
Adds an attachment to an issue.
Get Issue Attachment
Retrieves an attachment from an issue.
Add Watcher to Issue
Adds a new watcher to an issue.
Add Issue Comment
Adds a comment to an issue.
Update Issue Comment
Updates a comment to a specific issue.
Link Issues
Creates a link between two issues.
List Issue Comments
Returns all comments for an issue.
Delete Issue Comment
Deletes a comment on a specific issue.
Markdown to Jira format
Convert Markdown-formatted text to Jira's ADF syntax for use in comments and descriptions etc
Get Issue
Get issue data.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Jira Cloud event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Issue
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Jira Cloud action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Issue
Combine Jira Cloud with another integration and Coherence records to turn activity in one tool into an owned next step in the shared workspace.
Starts with
New Issue
Finishes with
Create Issue, then preserve the outcome in Coherence
The exact authentication fields depend on Jira Cloud. The workflow structure stays straightforward:
Authorize the Jira Cloud account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Jira Cloud or provide a complementary trigger or action.
Jira Cloud currently provides 3 triggers that can start a workflow and 16 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Jira Cloud currently lists 3 triggers and 16 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Jira Cloud triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
