GitHub automations
Developer Tools · 2 integrations · 12 workflow guides
Version control events — pull requests opened, issues filed, code merged — are natural triggers for downstream workflows across project management, CI/CD, and team communication tools. Teams automate GitHub to eliminate manual status updates, enforce review processes, sync work across tools like Jira and Slack, and orchestrate deployments without human handoffs. Choosing the right automation platform matters more here than with most apps, because GitHub's layered rate limits and webhook reliability quirks can silently break workflows that appear to be working.
What it costs to automate GitHub
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 |
GitHub integrations
Each page compares all five platforms for that pair.
Popular GitHub workflow guides
Step-by-step setup instructions for specific automations.
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 sync GitHub milestones with Jira sprints with Pipedream
Automatically create and link Jira tickets when GitHub issues are added to milestones.
How to route GitHub bug reports to Jira with Power Automate
Auto-creates Jira bug tickets when GitHub issues get labeled 'bug', mapping severity from GitHub labels to Jira priority fields.
How to Route Bug Reports from GitHub to Jira with Pipedream
Automatically creates Jira bug tickets when GitHub issues are labeled 'bug' with severity mapping from GitHub labels.
GitHub triggers & actions by platform
Which capabilities each platform supports for GitHub.
| Capability | Pipedream | Zapier | Power Automate | Make | n8n |
|---|---|---|---|---|---|
| Triggers | |||||
| App Event Source | ✓ | — | — | — | — |
| App-specific trigger | ✓ | — | — | — | — |
| Cron Schedule | — | — | — | — | ✓ |
| GitHub Trigger | — | — | — | — | ✓ |
| GitHub Trigger (webhook) | — | — | — | — | ✓ |
| HTTP Webhook | ✓ | — | — | — | — |
| New Commit | — | ✓ | — | — | — |
| New Event (polling) | ✓ | — | — | — | — |
| New Issue | — | ✓ | — | — | — |
| New Pull Request | — | ✓ | — | — | — |
| Watch Issues | — | — | — | ✓ | — |
| Watch Pull Requests | — | — | — | ✓ | — |
| When a record is created | — | — | ✓ | — | — |
| When a record is modified | — | — | ✓ | — | — |
| Actions | |||||
| HTTP Request | ✓ | — | — | — | ✓ |
| Send Message | ✓ | — | — | — | ✓ |
| Add a Comment | — | — | — | ✓ | — |
| Add Comment | — | ✓ | — | — | — |
| Create a record | — | — | ✓ | — | — |
| Create an Issue | — | — | — | ✓ | — |
| Create Issue | — | ✓ | — | — | — |
| Create Message | — | — | — | ✓ | — |
| Create Record | ✓ | — | — | — | — |
| Custom Code Step | ✓ | — | — | — | — |
| Update a record | — | — | ✓ | — | — |
Things to know about automating GitHub
Rate Limits Are Layered
Authenticated REST API calls are capped at 5,000 requests per hour for standard users, but a parallel secondary limit of 900 points per minute (where write operations cost 5 points each) can trigger 403 or 429 blocks long before the hourly cap is reached. Secondary limits can also fire for undisclosed reasons and are subject to change without notice.
Webhooks Don't Retry
GitHub webhooks have no built-in retry mechanism — a failed delivery is permanently lost, with no visibility into what was missed. Each repository or organization supports a maximum of 20 webhooks per event type, so high-fan-out architectures require a proxy or forwarding layer.
Fine-Grained PATs Are Now Preferred
GitHub recommends fine-grained personal access tokens over classic PATs; they offer over 50 granular permissions scoped per repository and are authorized before org access is granted. There is a hard cap of 50 fine-grained PATs per user — teams automating at scale should use GitHub Apps instead, which distribute rate limits across installations and can scale up to 15,000 requests per hour on GitHub Enterprise Cloud.
Breaking API Changes in 2026
GitHub's March 2026 REST API calendar version (2026-03-10) is the first to include breaking changes: the merge_commit_sha field is removed from pull request responses, the singular assignee field is removed from issue and PR endpoints (migrate to assignees array), and the workflow dispatch endpoint now returns 200 with run details instead of 204. Automations that don't pin the X-GitHub-Api-Version header default to 2022-11-28, which remains supported for at least 24 months.
Webhook Secret Exposure Incident
A bug active between September 11 and December 10, 2025 (and briefly again January 5, 2026) inadvertently exposed webhook secrets in an HTTP header on GitHub's delivery platform. If your automations on any platform — Zapier, Make, n8n, Power Automate, or Pipedream — were receiving GitHub webhooks during that window, check whether you received a notification from GitHub in April 2026 and rotate your secrets accordingly.
Platform Cost Diverges at Volume
Zapier counts every step in a workflow as a task, so multi-step GitHub automations (trigger → transform → Jira update → Slack notify) consume tasks quickly. Make charges per operation including the trigger module. n8n's self-hosted model uses execution-based pricing with no per-step charges, which can deliver 80–90% cost savings over Zapier for teams running complex workflows at volume.
What breaks at scale
Secondary rate limits become the real bottleneck before you ever approach the 5,000 requests/hour primary cap. Large teams with many concurrent PRs triggering CI runs, Slack notifications, and Jira syncs simultaneously can exhaust the 900-point-per-minute secondary budget fast — write operations cost 5 points each, so 180 write calls per minute is the ceiling. When the block hits (403 or 429), it lasts 1 to 30 minutes and the trigger that fired during the block is silently dropped on platforms that don't queue and retry, including standard webhook-based setups on Zapier and Make.
GitHub webhooks have no retry mechanism — if a delivery fails, that event is gone permanently with zero visibility. The July 2024 outage demonstrated this concretely: webhooks were delayed up to 71 minutes, meaning any automation on Zapier, Make, n8n, Power Automate, or Pipedream that was supposed to trigger a deployment, create a Jira ticket, or send an alert simply didn't fire on time with no error surfaced to the user. For workflows where event loss is unacceptable, polling-based triggers are a more resilient fallback, though they introduce latency and additional API call overhead against your rate limit budget.
The March 2026 API calendar version (2026-03-10) introduced the first breaking changes in GitHub's REST API history, including removal of merge_commit_sha from PR responses and removal of the singular assignee field from issue and PR objects. Workflows on any platform — including pre-built Zaps, Make scenarios, and n8n nodes — that parse these fields without an explicit X-GitHub-Api-Version: 2022-11-28 header will eventually break when GitHub updates the default version. Teams that built automations and moved on without documentation of the API version in use are most at risk of silent data loss when field values come back null or missing.
Frequently asked questions
Which automation platform works best with GitHub?
For simple use cases like posting a Slack message when a PR is opened, Zapier and Make both work reliably and require minimal setup. For complex pipelines — multi-branch logic, high-volume repos, or self-hosted infrastructure — n8n's open-source model and execution-based pricing give more flexibility, while Pipedream's code-native environment suits developers who need fine-grained API control. Power Automate is a strong option if your team is already in the Microsoft 365 ecosystem and needs GitHub connected to Azure DevOps or Teams.
How do I authenticate GitHub with Zapier, Make, or n8n?
All major platforms — Zapier, Make, n8n, Power Automate, and Pipedream — support GitHub OAuth and personal access tokens for authentication. GitHub recommends fine-grained PATs over classic PATs for better permission scoping, but classic PATs are still required for some edge cases like write access to public repos you don't own. For production automation at scale, GitHub Apps are the preferred approach because they carry higher rate limit allocations and don't tie usage to a single user account.
Can GitHub webhooks miss events or lose data in automation workflows?
Yes — GitHub's webhook system has no built-in retry mechanism, meaning any delivery failure results in a permanently lost event with no recovery path. In July 2024, a GitHub outage caused average webhook delays of 24 minutes with some delayed up to 71 minutes. Platforms like Pipedream and n8n support webhook polling as an alternative, which trades real-time delivery for more reliable event capture, and is worth considering for workflows where missing an event has downstream consequences.
Will GitHub rate limits break my automation at scale?
They can, especially if you're using a standard user token rather than a GitHub App. The primary REST API limit is 5,000 requests per hour, but secondary limits — 900 points per minute for REST, with write calls costing 5 points each — can throttle workflows far sooner. Platforms like Make and Zapier share this rate limit budget across all their users authenticating via the same token, and none of the five major platforms (Zapier, Make, n8n, Power Automate, Pipedream) fully insulate you from secondary limit blocks, which can last 1 to 30 minutes.