Skip to content
ClickRuntime

Connect GitHub to Slack

Engineering work happens in GitHub, but the conversation about it happens in Slack. Connecting them puts new issues, pull requests, failing builds and risky dependencies in front of the team where they already talk, with enough context to act without switching tabs.
Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Ideas

What you can do with GitHub and Slack

Digests, issue triage, pull request reviews, CI and dependency alerts, and backups, from GitHub to Slack. These are ready-made starting points. Anything else you can describe works too.
On a schedule

Back up exports to GitHub each night

Every night your configuration or workflow exports are saved to a GitHub repository, and Slack lists exactly what changed.

See how it works
Daily

Post a daily engineering digest from GitHub in Slack

Each morning before standup, Slack shows what merged yesterday, which pull requests are waiting for review and which issues were opened.

See how it works
The moment it happensAI

Turn new errors into GitHub issues with a Slack alert

Each new kind of error opens a GitHub issue with a likely cause, and the team is told in Slack. Repeats of a known error are not filed again.

See how it works
The moment it happensAI

Get an AI first review on every pull request

Each new pull request gets a review comment pointing out likely bugs and risks, and Slack shows a one-line verdict with the link.

See how it works
On a schedule

Get Slack alerts for risky dependencies

Each day Slack lists new security alerts for packages and GitHub Actions used in your repositories, most severe first.

See how it works
The moment it happensAI

Summarise documentation changes in Slack

When someone changes the docs in GitHub, Slack gets a short plain-language summary of what changed and why it matters.

See how it works
The moment it happensAI

Triage new GitHub issues with AI and flag urgent ones

Every new GitHub issue is labelled by type and priority, possible duplicates are noted, and urgent ones are posted to Slack.

See how it works
Daily

Track flaky CI jobs in GitHub Actions

Each morning Slack lists the GitHub Actions workflows that failed and then passed on a re-run in the last week, so you know which tests are flaky.

See how it works
The moment it happens

Post merged GitHub pull requests to Slack

Each merged pull request is posted to a Slack channel with title, author, lines changed and link.

See how it works
The moment it happens

Post new GitHub stars to a Slack channel

When someone stars your GitHub repo, a Slack message shows who it was, their company and follower count and the new star total.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with GitHub and Slack, plus any other app. Describe it and your assistant builds it.

See how to build your own

More ideas

On a schedule

Remind reviewers in Slack about open GitHub pull requests

Each weekday morning, reviewers with pull requests waiting more than a day are mentioned by name in a Slack channel.

See how it works
Each new issueAI

Triage new GitHub issues

Each new issue gets an AI summary and suggested label, posted to your team's Slack channel.

See how it works

Build your own

Build any GitHub and Slack automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what should happen between GitHub and Slack in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every weekday at 10am, post to #eng the pull requests waiting for review more than 24 hours, with author and reviewers.

When a pull request touches files under /migrations, post it to #db-review and mention the database owners.

Use cases

Why people connect GitHub and Slack

How the two apps work together

  • GitHub webhooks send issues, pull requests, releases and workflow runs to a ClickRuntime trigger link instantly.
  • The script formats each event and posts it to a Slack channel or DM.
  • Scheduled runs can query GitHub for digests, such as open pull requests waiting for review.

  • Pull request review requests

    Engineering teams post new pull requests to a channel. Reviewers see the title, author and changed files.

  • Release announcements

    Product and support teams want to know what shipped. A release post with AI-summarised notes goes to #releases.

  • Failed workflow alerts

    When a GitHub Actions run fails on main, the team gets a Slack post with the job and a link.

  • Issue triage for open source

    Maintainers get new issues posted with AI labels such as bug, question or feature request.

More apps

GitHub, Slack and other apps in one automation

An automation isn't limited to two apps. Add the next step in another app and it runs as part of the same automation.

Merged PRs close Linear issues

When a GitHub pull request is merged, mark the Linear issue named in its title as Done and post it in #eng on Slack.

Bug issues to Jira with Slack notice

When a GitHub issue gets the bug label, create a Jira bug with the details and post the link in #triage on Slack.

Release health in Slack

When a GitHub release is published, wait an hour, check Sentry for new errors in that release, and post the count in #releases.

Setup

Connect GitHub and Slack once

Every idea on this page uses the same two connections, so you set them up once. If one is missing, your assistant tells you and links to the right place.

GitHub

Developer / Source control

  1. In GitHub, open your profile picture, then Settings, Developer settings, Personal access tokens, Fine-grained tokens, and choose Generate new token.
  2. Give it a name and an expiration, and choose the resource owner (you or your organization).
  3. Under repository access, pick only the repos the automation needs, then set the minimum permissions, such as Issues, Pull requests or Contents.
  4. Generate the token and copy it.
  5. In the ClickRuntime dashboard, open Connections & secrets and save the token as a secret for GitHub.

Slack

Team chat

  1. At api.slack.com/apps, create a new app from scratch in your workspace.
  2. Under OAuth & Permissions, add the bot scopes the automation needs, such as chat:write, channels:read and channels:history.
  3. In the ClickRuntime dashboard, open Connections, choose Slack and enter your app's details, then install it to your workspace.
  4. In each channel the automation should use, type /invite @your-app-name.

FAQ

Questions about connecting GitHub and Slack

How does ClickRuntime connect to GitHub?
Through a GitHub app or token you add in your ClickRuntime dashboard, limited to the repositories and permissions each automation needs, such as reading pull requests or writing issues.
Does it react instantly to new issues and pull requests?
Yes, for automations that start from a GitHub event. You add a webhook in the repository settings pointing to your automation's trigger link, and GitHub notifies it within seconds.
Can it post to private Slack channels?
Yes. Invite the ClickRuntime notifications app to the private channel and name the channel when you set up the automation.
Does it work with GitHub organisations and private repositories?
Yes. Grant access to the organisation's repositories when you connect GitHub, and the automation can read private repositories you allow.
Is our code sent to AI?
Only for automations that need it, such as pull request reviews and documentation summaries, and only the changed lines, trimmed to a sensible length. Digests and alerts that use AI send titles and short descriptions.
Can it DM reviewers?
Yes, if GitHub usernames are mapped to Slack users, which you can give the assistant.
Can it filter by repository or branch?
Yes. You can limit alerts to specific repos, branches, labels or authors.
Can it post a daily digest instead of every event?
Yes. Events can be stored and posted as one summary at a set time.

Related pages

Keep exploring

Tell your assistant what GitHub and Slack should do together

Free plan. No credit card.

Add to ChatGPTAdd to Claude