GitHub + Slack integration

Combine GitHub + Slack and move repo activity into channels where your team already talks. Just ask Letaido's AI agent and watch it do the work.

Best GitHub and Slack integration jobs to start with

Use this GitHub Slack integration for release announcements, weekly merged changes and customer feature requests.

When a release is published

Release announcement draft in Slack

When a GitHub release is published, Letaido turns the notes into a short customer-facing announcement and posts it to Slack for review.

Every Friday at 3pm

Weekly merged changes digest in Slack

Every Friday, Leta reads the pull requests merged into main that week and posts a plain-English list of the merged changes to #marketing.

When someone mentions Letaido

Slack feature requests as GitHub issues

Mention @Letaido with a customer request; Leta updates a matching GitHub issue or opens one, then replies with its link.

When a requested feature is done

Tell sales when a requested feature is done

When a feature-request issue is closed as completed, Leta posts the customers who asked to #sales, tagging teammates whose Slack ID was logged.

GitHub Slack integration options, compared

GitHub's own Slack app posts repo notifications. Jobs that need judgement sit on top.

OptionGitHub updates in SlackAct on GitHub from SlackRuns on its ownFires on each GitHub eventRewrites for non-developers
Letaido AI agentYesYesYesPartlyYes
GitHub app for SlackYesYesYesYesPartly
ZapierYesPartlyYesPartlyPartly
Slack GitHub ActionYesNoYesPartlyNo
Read the full comparison
OptionDirectionWhat starts itBest forWatch out for
Letaido AI agentGitHub to Slack, and Slack requests into GitHub issuesA GitHub event such as a release, a schedule, a mention in Slack, or when you askJobs for the people who announce releases: release drafts, a weekly list of merged changes, feature requests logged from Slack, sales told when a request is doneNot a feed of every commit or pull request. Jobs that start on a GitHub event need a token with the Webhooks permission, and the bot must be invited to each channel
GitHub app for SlackGitHub to Slack, plus slash commands and Copilot from SlackRepo activity you subscribe a channel to, or you typing /github or mentioning @GitHubDeveloper notifications for issues, pull requests, commits, releases and deployments, link previews, opening issues from a message, Copilot in threadsA Slack admin installs it. Notifications follow GitHub's own format. Copilot features need an eligible GitHub Copilot plan
ZapierGitHub to Slack, or Slack messages into GitHub issues, one recipe at a timeA GitHub trigger checked on a polling interval, or a Slack eventFixed recipes such as a Slack message for each new release, commit, pull request or issueGitHub triggers are polling: Zapier checks for new data on an interval, every 15 minutes on its lowest plan
Slack GitHub ActionGitHub Actions to SlackA step in a GitHub Actions workflowBuild and deploy messages: sends data to Slack through a webhook, a Slack API method or Workflow BuilderSet up by a developer in the workflow file, with a Slack token or webhook URL stored as a secret

GitHub and Slack: the old way vs. Letaido

  1. 1Open the release
  2. 2Read the dev notes
  3. 3Rewrite for customers
  4. 4Paste it in Slack
When a new release is published on acme/app, read its notes and write a short, benefit-led announcement for customers: what's new and why it matters, no internal jargon. Post it to #product-marketing as a draft for us to review.
#product-marketing in Slack
Draft for review: v4.2.0
Shared dashboards: send a read-only link to anyone, no login needed; CSV export now keeps your filters, so the file matches what you see; Faster search on large workspaces
Full notes: v4.2.0 release on GitHub

How GitHub and Slack jobs start

When something happens

A job can start when a GitHub release is published or someone mentions @Letaido in Slack or a feature-request issue is closed as completed in GitHub, like “Release announcement draft in Slack”.

On a schedule

Saved as an automation, like “Weekly merged changes digest in Slack”: every Friday at 3pm.

When you ask

Ask in chat; Leta picks from 114 actions.

All 11 Slack events · All 13 GitHub events

How to set up the GitHub Slack integration

  1. 1Install the GitHub App or paste a token
  2. 2Create the Slack app from Letaido's manifest
  3. 3Approve the first GitHub and Slack run

    Allow all read operations once per app; approve each kind of write once.

  4. 4Watch the first run in chat
  5. 5Choose when it runs

Every GitHub and Slack action the agent can take

GitHub
13 groups: 31 reads, 19 writes
  • Read issues and search
  • Manage branches and files
  • Monitor GitHub Actions workflows
  • 10 more

List commit comments · Add commit comment · Get release · List workflow run jobs

Slack
10 groups: 27 reads, 37 writes
  • Post and manage messages
  • Create and edit canvases
  • Look up and manage users
  • 7 more

Get team info · Post message · Remove bookmark · Edit message

Frequently asked

Does GitHub integrate with Slack? +

Yes. GitHub's own Slack app posts repo notifications and lets you open issues from Slack. Letaido's AI agent, Leta, adds jobs on top for the people who announce releases, and the jobs on this page have been checked step by step.

How do I connect GitHub and Slack to Letaido? +

Connect each app once in Letaido and invite the Letaido bot to the Slack channels it should post in. Then describe the job in chat, or paste a prompt from a job on this page.

Is there a way to send GitHub notifications to Slack automatically? +

Yes, for the jobs you set up: a draft announcement when a release is published, a list of the week's merged changes every Friday, or a post to #sales when a requested feature is done. It is not a feed of every commit or pull request.

Can I turn a Slack message into a GitHub issue? +

Yes. Mention @Letaido with a customer request and Leta searches open feature-request issues first. It comments on the match, or opens a new issue, and replies in the thread with the link. The feature-request label must already exist on the repo.

What do GitHub event jobs need to run? +

Jobs that start on a GitHub event, such as a published release or a closed issue, need a GitHub token with the Webhooks permission. Mention jobs also need the app_mention event on in your Slack app.

How is Letaido different from the GitHub app for Slack? +

The GitHub app for Slack posts repo activity in GitHub's own format and runs slash commands. Leta runs a job you describe, on a GitHub event, a schedule, a mention or when you ask, and rewrites releases and merged changes for people who don't read pull requests.

Will it ask before it posts in Slack or changes GitHub? +

Allow all read operations once per app; approve each kind of write once.

Put GitHub and Slack to work today

Connect GitHub and Slack, then ask for a job like "Draft a Slack announcement for each GitHub release". Leta gets it done the moment something happens, or the moment you ask.

Get Letaido