LOW / CODEBlueprints
engineering

Deployment Notification Pipeline

Notify your team on Slack whenever a GitHub deployment succeeds or fails. Posts deployment status, commit info, and environment details to a dedicated channel.

Beginner~10 minn8nMake.com 684 downloads 2571 views

Setup Instructions

1. In your GitHub repository, go to Settings > Webhooks and create a webhook pointing to your automation platform's webhook URL. 2. Select the "Deployment status" event (or use the GitHub trigger node which handles this automatically). 3. In your automation platform, add a GitHub trigger node configured for deployment_status events. 4. Add a Set/Function node to extract: repository name, environment (production/staging), status (success/failure/error), commit SHA, commit message, and deployer username. 5. Add an IF node that branches on the deployment status — "success" vs everything else. 6. For success, add a Slack node that posts a green checkmark message to #deployments with the commit details. 7. For failure, add a Slack node that posts a red alert to #deployments and optionally tags the deployer with their Slack user ID.
Troubleshooting
**Webhook events not received:** Verify the webhook URL is correct and the secret matches. Check GitHub's webhook delivery log under Settings > Webhooks > Recent Deliveries for HTTP response codes. **Deployment status events not firing:** GitHub deployment status events require that deployments are created via the GitHub Deployments API (or tools like GitHub Actions, Vercel, Heroku). Manual git pushes do not create deployment events — you may need workflow_run events instead. **Slack message not showing commit info:** The deployment_status payload includes a nested deployment object. Access the commit SHA via data.deployment.sha and the ref via data.deployment.ref.

Need a custom version?

We can build a tailored automation workflow for your specific needs.

New blueprints weekly

Get notified when we publish new automation workflows.