Jira Trigger

The Jira Trigger fires your workflow the moment an event happens in Jira — such as an issue being created, a comment being added, a sprint starting, or a project being updated. It works via Jira's native Webhooks system.

Getting Your Jira Credentials

Before setting up the trigger, you need credentials to connect to your Jira instance. Jira supports three authentication methods:

Jira Cloud (API Token)

This is the recommended method for Jira Cloud users (*.atlassian.net).

Go to https://id.atlassian.com/manage-profile/security/api-tokens (opens in a new tab)
Click Create API token
Enter a label (e.g., InditeAI Trigger)
Click Create and copy the token immediately — you won't see it again
You'll need:
- Email: Your Atlassian login email
- API Token: The token you just copied
- Domain: https://yourcompany.atlassian.net

Jira Server — Password Auth

For self-hosted Jira Server or Data Center:

You'll need:
- Email: Your Jira login email
- Password: Your Jira login password
- Domain: https://jira.yourcompany.com

Jira Server — Personal Access Token (PAT)

For Jira Server 8.14+ and Data Center (recommended over password):

In Jira, go to Profile → Personal Access Tokens
Click Create token, name it (e.g., InditeAI), and click Create
Copy the token immediately
You'll need:
- Personal Access Token: The token you just copied
- Domain: https://jira.yourcompany.com

Setup Guide

Step 1: Add the Trigger to Your Workflow

Add the Jira Trigger block as your workflow's starting block.
Click Select Credentials and create a new Jira credential with the details from above.
Choose the event types you want to subscribe to (e.g., jira:issue_created, comment_created).
Note the Webhook URL displayed in the settings panel — you will register this in Jira.
Click Mark as registered once you've completed Step 2.

Step 2: Register the Webhook in Jira

For Jira Cloud:

Go to your Jira instance → Settings (gear icon) → System → WebHooks
- Direct URL: https://yourcompany.atlassian.net/plugins/servlet/webhooks
Click Create a WebHook
Give it a name (e.g., InditeAI Workflow Trigger)
Paste your Webhook URL from Step 1 into the URL field
Under Events, select the events that match what you chose in the trigger settings:
- Issue: created, updated, deleted
- Comment: created, updated, deleted
- Issue Link: created, deleted
- Project: created, updated, deleted
- Sprint: created, started, closed, updated, deleted
- Board: created, updated, deleted, configuration changed
- Version: created, updated, deleted, moved, released, unreleased
- Worklog: created, updated, deleted
- User: created, updated, deleted
(Optional) Add a JQL filter to only receive events for specific issues (e.g., project = PROJ)
Click Create
Ensure the webhook status shows as Enabled

For Jira Server / Data Center:

Go to Administration → System → WebHooks
Click Create a WebHook
Follow the same steps as Cloud above

Supported Event Types

Events are grouped by category:

Group	Events
Issue	`jira:issue_created`, `jira:issue_updated`, `jira:issue_deleted`
Comment	`comment_created`, `comment_updated`, `comment_deleted`
Issue Link	`issuelink_created`, `issuelink_deleted`
Project	`project_created`, `project_updated`, `project_deleted`
Sprint	`sprint_created`, `sprint_started`, `sprint_closed`, `sprint_updated`, `sprint_deleted`
Board	`board_created`, `board_updated`, `board_deleted`, `board_configuration_changed`
User	`user_created`, `user_updated`, `user_deleted`
Version	`jira:version_created`, `jira:version_updated`, `jira:version_deleted`, `jira:version_moved`, `jira:version_released`, `jira:version_unreleased`
Worklog	`worklog_created`, `worklog_updated`, `worklog_deleted`

You can subscribe to multiple event types in a single trigger block. Use the Select All checkbox per group for convenience.

Response Data

When the trigger fires, the following data is available as workflow variables:

Variable	Description
`webhookEvent`	The event type (e.g., `jira:issue_created`)
`issue.id`	Internal Jira issue ID
`issue.key`	Human-readable issue key (e.g., `PROJ-123`)
`issue.fields.summary`	Issue title/summary
`issue.fields.status.name`	Current status (e.g., `In Progress`)
`issue.fields.priority.name`	Priority level (e.g., `High`)
`issue.fields.issuetype.name`	Issue type (e.g., `Bug`, `Task`)
`issue.fields.project.key`	Project key (e.g., `PROJ`)
`issue.fields.project.name`	Project display name
`issue.fields.assignee.displayName`	Assignee's name
`issue.fields.assignee.accountId`	Assignee's account ID
`issue.fields.reporter.displayName`	Reporter's name
`issue.fields.created`	Issue creation timestamp
`issue.fields.updated`	Last update timestamp
`user.displayName`	Name of the user who triggered the event
`user.emailAddress`	Email of the user who triggered the event
`user.accountId`	Account ID of the user who triggered the event
`changelog.items`	Array of field changes (for update events)
`comment.id`	Comment ID (for comment events)
`comment.body`	Comment text (for comment events)
`comment.author.displayName`	Comment author's name
`timestamp`	Unix timestamp of the event

How Jira Trigger Helps with Automation

The Jira Trigger enables powerful real-time automation scenarios:

Instant notifications: Get Slack/email alerts the moment issues are created or status changes
Cross-tool sync: Mirror Jira changes to other systems (CRM, spreadsheets, databases) in real-time
Smart routing: Automatically assign or re-assign issues based on labels, priority, or project
Escalation: When an issue is marked high-priority, automatically page the on-call team
Reporting: Log every issue transition to a Google Sheet or database for custom analytics
AI-powered triage: Use an LLM Agent to analyze new issues and auto-categorize or suggest solutions

Example Use Cases

Bug triage: When a new bug is created, use an AI agent to analyze the description, suggest a priority level, and assign it to the right team.
Sprint notifications: When a sprint starts or closes, send a summary to Slack with the list of issues.
SLA monitoring: When an issue is created, start a timer. If it isn't resolved within the SLA window, escalate by transitioning it to "Urgent" and notifying the manager.
Customer sync: When a support issue is resolved in Jira, update the corresponding HubSpot ticket and send a resolution email to the customer.
Release tracking: When a version is released, automatically compile release notes from resolved issues and post them to a Slack channel or documentation page.
Worklog reporting: When a worklog is created, log the time entry to an external time-tracking system or spreadsheet.

Troubleshooting

Workflow not triggering?

Confirm the webhook in Jira is Enabled (not paused or errored).
Ensure the workflow is Published and Active in InditeAI.
Verify the Webhook URL in Jira exactly matches the URL shown in the trigger settings.
Check that the subscribed event types in Jira match those selected in the block.
For Jira Cloud: check the webhook's Last triggered timestamp in Jira settings to confirm it's firing.

Getting 401 Unauthorized errors?

Verify your credentials are still valid (API tokens can expire or be revoked).
Check that the email address matches the one used to create the token.
For Server PAT: confirm the token hasn't expired.

Missing data in the response?

changelog is only populated for jira:issue_updated events, not for creation or deletion.
comment fields are only available for comment_* events.
Custom fields appear under issue.fields.customfield_XXXXX — use the field ID, not the display name.

Webhook not receiving events for a specific project?

Check if you added a JQL filter when creating the webhook in Jira — it may be excluding events from that project.
Verify the authenticated user has access to that project.

Duplicate events received?

Jira may retry webhook delivery if it doesn't receive a timely response. InditeAI handles this gracefully, but you may see duplicate log entries. Use the webhookEvent + issue.key + timestamp combination to deduplicate if needed.

Calendly Trigger Shopify Trigger