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.
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.
Use this GitHub Slack integration for release announcements, weekly merged changes and customer feature requests.
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, Leta reads the pull requests merged into main that week and posts a plain-English list of the merged changes to #marketing.
Mention @Letaido with a customer request; Leta updates a matching GitHub issue or opens one, then replies with its link.
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's own Slack app posts repo notifications. Jobs that need judgement sit on top.
| Option | GitHub updates in Slack | Act on GitHub from Slack | Runs on its own | Fires on each GitHub event | Rewrites for non-developers |
|---|---|---|---|---|---|
| Yes | Yes | Yes | Partly | Yes | |
| GitHub app for Slack | Yes | Yes | Yes | Yes | Partly |
| Zapier | Yes | Partly | Yes | Partly | Partly |
| Slack GitHub Action | Yes | No | Yes | Partly | No |
| Option | Direction | What starts it | Best for | Watch out for |
|---|---|---|---|---|
| Letaido AI agent | GitHub to Slack, and Slack requests into GitHub issues | A GitHub event such as a release, a schedule, a mention in Slack, or when you ask | Jobs 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 done | Not 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 Slack | GitHub to Slack, plus slash commands and Copilot from Slack | Repo activity you subscribe a channel to, or you typing /github or mentioning @GitHub | Developer notifications for issues, pull requests, commits, releases and deployments, link previews, opening issues from a message, Copilot in threads | A Slack admin installs it. Notifications follow GitHub's own format. Copilot features need an eligible GitHub Copilot plan |
| Zapier | GitHub to Slack, or Slack messages into GitHub issues, one recipe at a time | A GitHub trigger checked on a polling interval, or a Slack event | Fixed recipes such as a Slack message for each new release, commit, pull request or issue | GitHub triggers are polling: Zapier checks for new data on an interval, every 15 minutes on its lowest plan |
| Slack GitHub Action | GitHub Actions to Slack | A step in a GitHub Actions workflow | Build and deploy messages: sends data to Slack through a webhook, a Slack API method or Workflow Builder | Set up by a developer in the workflow file, with a Slack token or webhook URL stored as a secret |
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”.
Saved as an automation, like “Weekly merged changes digest in Slack”: every Friday at 3pm.
Ask in chat; Leta picks from 114 actions.
Allow all read operations once per app; approve each kind of write once.
List commit comments · Add commit comment · Get release · List workflow run jobs
Get team info · Post message · Remove bookmark · Edit message
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.
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.
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.
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.
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.
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.
Allow all read operations once per app; approve each kind of write once.
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