Deployment Notifications
Automate deployment notifications with Nebula. Post summaries to Slack whenever your team ships — version numbers, changes, and who deployed.
What you'll build
Whenever your team deploys to production, Nebula automatically posts a formatted summary to Slack with the version number, what changed, and who deployed it — so your whole team stays in the loop without anyone having to write an update manually.
What to say
When a new deployment goes out to production, post a summary to #engineering in Slack with the version number, what changed, and who deployed it.
Checking latest deployment event... Found: v2.4.1 deployed to production by @maria at 3:42 PM.
Parsing deployment payload: version v2.4.1, 3 commits, 2 contributors...
Posted deployment summary to #engineering.
Done! Posted to #engineering:
Production Deploy — v2.4.1 Deployed by: Maria Lopez Time: 3:42 PM UTC
Changes:
- Fix payment webhook retry logic (#482) — @maria
- Add rate limiting to /api/search (#479) — @james
- Update dependencies and patch CVE-2026-1234 (#481) — @maria
3 commits from 2 contributors.
Customize the Slack channel and what details to include. You can add release notes, link to the diff, or tag specific people.
What happens
A deployment event is received
When your CI/CD pipeline completes a production deployment, it fires a webhook event. Nebula's GitHub Agent picks up the deployment status event and passes the payload to Nebula for processing.
Nebula parses the deployment details
Nebula extracts the key information from the event: version number, who triggered the deploy, timestamp, and the list of commits included. It cross-references with GitHub to get commit messages, PR titles, and author info.
A formatted summary is composed
Nebula puts together a clean, scannable message with the version, deployer, timestamp, and a list of changes. Each change includes the PR title, number, and author so your team can quickly see what shipped.
The summary is posted to Slack
Your Slack Agent posts the deployment summary to the channel you specified. The entire flow — from deploy event to Slack message — happens automatically with no manual steps.
Make it automatic
Set this up as an event trigger — notify #engineering whenever a production deployment completes.
Creating event trigger: on deployment_status event (environment: production, state: success). Task: parse deployment payload via GitHub Agent, format summary with version, changes, and deployer, post to #engineering via Slack Agent.
Registered webhook for deployment_status events on production environment.
Your event trigger is live. Whenever a production deployment completes, I'll post a summary to #engineering with the version, changes, and who deployed. You can pause or edit this from the Triggers page.
Nebula creates an event trigger that fires on every successful production deployment. You can view, pause, or delete it from the Triggers page in the sidebar.
Connect your integrations
This recipe uses the GitHub Agent for deployment events and the Slack Agent for posting notifications. Connect both from the Integrations page — make sure the Slack bot has been invited to your target channel.
Related recipes
GitHub Issue Triage
Label, prioritize, and assign new issues automatically based on content.
Code Review Digest
Get a daily summary of open pull requests that need your team's attention.
Webhook Triggers
Give your agent a webhook URL so external services like Stripe and GitHub can trigger it automatically.
GitHub Issue Triage
Automate GitHub issue triage with Nebula — label, prioritize, and assign new issues based on content to keep your backlog organized hands-free.
Code Review Digest
Generate an AI code review digest with Nebula. Summarize open pull requests daily — changes, authors, wait times — and post the digest to Slack.