Discord to GitHub integrations Automate your workflows between Discord and Instagram with IFTTT.

Create your own Discord 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.

29 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 message in channel

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 when a new message is posted in a channel you select.

New pinned message in channel

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 when a new message is pinned in a channel you select.

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 Channel Invites

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 all invites to a channel.

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.

Post a message to a channel

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 message from the IFTTT Bot to the channel you specify.

Post a rich message to a channel

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 rich message from the IFTTT Bot to the channel you specify. Although most fields are optional, running the action requires content in the message body or content in at least one of the embed attributes.

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.

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.

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 Channel Invites

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 all invites to a channel.

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.

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 message in channel

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 when a new message is posted in a channel you select.

New pinned message in channel

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 when a new message is pinned in a channel you select.

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.

Post a message to a channel

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 message from the IFTTT Bot to the channel you specify.

Post a rich message to a channel

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 rich message from the IFTTT Bot to the channel you specify. Although most fields are optional, running the action requires content in the message body or content in at least one of the embed attributes.

Build an automation in seconds!

You can add delays, queries, and more actions in the next step!

GET STARTED

How to connect to a Discord automation

Find an automation using Discord

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

Connect IFTTT to your Discord account

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

Upgrade your automations with

Start your free trial

More on Discord and Instagram

About Discord

Whether you’re part of a school club, gaming group, worldwide art community, or just a handful of friends that want to spend time together, Discord makes it easy to talk every day and hang out more often.

To add the Bot, the user needs to have the Manage Server permission. Note: Revoking Discord Permissions will not stop the Bot from running. The Bot needs to be removed from the server or have its permissions disabled.

Connect Discord

More integrations with Discord

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.

Connect GitHub

More integrations with GitHub

Help