How to route Spacelift notifications between Slack and incident management tools
Last updated: September 15, 2025
Many teams want to split their Spacelift notifications between day-to-day visibility tools like Slack and critical incident management platforms like Opsgenie or PagerDuty. This approach helps maintain team awareness without overwhelming engineers with non-critical alerts.
Recommended notification routing strategy
The best practice is to:
Send routine updates, approvals, and visibility events to Slack
Route only production-impacting failures or critical internal errors to incident management tools like Opsgenie
This keeps your engineers informed through Slack without overwhelming them, while reserving incident management tools for cases that require immediate escalation.
Implementation options
Slack integration (native)
Spacelift offers a native Slack integration that allows you to:
Install the Slack app directly
Route notifications using Notification Policies
Handle approvals directly from Slack
Incident management tools (via webhooks)
While Spacelift doesn't have built-in integrations for tools like Opsgenie, you can connect them using webhooks:
Set up a lightweight forwarder (e.g., AWS Lambda, Cloud Run)
Configure the forwarder to receive Spacelift webhook payloads
Have the forwarder call the incident management tool's API (e.g., Opsgenie's Create Alert API)
Using Notification Policies for filtering
Spacelift's Notification Policies allow you to filter events and route them appropriately. You can filter by:
Stack labels
Environments
Event type
This enables you to send all Spacelift events (runs, policies, drift, errors) to the appropriate destination based on your criteria. For example, you might route all events to Slack, but only production failures to your incident management system.
This webhook + Notification Policy model is commonly used by Spacelift customers to integrate with various incident management tools while maintaining appropriate notification channels for different types of events.