Connect Jira to Zapier by adding Jira as a trigger or action app in the Zap editor. Triggers include New Issue and Issue Status Changed, and actions include Create Issue, Update Issue, Find Issue, Find Issues via JQL, Add Watcher and Move Issue to Sprint. Polling triggers check every 15 minutes on the Zapier Free plan, as of Nov 2026.
Jira at the start of a zap, or at the end
The first decision is which side Jira sits on. Either something in Jira kicks off work elsewhere, such as a status change posting a note to your client tracker, or something elsewhere creates or updates work in Jira, such as a support form raising an issue. Zapier offers both, and you'll often want one of each.
The two Jira triggers
- New Issue fires when a new issue is created.
- Issue Status Changed fires each time an issue changes status in a project.
Issue Status Changed is the more useful of the two for small teams. It'll tell a client, a manager or another tool the moment work moves to Done, and nobody's got to remember.
Everything Zapier can do inside Jira
| Action | What it does |
|---|---|
| Create Issue | Creates an issue by project and issue type, with a rich text option |
| Update Issue | Updates an existing issue, including its status |
| Add Attachment to Issue | Adds a file to an issue |
| Get Attachment Content | Retrieves an attachment by its ID |
| Add or Edit Form on Issue | Adds or edits a form on an issue, and can submit it |
| Add Watcher to Issue | Adds a new watcher |
| Move Issue to Sprint | Moves an issue to an active or open sprint by project board |
| Find Issue | Searches by summary or key |
| Find Issues (Via JQL) | Searches using JQL, with an optional maximum number of results |
| Find Filters | Finds saved filters by name or owner |
| Get Sprint Information | Retrieves the details of a sprint |
The search actions matter more than they'd seem. Run Find Issue before Create Issue and you can check whether a ticket already exists, which stops a busy form from flooding a project with duplicates you'd then have to merge. Find Issues (Via JQL) lets you pull a precise set of issues using the same query language your developers already use in Jira.
Building the zap
- In the Zap editor, set up the trigger step and choose the event you want.
- Connect your account when prompted, then pick the project the trigger should watch.
- Use the test record Zapier pulls from your existing data to set up the later steps.
- Add one or more actions and map the fields.
- Turn the zap on.
A zap's made of a trigger and one or more actions. Once you add more than one action, or filters and searches, it becomes a multi-step zap, which is available on higher plans. A find-then-create pattern counts as multi-step, so it's worth planning for that before you build.
Fifteen minutes between the change and the zap
Zapier's Jira integrations page lists both triggers as polling triggers. They check for new data on a timer rather than being pushed the change, and on the Free plan, as of Nov 2026, that timer is every 15 minutes. So a new issue or a status change can take up to 15 minutes to start a zap.
For reporting and housekeeping, that's fine and you won't notice it. For anything a customer is waiting on, such as a support confirmation, set expectations with your team so nobody assumes the zap is broken and builds a second one.
Three zaps worth trying first
- Support form to issue: a form trigger, Find Issue to check for duplicates, then Create Issue in your support project.
- Done to client update: Issue Status Changed, filtered to Done, then a message or email in the tool your client uses.
- Urgent work to the sprint: a trigger from your help desk, then Create Issue and Move Issue to Sprint so it lands in the active sprint.
A webhook route instead
n8n has a Webhook node that can start a workflow when an app sends data, which is an alternative if you'd rather work with webhooks than a zap. My comparison of n8n and Zapier covers the trade-offs.
My advice for your first Jira zap
Start with Issue Status Changed and one action, so you'll see it working before you add steps. Use Find Issue before Create Issue whenever outside data creates tickets, and build for the 15-minute delay if you're on the Free plan. If Jira itself is the sticking point, my roundup of other project tools covers lighter options.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Can Zapier create Jira issues?
Yes. The Create Issue action creates an issue by project and issue type.
Can it trigger on status changes?
Yes, with the Issue Status Changed trigger.
Can Zapier search Jira with JQL?
Yes, with Find Issues (Via JQL).
How quickly do Jira triggers run?
They poll, every 15 minutes on the Zapier Free plan as of Nov 2026.
Can Zapier move issues to a sprint?
Yes, with the Move Issue to Sprint action.
