How Do I Set Up a Jira Trigger for My Agent or Workflow?

Last updated: April 10, 2026

Gumloop supports Jira as an event-based trigger for both agents and workflows. When a new issue is created in a Jira project, your agent or workflow fires automatically. You can filter by status, priority, labels, issue type, assignee, custom fields, JQL, or saved filters.

Prerequisites

  • You must connect your Jira account on the Apps page before setting up the trigger.

  • Triggers are available on the Pro plan and above.

Setting Up a Jira Trigger (Agents)

  1. Open your agent's configuration page

  2. Go to the Triggers section and click + Trigger

  3. Choose Event-Based Trigger

  4. Select Jira from the integration list

Jira trigger configuration in Gumloop

  1. Configure the trigger:

    • Credential — select your connected Jira account

    • Resource — your Jira instance

    • Project — the Jira project to monitor

    • Filters (optional) — narrow which issues fire the trigger

  2. Write your prompt template using the available variables (Issue ID, Key, Summary, etc.)

  3. Click Create — the trigger is immediately active

Setting Up a Jira Trigger (Workflows)

For workflows, drag the Jira Issue Reader node into your workflow editor, configure it with the same options above (credential, project, filters), and toggle Activate as workflow trigger to Yes. Then save your workflow.

Filter Options

There are three ways to filter which Jira issues fire the trigger:

Standard Filters

Filter by Status, Priority, Labels, Issue Type, Assignee, and Custom Fields. These are dropdown selections — no query language needed.

JQL (Jira Query Language)

Write a custom JQL expression for advanced filtering. For example:

  • priority = High AND labels = "urgent"

  • issuetype = Bug AND status = "To Do"

Saved Filter

Use an existing filter saved in your Jira instance. This is useful if your team already has complex filters set up in Jira that you want to reuse.

How the Trigger Works

  • Fires when: A new issue is created in the selected Jira project that matches your filters.

  • Polling frequency: Checks for new issues approximately every 60 seconds.

  • Batch size: Fetches up to 5 new issues per poll.

  • Deduplication: Uses a compound cursor based on the issue's created timestamp and issue key to avoid processing the same issue twice.

Available Template Variables

When the trigger fires, these variables are available in your prompt template:

  • Issue ID — the Jira issue ID

  • Key — the issue key (e.g., PROJ-123)

  • Summary — the issue title

  • Other issue fields based on the Information to Read selection in your trigger configuration

Common Use Cases

  • Bug triage: Agent automatically categorizes and prioritizes new bugs based on description and labels

  • Slack notifications: Post a formatted message to a Slack channel whenever a high-priority issue is created

  • Cross-tool sync: Create a corresponding card in Linear, Asana, or a Google Sheet row when a new Jira issue lands

  • SLA tracking: Start a timer and alert the team if high-priority issues aren't assigned within a threshold

Troubleshooting

  • Trigger not firing? Make sure your Jira credential is connected on the Apps page and that the project exists in the selected Jira instance.

  • Only some issues fire the trigger? Check your filters. Standard filters, JQL, or saved filters can narrow which issues match. Remove filters temporarily to test.

  • Trigger deactivated itself? Triggers automatically deactivate after 3 consecutive failed runs. Check your Triggers page for error details, fix the issue, and re-enable.

Related