Resources · Zapier integration

GitHub Zapier integrationAutomate GitHub with Zapier.

The GitHub Zapier integration gives you 20 triggers, 12 actions and 8 searches. Repo activity can start work in other apps, and other apps can open issues, branches or pull requests for you. One catch up front: every GitHub trigger runs on a timer, none is instant.

See the 40 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the GitHub Zapier integration actually does for you

It links your GitHub account to Zapier so that something happening in a repository (a new issue, a release, a pull request) starts an automation, and so that other tools can write back into GitHub without anyone opening a browser tab. You pick the event, you pick what follows, Zapier runs it.

Three results people build first. A triage desk: New Issue feeds Add Labels to Issue, so nothing sits untagged. A release log: New Release pushes the news to the place your customers or your sales team actually read. A paper trail for outside requests: a form or a support ticket elsewhere becomes a GitHub issue through Create Issue, and Find or Create an Issue keeps duplicates out.

Now what Zapier does not do here. None of the 20 GitHub triggers is instant: Zapier checks your account at an interval that depends on your plan, so on the free plan a new pull request can wait up to 15 minutes before anything moves. It also never digs into the past. Issues opened before you switch the Zap on stay where they are. And it will not merge code on its own judgment: Create Pull Request merges only when you tell it to.

Comparing tools before you commit? The same app has its own page for GitHub n8n integration and for GitHub Make integration, written the same way, so you can line them up side by side.

Vocabulary

Zapier words in one minute

Seven words come back on every line of this page. Here they are once, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for that event to show up.
Action
What the Zap does after it starts: the step that writes, sends or moves something in an app on your behalf.
Task
The unit Zapier bills you for: one action that your Zap finishes successfully. Your plan allowance is a count of these.
Polling vs instant
Polling: Zapier asks the app for new items on a timer. Instant: the app tells Zapier the moment it happens. All GitHub triggers poll.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and quietly stops it the rest of the time.
Search step
A step that looks up something already sitting in an app (a branch, an issue, a user) so later steps can use what it found.
Cost

What a GitHub Zap really costs

GitHub is not a premium app, so it works on the free plan. The bill is counted in tasks, and only successful actions count.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, 2-step Zaps only
  • Trigger checksFree, never billed
  • Failed actionNot counted

The trigger itself costs nothing, however often Zapier checks your repos. Each action that goes through counts once, so a Zap with three actions burns three times what a one-action Zap does, and an action that fails is not charged. The free plan gives you 100 tasks a month and unlimited Zaps, but only two steps per Zap. Add a filter, a search step or a second action and you have a multi-step Zap, which needs a paid plan.

Connect

Connect GitHub to Zapier in three steps

  1. 01

    Open your Apps page

    In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box: type GitHub and pick it from the list of apps that comes up.

  2. 02

    Sign in to GitHub

    Click Add connection. A new tab opens on GitHub. Sign in with the account whose repos you want to automate, not a teammate's, because every step will act as that account.

  3. 03

    Grant access

    Approve the access Zapier asks for. The connection is then saved once and reused by every GitHub step you add later, in this Zap and in the next ones.

First Zap

Your first GitHub Zap: a welcome comment on outside pull requests

GoalWhen a new pull request opens, check who sent it and post a short welcome comment for outside contributors.

  1. 01

    Build: pick the trigger

    Create a Zap, choose GitHub, then New Pull Request. Select your GitHub connection, then the repository whose new pull requests should start the Zap.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent pull requests on that repo, so you build the rest on a real one instead of a blank.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then set the field to look at, the rule and the value. Text rules only work on text, so pick a text rule for an author name.

  4. 04

    Add the comment

    Add GitHub again with Create Comment, point it at the pull request from step 1 and write the welcome text. A filter makes this a multi-step Zap, so it needs a paid plan.

  5. 05

    Test, then publish

    Test the action once and check the comment on GitHub. If it reads the way you want, click Publish to switch the Zap on for good.

Triggers

The 20 GitHub triggers

20 events start a Zap when something happens in GitHub. Zapier checks for them at the interval your plan allows.

1

New Branch

Polling trigger

In Zapier“Triggers when a new branch is created.”

Starts your Zap whenever someone creates a branch on the repository you picked. It is the earliest sign that someone has started on a piece of work.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a product team that wants the matching ticket in its project tracker moved to in progress as soon as a developer branches off.
Watch out
never pair it with Create Branch on the same repo, or every branch the Zap creates sets it off again.
2

New Collaborator

Polling trigger

In Zapier“Triggers when you add a new collaborator.”

Fires each time you add a collaborator to a repository. It follows your own invitations, so it acts as a log of who you let in and when.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
an agency giving client developers access to a repo, and wanting a record kept outside GitHub for the account manager.
Watch out
it only sees collaborators added after the Zap is on, so anyone already on the repo is missing from your log.
3

New Commit Comment

Polling trigger

In Zapier“Triggers when a new comment on a commit is created.”

Picks up comments left directly on a commit, the remarks people write next to a specific change rather than in an issue thread. Those comments are easy to miss, and this trigger brings them out.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a tech lead who reviews code line by line and wants every commit remark copied somewhere the whole team checks daily.
Watch out
comments on issues and pull requests are not commit comments; for those, look at New Mention or New Repo Event instead.
4

New Commit

Polling trigger

In Zapier“Triggers when a new commit is created.”

Runs on every new commit in the repository you chose. It is the most granular view of work landing in the code, one Zap run per change.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a small documentation repo where each change should be announced to the support team, who need to know when help pages move.
Watch out
Create or Update File writes a commit itself, so using it on the same repo starts a loop that eats tasks fast.
5

New Repo Event

Polling trigger

In Zapier“Triggers when anything happens on a repo.”

The broadest trigger on the list: it fires when anything at all happens on one repository. Pushes, comments, new issues, all of it lands in the same Zap.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
an activity feed for a client-facing repo, where an account manager wants to see that work is moving without opening GitHub.
Watch out
on a busy repo, every event becomes a run; add a filter to keep only the kinds you care about (paid plan).
6

New Gist

Polling trigger

In Zapier“Triggers when you add/star a gist (public or private).”

Fires when you add a gist or star one, public or private. Gists are GitHub's small standalone snippets, outside any repository, and this trigger turns them into a personal collection.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a developer advocate who stars useful snippets during the week and wants them gathered into a shared reading list for the team.
Watch out
starring counts as well as creating, so a Zap meant for your own gists will also catch the ones you only bookmarked.
7

New Global Event

Polling trigger

In Zapier“Triggers when anything happens from or to you, on any repo.”

Unlike New Repo Event, this one is not tied to a single repository. It follows activity from you or to you across every repo your account touches.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a freelance developer working across several client organizations who wants one personal timeline of everything that happened that day.
Watch out
the required Actor of Event setting makes you choose: events you performed or events you received, never both in the same Zap.
8

Issue Closed

Polling trigger

In Zapier“Triggers when an issue is closed.”

Waits for the end of an issue's life rather than its start. Each time an issue is closed on the repository you picked, the Zap runs.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a customer success team that promised to get back to a user once their bug report was handled, and wants a reminder to do it.
Watch out
issues closed before the Zap went live never show up, so do not count on it to clean up an old backlog.
9

New Issue

Polling trigger

In Zapier“Triggers when a new issue is created.”

The trigger most GitHub Zaps start with. A new issue appears on the repository you picked, and the Zap starts from it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
an open-source maintainer who wants every incoming bug report labeled and copied into the team's planning board before morning stand-up.
Watch out
if another Zap creates issues on the same repo through Create Issue, the two can feed each other in a loop.
10

New Label

Polling trigger

In Zapier“Triggers when a new label is created.”

Fires when someone creates a label on a repository. Labels are how many teams encode priority, area or status, so a new one usually means a new way of sorting work.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
an engineering manager who keeps a single list of approved labels and wants to hear when someone invents one on their own.
Watch out
it reacts to the label being created, not to a label being put on an issue; those are two different events.
11

New Mention

Polling trigger

In Zapier“Triggers when your Github username is mentioned in a Commit, Comment, Issue or Pull Request.”

Catches every place your GitHub username gets mentioned: in a commit, a comment, an issue or a pull request. It is the trigger for people who get pinged more than they can read.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a CTO who lives in other tools most of the day and wants direct mentions pushed to the inbox they actually check.
Watch out
it follows the username of the connected account only, so a teammate's mentions need their own connection and Zap.
12

New Milestone

Polling trigger

In Zapier“Triggers when a new milestone is created.”

Runs when a milestone is created on a repository. Milestones group issues toward a deadline or a version, so this is the moment a new piece of planning starts.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a product owner who mirrors each new milestone as a project in the roadmap tool that leadership reads.
Watch out
it sees creation only; moving a milestone's date or closing it later will not start the Zap.
13

New Notification

Polling trigger

In Zapier“Triggers when a new notification is created.”

Pulls in the notifications GitHub generates for your account. Each new one starts a run.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a solo maintainer who wants GitHub alerts sorted and forwarded to one daily digest instead of chasing them across tabs.
Watch out
notifications can come in bursts after a busy day, and Zapier's flood protection may hold a very large batch back.
14

New Organization

Polling trigger

In Zapier“Triggers when a new organization is created.”

Fires when a new organization is created. Organizations are the shared accounts that own team repositories, so this trigger watches the top level of your GitHub setup.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
an IT lead who wants every new organization logged for an access review, before repos start appearing inside it.
Watch out
organizations created before the Zap was on never come through, so take a manual inventory first.
15

New Pull Request

Polling trigger

In Zapier“Triggers when a new pull request is created.”

Opening a pull request sets this one off. A pull request is a request to merge a set of changes into a branch, and for most teams that is the moment review work begins.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a startup with a small dev team that wants each new pull request posted where the reviewers already talk, with a link and the author.
Watch out
do not pair it with Create Pull Request on the same repo, or each pull request the Zap opens triggers it again.
16

New Release

Polling trigger

In Zapier“Triggers when a new release is added.”

Runs each time a release is added to the repository. Releases are the tagged versions you ship, usually with notes attached, which makes this trigger a natural changelog feed.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a SaaS company that wants release notes turned into a customer update or a help-center draft without someone copying them by hand.
Watch out
it reacts to new releases only; edits to an existing release's notes will not start a new run.
17

New Repository

Polling trigger

In Zapier“Triggers when a new repository is created.”

Watches for repository creation. It covers the place where projects are born, before a single line of code is pushed.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a dev agency that opens one repo per client project and wants the matching folder, channel or project card set up from it.
Watch out
a bulk migration that creates many repos at once can trip Zapier's flood protection and stall the batch.
18

New Review Request

Polling trigger

In Zapier“Triggers when a review is requested from you or a specified user.”

A review request on a pull request starts this one, whether it is addressed to you or from a user you name in the setup. It turns review requests into tasks you cannot overlook.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a senior engineer who wants every review request added to their personal to-do list, so code does not sit waiting on them.
Watch out
pick the right person in the setup; leaving it on yourself will miss requests sent to a colleague you cover for.
19

New Team

Polling trigger

In Zapier“Triggers when you are added to a team.”

Triggers when your account is added to a team inside an organization. Teams decide which repos you can reach, so joining one often changes your access.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a contractor who joins several client teams over a year and wants each one logged with the date for their own records and invoicing.
Watch out
it is about the connected account joining a team, not about any team being created in the organization.
20

New Watcher

Polling trigger

In Zapier“Triggers when a new watcher is added to a repo.”

Every time a person starts watching a repository, this trigger runs. Watching means they asked GitHub to keep them posted on its activity. On a public project, that is a signal of interest.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a developer-tools company tracking who follows its open-source repo, to feed a list the community manager reviews each week.
Watch out
watchers who joined before the Zap went live stay invisible to it; nothing is picked up from the past.
Actions

The 12 GitHub actions

GitHub gives you 12 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Labels to Issue

Action

In Zapier“Add labels to an existing issue without removing existing labels.”

Puts one or more labels on an existing issue and leaves the labels already there in place. You must tell it which issue.

When to use it
tagging every issue that comes from your customer form as customer-reported, so the team can filter them in one click.
Watch out
it only adds and never takes a label off, so a wrong label stays until someone removes it.
2

Create Comment

Action

In Zapier“Creates a new comment in an Issue or Pull Request.”

Posts a comment on an issue or a pull request. The only thing it insists on is knowing which one, so map that from the trigger or a search.

When to use it
telling a bug reporter on GitHub that support has replied to them elsewhere, so the thread stays complete for the developers.
3

Create Branch

Action

In Zapier“Creates a new branch in a GitHub repository.”

Creates a new branch in a repository. It needs three things: the repository, the new branch name, and the branch or commit to start from.

When to use it
a ticket moved to in progress in your project tool opens a branch named after it, so developers start from the right place.
Watch out
the source branch must exist, or there is nothing to copy from.
4

Create or Update File

Action

In Zapier“Creates a new file or updates an existing file in a GitHub repository.”

Writes a file into a repository: it creates it if the path is new, or replaces the content if the file is already there. Every write comes with a commit message you set.

When to use it
keeping a changelog or a status file in the repo updated from content written in another tool.
Watch out
to update an existing file, run Get File Contents first to fetch the SHA the update requires.
5

Delete Branch

Action

In Zapier“Deletes an unwanted branch.”

Removes a branch you no longer need. The branch name is the one required field, so map it carefully.

When to use it
clearing a feature branch once its ticket is archived in your project tool, so the branch list stays short.
Watch out
a wrong mapping deletes the wrong branch, so test the Zap on a throwaway branch first.
6

Create Gist

Action

In Zapier“Creates a new gist.”

Saves text as a new gist, with a filename and content. You decide whether the gist is public and shareable or kept private.

When to use it
turning a snippet saved in a notes app into a gist you can link from documentation or a support answer.
Watch out
the public option makes the gist accessible and shareable, so leave it off for internal snippets.
7

Create Issue

Action

In Zapier“Create a new issue.”

Opens a fresh issue on the repository of your choice, filled with what you map in from earlier steps.

When to use it
a bug report form on your website that should land straight in the engineering backlog, with the reporter's details kept in the description.
Watch out
if the same request can arrive twice, Find or Create an Issue is the safer choice.
8

Create Pull Request

Action

In Zapier“Create a new pull request and merge it (optional).”

Opens a new pull request, and can also merge it right away if you choose that option. Leave it unset and a human still reviews.

When to use it
a content team that edits files through a Zap and wants each change proposed as a pull request for a developer to approve.
Watch out
turning on the merge skips review entirely; keep it for changes nobody needs to read.
9

Set Profile Status

Action

In Zapier“Sets your GitHub profile status.”

Changes the status shown on your GitHub profile, and can flag you as busy through the Limited Availability option.

When to use it
switching your status to busy when a calendar event marked as focus time starts, so teammates know a review may wait.
Watch out
it changes the profile of the connected account only, never a colleague's.
10

Submit Review

Action

In Zapier“Submits a pull request review”

Submits a review on a pull request in the name of the connected account. Two fields are required: the pull request and the review action itself.

When to use it
recording an approval on GitHub when a manager signs off in a separate approval tool, without opening GitHub.
Watch out
the review counts as yours, so connect the account that is actually entitled to approve.
11

Update Issue

Action

In Zapier“Update an existing issue.”

Changes an issue that already exists, with whatever the step lets you edit. Point it at the issue first: that field is required.

When to use it
updating the GitHub issue once the matching support ticket is marked solved elsewhere.
Watch out
the issue usually comes from a Find Issue step, which makes the Zap multi-step and paid.
12

Update Pull Request

Action

In Zapier“Update an existing pull request.”

Edits a pull request that is already open. Like its issue counterpart, it needs to know exactly which pull request to touch.

When to use it
updating a pull request once its design is signed off in another tool.
Watch out
the pull request usually comes from a Find Pull Request step, which makes the Zap multi-step and paid.
Searches

The 8 GitHub searches

8 search steps look for data that already exists in GitHub, so a later step can use it.

A search step looks something up in GitHub and passes what it found to the next step. In the editor, GitHub's searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the lookup does not go as planned.

1

Find Branch

Search

In Zapier“Finds a branch in a GitHub repository by name, or lists all branches.”

Looks for a branch by name in a repository, or lists every branch when you leave the name out. The repository is required.

When to use it
checking that a branch exists before Create Pull Request points at it, so the Zap does not fail halfway.
2

Get File Contents

Search

In Zapier“Retrieves the content, SHA, and metadata of a file in a GitHub repository. Useful for fetching the SHA required to update an existing file. Note: decoded_content is UTF-8 text and will be lossy for binary files — use content (base64) or download_url for those.”

Reads a file in a repository and hands back its content and its SHA, the identifier an update of that file asks for. Give it a folder path instead and it returns every entry inside.

When to use it
right before Create or Update File, to fetch the SHA an update of an existing file requires.
Watch out
the readable text version suits text files only; images and other binary files come back garbled there.
3

Check Organization Membership

Search

In Zapier“Finds a specific members.”

Tells you whether a given user belongs to an organization. You supply the organization name and the user's login.

When to use it
in the welcome Zap above, to tell a teammate's pull request from an outside contributor's.
Watch out
if your account is not in that organization, only public members can be confirmed.
4

Find Organization

Search

In Zapier“Find an organization, whether or not you are a member.”

Finds an organization by its name, whether or not your account is a member. Handy to fetch details before a later step uses them.

When to use it
enriching a new client record with their GitHub organization before you invite anyone to it.
5

Find Repository

Search

In Zapier“Find a specific repository”

Locates a specific repository from its name, so later steps can point at it without you hard-coding it in each one.

When to use it
a Zap where the project name arrives from a form and each action must land in the repo that matches.
6

Find Issue

SearchFind or create

In Zapier“Finds a specific repo issue.”

Finds one issue in a repo, using three required settings: its state, what to search by and the value to match. Its variant Find or Create an Issue is the same search with the creation box ticked: it opens the issue, by title, when none matches.

When to use it
before Update Issue, or to avoid opening the same bug twice from repeated form entries.
7

Find Pull Request

SearchFind or create

In Zapier“Finds a specific repo pull.”

Tracks down one pull request in a repo, with the same three required settings as Find Issue. Tick the creation box and you get Find or Create a Pull Request, which opens one by title if nothing matches; it is the same search, not an extra operation.

When to use it
feeding Update Pull Request or Submit Review the right pull request.
8

Find User

Search

In Zapier“Finds a specific user.”

Finds a GitHub user so later steps can use their account details.

When to use it
matching a teammate in another tool to their GitHub account before a step that needs their login.
Watch out
if nobody matches, the Zap stops there unless you switch on the setting for empty results.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, an empty search stops the Zap right there and the steps that needed the result are skipped. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: the setting above disappears and the step asks for what it needs to create the missing item.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When a GitHub Zap breaks

Zapier ties no help article of its own to GitHub, so the traps below are Zapier's general limits, as they play out on repos.

Four of Zapier's general limits catch GitHub Zaps out, and they are worth knowing before you publish. For a deeper diagnosis, the Zapier troubleshooting page walks through the checks.

  • Old issues never come through

    A Zap only reacts to what happens after it is switched on. Issues, releases or pull requests that already existed stay out; moving that backlog is a separate job.

  • The Zap triggers itself

    A Zap that writes where its own trigger watches (New Branch with Create Branch, New Commit with Create or Update File on one repo) restarts itself and burns tasks.

  • A bulk import gets held back

    After a migration or a bulk import, a trigger can suddenly return a huge batch. Zapier's flood protection may hold it back instead of running every item.

  • Nothing runs twice, on purpose

    On a polling trigger, Zapier remembers what it has already seen. An issue that was edited does not come back as new, so do not expect a second run.
Need help

Need help automating GitHub with Zapier?

A person reads every message.

FAQ

GitHub Zapier integration: your questions

01Is the GitHub Zapier integration free?
Yes, as long as your Zap has two steps. GitHub is not a premium app, so it runs on the free plan, which gives you 100 tasks a month and unlimited Zaps. The catch is the step limit: the free plan builds one trigger plus one action, nothing more. As soon as you add a filter, a search such as Find Issue, or a second action, the Zap becomes multi-step and needs a paid plan. Plenty of useful GitHub Zaps fit in two steps, like New Issue into Add Labels to Issue.
02How many tasks does a GitHub Zap use?
One per action that completes successfully, and nothing for the trigger. Zapier can check your repos as often as your plan allows without billing you for the checks. A Zap with New Pull Request and Create Comment costs one task per pull request. Add a second action and it costs two each time. An action that fails, for example because the branch it needed was gone, is not counted against your plan. A handful of apps and actions take more than one task, so watch your usage in the first week.
03Does GitHub trigger Zapier in real time?
No. All 20 GitHub triggers are polling triggers: Zapier asks GitHub for new items on a timer rather than being told the moment something happens. How often depends on your plan: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. On paid plans you can change the interval and also run a check by hand from the editor. If minutes matter, plan for that delay in whatever the Zap does next, for instance in what you promise a user.
04What does it take to connect GitHub to Zapier?
A GitHub account, plus read or write access on any repository you do not own and want the Zap to touch. The connection itself takes three moves: Apps, then + Add connection, then sign in to GitHub in the tab that opens and grant access. Use the account the actions should act as, since comments, reviews and new branches will all carry its name. Once saved, that connection is reused by every GitHub step you add, in this Zap and in later ones.
05Why does a GitHub Zap keep running on its own?
Because it is probably writing where its own trigger is looking. Pair New Branch with Create Branch, New Issue with Create Issue, or New Commit with Create or Update File on the same repository, and each action creates exactly the kind of item that starts the Zap again. Every loop costs tasks, so a free allowance of 100 can disappear quickly. Point the action at a different repo, or add a filter (paid plan) that lets through only the items a person created.
06What if the GitHub action you need is not in Zapier?
Check the searches first, since several needs are covered there rather than in the action list, like Get File Contents or Check Organization Membership. If it is still missing, Zapier simply does not offer it for GitHub today: there are 12 actions and 8 searches, and that is the full list. You can then ask whether the job really belongs in GitHub, or look at whether another automation tool exposes that operation, using the same checks this page used for Zapier.
07Zapier, Make or n8n for GitHub?
It depends on three criteria rather than on a ranking. First, delay: on Zapier every GitHub trigger polls, so ask how long each tool waits before reacting. Second, steps: Zapier's free plan stops at two, so count the filters and searches your scenario needs. Third, coverage: compare the exact operation names you need, such as Submit Review or Create or Update File, against each tool's list. Lined up on those three points, the tools tell you more than any general verdict.
Same platform

Other docs you might need on this stack.

Browse all integrations