Skip to content
Per-pair page

Discord + GitHub: developer activity in your community channels.

Post GitHub events (PRs, releases, deployments, issues) into Discord channels with rich embeds. Built for dev-tool communities, open-source projects, and async-first engineering teams.

Trigger app
GitHub as the trigger

Workflows fire when something happens in GitHub.

Action app
Discord as the action

Workflows do something in Discord, instantly.

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

GitHubDiscord

When something happens in GitHub, do it in Discord.

1 GitHub triggers wired to 8 Discord actions. Most-used pairing: New GitHub EventAdd Reaction.

DiscordGitHub

Or fire it the other way around.

3 Discord triggers wired to 23 GitHub actions downstream.

See DiscordGitHub
Popular pairings

Common GitHub → Discord workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 4 of 8 combinations
How it works

Connect GitHub and Discord in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize GitHub and Discord

    Open Tiny Command, authorize GitHub and Discord once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a GitHub trigger

    Drop the GitHub → New GitHub Event trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/github.trigger-event
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Discord action

    Drop the Discord → Add Reaction action below it. Map fields from the GitHub payload into the Discord inputs.

    discord.add-reaction
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about GitHub + Discord.

How do I post GitHub PR events into Discord?
GitHub PR Opened / Reviewed / Merged trigger → Discord Send Message with an embed showing title, author, status, and the PR URL. Pick the channel by repo or PR labels.
Can I announce GitHub releases in Discord?
Yes. GitHub Release Published → Discord Send Message in a #releases channel with the release name, body, and download link. Optionally @-mention a community-update role.
How do I create GitHub issues from Discord messages?
Discord Reaction Added (e.g., :bug:) → GitHub Create Issue with title from message text, body including author and original message URL. Reactions become the capture verb for triage-from-community.
Can I show GitHub commit notifications in Discord?
Yes — GitHub Push trigger → Discord Send Message with a compact embed (author, commit count, branch). For high-traffic repos, aggregate into a daily digest instead of per-push notifications.
How do I route different GitHub repos to different Discord channels?
Switch on the repo name in the trigger payload. Frontend repo → #frontend channel. Backend → #backend. Docs → #docs. One workflow, many destinations based on repo.
Can Discord reactions approve GitHub PRs?
Possible but risky — Discord reactions don't carry strong authentication. Better: link to the PR from Discord and have the reviewer click through. Reserve reactions for lightweight signals (acks, votes), not merge gating.
Related

Other apps that pair well with GitHub.


Wire GitHub to Discord in 2 minutes.

Free tier available. No credit card. No onboarding call.