Start free
Per-pair page

GitHub + Slack: PR notifications you actually want.

Post GitHub PR, issue, and release events to Slack channels with custom routing, formatting, and review-reminder automation. More flexible than GitHub's default Slack app.

Connect Slack to GitHub — start free See reverse direction
Trigger app
Slack as the trigger

Workflows fire when something happens in Slack.

See all 13 triggers →
Action app
GitHub as the action

Workflows do something in GitHub, instantly.

See all 23 actions →
Connect Slack to GitHub — start free
Both directions

Pick the way that fits your stack.

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

Slack → GitHub

When something happens in Slack, do it in GitHub.

13 Slack triggers wired to 23 GitHub actions. Most-used pairing: App Home Opened → Add Labels.

GitHub → Slack

Or fire it the other way around.

1 GitHub triggers wired to 45 Slack actions downstream.

See GitHub → Slack →
Popular pairings

Common Slack → GitHub workflows.

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

Showing 9 of 299 combinations
When app home opened in Slack, add labels in GitHub.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app home opened in Slack, create comment in GitHub.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app home opened in Slack, create issue in GitHub.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app home opened in Slack, create or update file in GitHub.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app mentioned in Slack, add labels in GitHub.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When app mentioned in Slack, create comment in GitHub.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When app mentioned in Slack, create issue in GitHub.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When app mentioned in Slack, create or update file in GitHub.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When new channel in Slack, add labels in GitHub.

Fires when a new Slack channel is created in the workspace. Useful for auto-adding the bot, welcome messages, or governance audit logs.

How it works

Connect Slack and GitHub in five steps.

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

  1. 1
    Connect
    Authorize Slack and GitHub

    Open TinyCommand, authorize Slack and GitHub once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Slack trigger

    Drop the Slack → App Home Opened trigger onto the canvas. TinyCommand auto-registers the webhook.

    POST /v1/webhooks/slack.trigger-app-home-opened
  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 GitHub action

    Drop the GitHub → Add Labels action below it. Map fields from the Slack payload into the GitHub inputs.

    github.add-labels-to-issue
  5. 5
    Publish
    Publish and forget

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

FAQ

Questions about Slack + GitHub.

Why use a custom GitHub + Slack workflow over the GitHub Slack app?
GitHub's app gives basic per-repo notifications. Custom workflows let you route by repo + label, batch into digests, AI-summarize PRs, post review reminders on stale PRs, etc.
How do I post a Slack message when a GitHub PR needs review?
GitHub PR Review Requested → look up reviewer's Slack ID (via email lookup) → Slack Send DM with PR title, author, and link. Faster than waiting for email.
Can I post a daily Slack digest of open GitHub PRs?
Yes. Scheduled 9am: GitHub Search Issues for "is:open is:pr" → format as bullet list by author → Slack Send Message to #engineering. Daily review-queue checkpoint.
How do I escalate stale GitHub PRs in Slack?
Scheduled daily: GitHub Search "is:open is:pr updated:<7d" → for each, Slack DM the author and assignee. Or post to a #stale-prs channel for engineering manager visibility.
Can I AI-summarize a GitHub PR in the Slack message?
Yes. Insert Claude/OpenAI step between trigger and Slack Send Message. Summarize the diff in 1 sentence. Lets reviewers prioritize PRs based on what they actually do, not just titles.
How do I avoid Slack noise on every GitHub commit?
Filter triggers to significant events (PR opened, merged, release published). Skip per-commit. Aggregate into hourly or daily digests for low-priority signal.
Related

Other apps that pair well with Slack.

+
Slack + Gmail
Email
+
Slack + Google Sheets
Spreadsheets & Databases
+
Slack + HubSpot
CRM & Sales
+
Slack + Stripe
Payments
+
Slack + Notion
Productivity
+
Slack + Airtable
Spreadsheets & Databases
Connect Slack to GitHub — start free