Preview deploy alerts in Slack with PR context
When a Vercel preview build finishes, post a plain-English summary, the preview link, and the pull request to the right Slack channel.
Integrations
Vercel
GitHub
Slack
Type
Categories
- Engineering
- Product
I want an agent workflow that posts a stakeholder-friendly heads-up in Slack every time a Vercel preview deployment finishes building, so designers, PMs, and reviewers can click straight through without digging in GitHub.
Trigger: an incoming webhook from Vercel on the deployment.succeeded event. Filter to preview deployments only and ignore production builds, failed builds, and cancelled builds.
When it fires, the agent should:
1. Call Vercel's Get Deployment with the deployment ID from the webhook payload to read the project name, branch, commit SHA, preview URL, and the deploy author.
2. Use GitHub's Search Issues and Pull Requests (or List Pull Requests filtered by head branch) to find the matching open pull request for that branch and commit SHA. If no PR is found, post a minimal heads-up with the preview URL and project/branch, and skip the summary step.
3. Call GitHub's Get a Pull Request for the matched PR to read its title, body, author, base branch, and diff statistics.
4. Draft a plain-language summary of what changed in 1 to 3 sentences. No diff syntax, no jargon, no raw file path lists. The audience is non-engineers.
5. Decide which Slack channel to post to using a configurable map from directory prefix to channel. For example, apps/design-system goes to #design-review, apps/marketing-site goes to #marketing, apps/api goes to #backend-review. If nothing matches, fall back to a default channel like #previews.
6. Use Slack's Send a Message to post one message to the chosen channel that includes the PR title and link, the author, the preview URL as a clickable link, and the plain-language summary.
Skip the post entirely if the branch is on an ignore list, if the deploy author is on an ignore list, or if the PR is a draft and draft-skipping is enabled.
I should be able to configure: the directory-to-channel routing map, the default channel, branches and authors to skip, whether draft PRs are included, and which Vercel projects this workflow watches (so one workflow can cover multiple projects).
What it does
- Watches Vercel for preview deployments that just finished building, and ignores production deploys.
- Finds the matching pull request on GitHub and reads its title, author, and what changed.
- Drafts a short plain-language summary so designers, PMs, and reviewers know what they are clicking into.
- Posts to the right Slack channel based on which part of the codebase changed, so design updates land in the design channel and marketing changes land in the marketing channel.
What you’ll need
- A Vercel account with the project you want monitored
- A GitHub login for the repository connected to that Vercel project
- A Slack workspace and the channels you want previews posted into
How to customize it
- Map your own folders to Slack channels, for example apps/design-system to #design-review and apps/marketing-site to #marketing.
- Decide what goes in the message, like PR title, author, preview link, and summary length.
- Skip specific authors, branches, or draft pull requests so noisy previews stay quiet.
- Set a default channel for changes that do not match any of your folder rules.
Use cases
- Notifications & Alerts
