Explore Plans

GitHub to MESH integrations

Create an issue to GitHub using MESH. Already built and ready to turn on, one of 3 for GitHub and MESH on IFTTT.
Get started todayGet started today

Automate GitHub and MESH from your AI assistant

Have Claude, ChatGPT, or Cursor build and run GitHub and MESH automations for you, like “Create an issue to GitHub using MESH”, with IFTTT MCP.

Set up IFTTT MCP

Create your own GitHub and MESH workflow

Create custom workflows effortlessly by selecting triggers, queries, and actions. With IFTTT, it's simple: “If this” trigger happens, “then that” action follows. Streamline tasks and save time with automated workflows that work for you.

27 triggers, queries, and actions

Any new closed issue

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time any issue is closed in a repository you own or collaborate on.

Any new commit

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time a new commit in a repo is created on Github.

Any new Gist

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time you create a new Gist on Github.

Any new issue

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time any new issue is opened in a repository you own or collaborate on.

Any new notification

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires every time you receive a new notification on Github.

Any new notification from a repository

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time you receive a new notification from a specific repository on Github.

Any new release

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time a repo release a new version on Github.

Any new repository event

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires every time a new event occurs in a repository.

Event from MESH app received

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time your IFTTT Tag on MESH app receives an input signal from the other Tag.

New issue assigned to you

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time a new issue is assigned to you.

New pull request for a specific repository

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time a new pull request is opened for a repository you specify.

New repository by a specific username or organization

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time a new repository is created by the username or organization you specify.

History of closed issues

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of every time any issue is closed in a repository you own or collaborate on.

History of events from MESH app

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times when your IFTTT Tag on MESH app receives an input signal from the other Tag.

History of issues

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of every time any new issue is opened in a repository you own or collaborate on.

History of issues assigned to you

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of every time a new issue is assigned to you.

History of pull requests for a specific repository

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of every time a new pull request is opened for a repository you specify.

History of repositories by a specific username or organization

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of every time a new repository is created by the username or organization you specify.

List Gists.

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of Gists owned by the current user.

List starred Gists

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of Gists starred by the current user.

List starred repos

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of repositories starred by the current user.

List watched repos

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of repositories watched by the current user.

Lists users that have starred the repository

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of users that have starred the repository.

Create an issue

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will create a new issue for the repository you specify.

Create an issue/pull request comment

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will comment in a specific issue or pull request on Github.

Create new Gist

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will create a Gist for you.

Send an event to MESH app

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will send an event to MESH app.

Any new closed issue

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time any issue is closed in a repository you own or collaborate on.

Any new commit

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time a new commit in a repo is created on Github.

Any new Gist

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time you create a new Gist on Github.

Any new issue

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time any new issue is opened in a repository you own or collaborate on.

Any new notification

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires every time you receive a new notification on Github.

Any new notification from a repository

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time you receive a new notification from a specific repository on Github.

Any new release

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time a repo release a new version on Github.

Any new repository event

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires every time a new event occurs in a repository.

Create an issue

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will create a new issue for the repository you specify.

Create an issue/pull request comment

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will comment in a specific issue or pull request on Github.

Create new Gist

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will create a Gist for you.

Event from MESH app received

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This Trigger fires every time your IFTTT Tag on MESH app receives an input signal from the other Tag.

Build an automation in seconds!

You can add delays, queries, and more actions in the chat.

GET STARTED

How to connect to a GitHub automation

Find an Applet using GitHub and MESH

Find an automation to connect to, or create your own!

Connect IFTTT to your accounts

Securely connect the Applet services to your respective accounts.

Finalize and customize your Applet

Review trigger and action settings, and click connect. Simple as that!
Get started

Make more happen with your credits

  • Connect to more Applets

    More credits, more possibilities

    Get more credits per month to power more automation activity.
  • If a new calendar event is added, with an AI prompt, then an AI agent runs actions across your services

    Power more advanced automations

    Use credits to power your automations, including actions that require more processing.
  • Get access to faster speeds

    Access faster speeds and higher rate limits

    Get faster updates and more actions with increased rate limits and more frequent checks.

More on GitHub and MESH

About GitHub

GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Turn on Applets to automatically track issues, pull requests, repositories, and to quickly create issues.

Explore GitHub

More integrations with GitHub

About MESH

MESH makes the world around you come to life. With 7 physical MESH 'tags' and an easy-to-use companion iOS app (free), the MESH system gives you the power to enhance your DIY projects with fun interactivity.

Explore MESH

More integrations with MESH

IFTTT helps all your apps and devices work better together

Get started for free