Add iOS Reminders tasks for new GitHub issues assigned to you
by
About this Applet
Get instant updates on your Triby whenever a new GitHub issue is assigned to you. This automation sends a message to your chosen Triby device with details about the issue so you stay informed without checking GitHub. Ideal for keeping track of new tasks as soon as they come in.
If
Trigger ingredients
IssueTitle
IssueBody
IssueLabels
IssueURL
CreatedAt
AuthorUsername
AuthorAvatarImageURL
RepositoryName
Then
Action fields
Which Triby IO?
What message?
Services used in this Applet
You might also like...
-
674
-
-
Create a Todoist task for new GitHub issues assigned to youby
557
-
-
Create GitHub issue for new YouTube videoby
445
-
Related services
-
-
App store rating
Create your own Invoxia Triby and GitHub 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.
38 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.
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.
On button pressed
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
This trigger fires when you press a given button on your Triby IO.
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.
[Advanced] Execute a script on specified Triby IO
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 execute a script on a Triby IO you specify (advanced use, read the documentation available at www.invoxia.com/developers for more information).
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.
Play media URL on specified Triby IO
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 play a provided media URL, on a Triby IO you specify.
Play preset media on specified Triby IO
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 play a media among those already preset on a button, on a Triby IO you specify.
Send a message to every Triby IO
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 a given message to a every Triby IO you own.
Send a message to specified Triby IO
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 a given message to a Triby IO you specify.
Send a silent message to every Triby IO
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 a silent message to every Triby IO in your group.
Send a silent message to specified Triby IO
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 a silent message to a Triby IO you specify.
Send an image to every Triby IO
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 image to every Triby IO you own.
Send an image to specified Triby IO
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 image to a Triby IO you specify.
[Advanced] Execute a script on specified Triby IO
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 execute a script on a Triby IO you specify (advanced use, read the documentation available at www.invoxia.com/developers for more information).
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.
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
On button pressed
Then
Select an action the automation will perform
[Advanced] Execute a script on specified Triby IO
Create an issue
Create an issue/pull request comment
Create new Gist
Play media URL on specified Triby IO
Play preset media on specified Triby IO
Send a message to every Triby IO
Send a message to specified Triby IO
Send a silent message to every Triby IO
Send a silent message to specified Triby IO
Send an image to every Triby IO
Send an image to specified Triby IO
Start a call from specified Triby IO
Start a timer on specified Triby IO
Start an intercom call from specified Triby IO
Stop playing media on specified Triby IO
You can add delays, queries, and more actions in the chat.
More on Invoxia Triby and GitHub
About Invoxia Triby
Triby, by invoxia, is a smart hub for your home. With its unique audio technology, design, and E-ink display, Triby enhances the possible interactions with your connected environments and with your loved ones.
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.