Email me when I'm assigned a new GitHub issue
Other popular GitHub workflows and automations
-
171
-
-
Post new GitHub pull requests to Slack channel
43
-
-
Tweet automatically when a new GitHub repository is created
29
-
-
Add new GitHub issues to a weekly email summary
315
-
-
Post new GitHub issues to Slack channel
233
-
-
Get a Pushover alert for new GitHub issues
10
-
-
Create a Todoist task for new GitHub issues assigned to you
557
-
-
Create a GitHub issue for each new Blogger post
95
-
-
Create a GitHub issue for each new YouTube upload
85
-
Automate GitHub and MeshTek from your AI assistant
Ask ChatGPT to create GitHub applets that track pull requests, issues, and releases, all from your AI assistant with IFTTT MCP.
Set up IFTTT MCP
Create your own GitHub and MeshTek 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.
33 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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires every time a new event occurs in a repository.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 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.
Apply Normal Effects
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 apply a selected normal effect to selected Meshtek device.
Apply Special Effects
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 apply a selected special effect to selected Meshtek device.
Apply Static Preset
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 apply a Static effect to selected Meshtek device.
Apply Strip Effects
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 apply a selected strip effects to selected Meshtek device.
Apply White
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 apply white to selected Meshtek device.
Blink Lights
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 blink selected Meshtek device on and off to a specified Color and times.
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.
Lights Off
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 turn off your selected Meshtek device.
Lights On
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 turn on selected Meshtek device to the chosen default lighting setting.
Set Color
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 turn on or change selected Meshtek device to a specified color.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
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 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires every time a new event occurs in a repository.
Apply Normal Effects
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 apply a selected normal effect to selected Meshtek device.
Apply Special Effects
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 apply a selected special effect to selected Meshtek device.
Apply Static Preset
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 apply a Static effect to selected Meshtek device.
Apply Strip Effects
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 apply a selected strip effects to selected Meshtek device.
Build an automation in seconds!
If
Select a trigger the automation will use
Any new closed issue
Any new commit
Any new Gist
Any new issue
Any new notification
Any new notification from a repository
Any new release
Any new repository event
New issue assigned to you
New pull request for a specific repository
New repository by a specific username or organization
Then
Select an action the automation will perform
Apply Normal Effects
Apply Special Effects
Apply Static Preset
Apply Strip Effects
Apply White
Blink Lights
Create an issue
Create an issue/pull request comment
Create new Gist
Lights Off
Lights On
Set Color
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 MeshTek
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!Upgrade your automations with
-
Connect to more Applets
Connect up to 20 automations with Pro, and unlimited automations with Pro+ -
Add multiple actions with exclusive services
Add real-time data and multiple actions for smarter automations -
Get access to faster speeds
Get faster updates and more actions with higher rate limits and quicker checks
GitHub and MeshTek tips, tools, and resources
-
Productivity
The 10 AI tools taking over your feed just joined your workflow
-
Business
20 business tools to automatically run and scale your business
-
Business
10 new tools for the work that keeps your business moving
-
Productivity
The ultimate automation stack in 2026
-
Popular
Automate your Discord server with IFTTT
-
Business
How to automate with AI in 2026
More on GitHub and MeshTek
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.
About MeshTek
The smartest lights on the planet are even smarter when used with IFTTT. Control your Meshtek device with your voice, trigger notifications, and automate your lighting to suit your fancy. Explore the possibilities and give life to light with Meshtek devices. Note: the Meshtek mobile app must be active and within range of your Meshtek device in order to execute IFTTT actions.