Jira automations
Project Management · 2 integrations · 21 workflow guides
Teams automate Jira to eliminate manual ticket creation, sync issue status across tools like Slack and GitHub, and trigger downstream actions when bugs are filed or sprints close. The appeal is obvious — dev workflows generate a constant stream of repetitive updates that no one should be doing by hand. Choosing the right platform matters because Jira's three-layer rate limiting system and recent API deprecations mean poorly configured automations can silently fail or take down every other integration on your site.
What it costs to automate Jira
Platform pricing at different volumes. Annual billing shown.
| Platform | Free tier | 100 tasks/mo | 1K tasks/mo | 10K tasks/mo |
|---|---|---|---|---|
| Zapier | 100 tasks/mo | Free | $69/mo | $69+/mo |
| Power Automate | 750 runs/mo | Free | $15/mo | $15/mo |
| Make | 1,000 credits/mo | Free | Free | $10.59/mo |
| Pipedream | 100 credits/mo | Free | $29/mo | $79/mo |
| n8n | Yes | $20/mo | $20/mo | $50/mo |
Jira integrations
Each page compares all five platforms for that pair.
Popular Jira workflow guides
Step-by-step setup instructions for specific automations.
How to Instant Jira Issue Creation from Slack Messages with Zapier
Automatically convert Slack messages into Jira tickets using reactions or slash commands when bugs or issues are reported.
How to Create Jira Issues from Slack Messages with Make
Automatically convert urgent Slack messages into Jira tickets using reactions or slash commands with real-time processing.
How to Create Jira Issues from Slack Messages with n8n
Automatically convert Slack messages into Jira tickets using slash commands or emoji reactions with n8n.
How to Create Jira Issues from Slack Messages with Power Automate
Convert Slack messages into Jira tickets automatically using slash commands or emoji reactions with instant webhook triggers.
How to Escalate Support Tickets from Slack to Jira with Pipedream
Automatically create Jira issues from Slack messages in support channels, capturing full context and thread details for engineering handoffs.
How to sync GitHub milestones with Jira sprints using Power Automate
Auto-create Jira tickets when issues get added to GitHub milestones and link them to matching sprint boards.
How to Generate Daily Standup Issue Summaries with Pipedream
Automatically post daily Slack summaries of each team member's Jira issues including new assignments and approaching deadlines.
Jira triggers & actions by platform
Which capabilities each platform supports for Jira.
| Capability | Pipedream | Zapier | Power Automate | Make | n8n |
|---|---|---|---|---|---|
| Triggers | |||||
| Issue Updated | — | ✓ | — | ✓ | ✓ |
| Issue Status Changed | — | ✓ | — | ✓ | — |
| New Issue | — | ✓ | — | ✓ | — |
| App Event Source | ✓ | — | — | — | — |
| App-specific trigger | ✓ | — | — | — | — |
| Cron Schedule | — | — | — | — | ✓ |
| GitHub Trigger (webhook) | — | — | — | — | ✓ |
| HTTP Webhook | ✓ | — | — | — | — |
| Issue Created | — | — | — | — | ✓ |
| Jira Webhook | — | — | — | — | ✓ |
| When a record is created | — | — | ✓ | — | — |
| When a record is modified | — | — | ✓ | — | — |
| Actions | |||||
| Create Issue | — | ✓ | — | ✓ | ✓ |
| Send Message | ✓ | — | — | ✓ | ✓ |
| Update Issue | — | ✓ | — | ✓ | ✓ |
| Add Comment | — | ✓ | — | ✓ | — |
| HTTP Request | ✓ | — | — | — | ✓ |
| Add a Comment | — | — | — | ✓ | — |
| Create a record | — | — | ✓ | — | — |
| Create an Issue | — | — | — | ✓ | — |
| Create Record | ✓ | — | — | — | — |
| Custom Code Step | ✓ | — | — | — | — |
| Update a record | — | — | ✓ | — | — |
Things to know about automating Jira
Three-Layer Rate Limiting
Jira Cloud enforces rate limits simultaneously at three levels: a points-based hourly quota (a search returning 50 issues costs 51 points in one call), a per-second burst limit per endpoint, and a per-issue write frequency cap. The points-based system goes into full enforcement on March 2, 2026 for all OAuth 2.0, Forge, and Connect apps.
Search API Deprecation
The legacy /rest/api/2/search and /rest/api/3/search endpoints were deprecated in October 2024 and are no longer supported for new development as of May 1, 2025 — migrate to /rest/api/3/search/jql. Rollout is progressive by region, so if your automation suddenly receives a 410 Gone response, your Jira instance has switched over.
Webhook Delivery Not Guaranteed
Jira webhooks are best-effort — a single HTTP POST is attempted with no retry. On top of that, Jira will silently drop deliveries when more than 500 dispatches are in-flight simultaneously, and there is no native alert when this happens.
API Token vs. OAuth Auth
Basic auth with an API token is the most common setup for Zapier, Make, n8n, Power Automate, and Pipedream, but note that rate limits on API tokens took effect November 22, 2025. OAuth 1.0a is fully deprecated — if any of your existing integrations still use it, migrate to OAuth 2.0 (3LO) before they break.
Pagination Model Changed
The new JQL search API uses cursor-based pagination via a nextPageToken instead of offset parameters — this is a breaking change for any automation built on the old model. Platforms like n8n and Make may need manual workflow updates if their Jira nodes have not been patched to handle the new response format.
Shared Quota Across All Apps
All OAuth apps on your Jira site draw from the same hourly points quota — if one runaway automation exhausts it, every other integration (Slack notifications, GitHub syncs, standup bots) gets throttled simultaneously. There is nothing in the Jira admin UI to flag this, and 429 errors do not appear in the Atlassian Admin audit log.
What breaks at scale
Every time an event fires — like 'Issue Created' — Jira synchronously executes the JQL filter for every webhook registered to that event on the same processing thread. With 20 webhooks each taking up to 200ms to evaluate, you are adding up to 4 seconds of latency to every single issue creation across your entire site. At scale this compounds into visible slowdowns for end users and dramatically increases the risk of hitting the 500 in-flight dispatch limit, at which point Jira starts silently dropping webhook deliveries with no log entry and no alert to any connected platform.
All OAuth 2.0 apps on a Jira site — your Zapier zaps, Make scenarios, n8n workflows, Power Automate flows, and Pipedream pipelines — draw from the same shared hourly points quota. A single runaway bulk-sync job (like a Make scenario paginating through thousands of issues) can exhaust the quota for every other app simultaneously. The worst part: 429 errors are not recorded in the Atlassian Admin audit log, so when your Slack notifications and GitHub sync go silent, there is no obvious place in Jira to diagnose why.
The legacy offset-based pagination model is a breaking change casualty of the new /rest/api/3/search/jql migration — the new API returns a nextPageToken cursor instead of accepting offset parameters. Any automation built on the old pattern (common in older Zapier, Make, and n8n Jira nodes) will either silently return only the first page of results or fail outright with a 410 Gone on instances that have already switched over. This rollout is progressive by region, so the same workflow can work on one Jira site and break on another.
Frequently asked questions
How do I automate Jira issue creation from Slack or GitHub?
All five major platforms — Zapier, Make, n8n, Power Automate, and Pipedream — support Jira triggers and actions for creating issues from Slack messages or GitHub events like new pull requests or failed checks. Zapier and Make offer the fastest no-code setup, while n8n and Pipedream give more control over field mapping and conditional logic. Make sure your Jira user role has write permissions to the target project fields, or the action will fail silently.
What are the Jira API rate limits for automation platforms?
As of March 2, 2026, Jira Cloud enforces a points-based hourly quota for all OAuth 2.0 apps — each API call consumes points based on data volume (e.g., a 50-issue JQL search costs 51 points). There is also a per-second burst limit per endpoint and a per-issue write frequency cap. API token-based traffic (commonly used by n8n and self-hosted tools) is governed by separate burst limits that took effect November 22, 2025.
Why are my Jira webhooks not firing reliably in Zapier, Make, or n8n?
Jira webhooks are best-effort with no built-in retry — if the receiving endpoint is down or the in-flight queue exceeds 500 concurrent dispatches, the event is silently dropped. In n8n specifically, there is a known bug on self-hosted instances where the Jira trigger fails to activate for certain workflows even when others on the same server work fine. For Jira Service Management, automation webhooks also require the destination URL to be manually whitelisted in System > Allowlist.
Does Jira Cloud Free support API access for automation tools?
Yes, Jira Cloud Free does support API access, so basic automations in Zapier, Make, n8n, Power Automate, and Pipedream will work. However, some advanced webhook event types may require Jira Standard or Premium, and Free tier instances are subject to the same shared hourly quota limits that can affect all apps on your site. For high-volume automations, hitting the quota on a Free plan will throttle every connected tool with no warning in the Jira UI.