Jira Trigger

Triggers a workflow when events occur in Jira. The webhook is automatically registered with Jira when the workflow is published — no manual setup required.

Requires a Jira connection with admin permissions for webhook management.

Configuration

Field	Description	Notes
Connection	Jira connection to use	Required
Events	Which events to listen for	Required. Multiple selection
JQL Filter	Optional JQL to limit which issues trigger	Optional

Supported Events

Event	Description
jira:issue_created	Issue created
jira:issue_updated	Issue updated
jira:issue_deleted	Issue deleted
comment_created	Comment added
comment_updated	Comment edited
comment_deleted	Comment removed
issuelink_created	Issue link created
issuelink_deleted	Issue link removed

Output

The trigger passes the full Jira webhook payload to downstream nodes. Key fields include:

Field	Description
body.webhookEvent	Event type (e.g., jira:issue_created)
body.issue	Full issue object
body.user	User who triggered the event
body.changelog	Changes made (for update events)

JQL Filter Example

To only trigger on issues in a specific project:

project = MYPROJECT AND status != Done

How It Works

1. You configure the trigger with events and an optional JQL filter
2. When you publish the workflow, the system automatically creates a webhook in your Jira instance
3. When you re-publish or delete the workflow, the old webhook is cleaned up and a new one is registered
4. Jira sends event payloads to your workflow's unique webhook URL

Admin Permissions

Your Jira account needs admin permissions to create webhooks. If webhook registration fails, the trigger won't receive events.