Connect Jira to Confection

Use 4 documented Jira triggers to run 2 documented Confection actions.

4 source triggers

2 target actions

Reverse direction supported

Start Free Trial Browse Jira integrations

Why Connect Jira & Confection?

Start with a Jira event

Choose from 4 documented triggers, including New Event, New Issue Created Event (Instant), New Issue Deleted Event (Instant).

Run a Confection action

Send the event into one of 2 documented actions, such as Get Full Details of UUID, Get Related UUIDs.

Map and review the workflow

Choose the fields and conditions for the workflow, then test the result before activation.

Available Triggers & Actions

Jira

Triggers (4)

New Event

Emit new event when an event with subscribed event source triggered, See the documentation

webhook

New Issue Created Event (Instant)

Emit new event when an issue is created. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook

New Issue Deleted Event (Instant)

Emit new event when an issue is deleted. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook

New Issue Updated Event (Instant)

Emit new event when an issue is updated. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook

Actions (24)

Add Attachment To Issue

Adds an attachment to an issue. See the documentation

Add Comment To Issue

Adds a new comment to an issue. See the documentation

Add Multiple Attachments To Issue

Adds multiple attachments to an issue. See the documentation

Add Watcher To Issue

Adds a user as a watcher of an issue by passing the account ID of the user, For example, 5b10ac8d82e05b22cc7d4ef5, If no user is specified the calling user is added. See the documentation

Assign Issue

Assigns an issue to a user. See the documentation

Check Issues Against JQL

Checks whether one or more issues would be returned by one or more JQL queries. See the documentation

Count Issues Using JQL

Provide an estimated count of the issues that match the JQL. See the documentation

Create Custom Field Options (Context)

Create a context for custom field options. See the documentation.

Create Future Sprint

Creates a future sprint. See the documentation

Create Issue

Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask. See the documentation

Create Jira Version in Project

Creates a project version. See the documentation

Delete Project

Deletes a project. See the documentation

Get All Projects

Gets metadata on all projects. See the documentation

Get Board

Returns the board for the given board ID. See the documentation

Get Cloud ID

Gets the cloud ID and details of all accessible Jira Cloud sites. See the documentation

Get Current User

Returns the authenticated Jira user's account ID, display name, email, and active status. Call this first when the user says 'my issues', 'assigned to me', or needs their Jira identity. Use the returned accountId with **Search Issues with JQL** (e.g. assignee = '{accountId}') or **Assign Issue**. Requires a Cloud ID to identify the Jira site. See the documentation.

Get Issue

Gets the details for an issue. See the documentation

Get Issue Picker Suggestions

Returns lists of issues matching a query string. See the documentation

Get Issue Types

Gets the available issue types. If a project ID is provided, returns issue types for that project. Otherwise, returns all issue types accessible to the user. See the documentation

Get Sprint

Returns the sprint for a given sprint ID. See the documentation

Get Task

Gets the status of a long-running asynchronous task. See the documentation

Get Transitions

Gets either all transitions or a transition that can be performed by the user on an issue, based on the issue's status. See the documentation

Get User

Gets details of user. See the documentation

Get Users

Gets the details for a list of users. See the documentation

Confection

Triggers (3)

New Event

Emit new event when a UUID receives a value for the configured **Event Name**. The latest value as well a history of all values ever received for that **Event Name** will be returned.

polling

New Field Value

Emit new event when the UUID is significant enough to be classified as a lead. You define the field of significance and if a UUID gets a value for this field, it will trigger.

polling

New or Updated Leads

Emit new event when any UUID is created or updated. To learn more about how Confection handles UUIDs, visit https://confection.io/main/demo/#uuid.

polling

Actions (2)

Get Full Details of UUID

This action will retrieve the full details of a specified UUID.

Get Related UUIDs

This action will retrieve all UUIDs that have a likeness score of at least 50 (default) with the provided UUID. The likeness score can be customized in configuration.