We’d like to get these alerts in our normal alerting flows via Slack and/or Pagerduty, so it’d be nice if we could get them in a notification policy or something like that.
@Evan Strat, @Zach Himsel this might actually be possible now. We’ve just launched Personal Settings → External Accounts linking, where a user can connect their external accounts (Github, Slack, soon Teams) to their Spacelift user, and now you can create notification policies that target exactly that user and they get notified in Slack etc. having the error as input. You must first set up the initial integration first, and then the users to connect their accounts. What do you think?
How does that work with regard to the “system” level notifications? i.e. the ones in https://<org>.app.spacelift.io/notifications?
AFAIK, those notifications don’t evaluate any kind of notify policy…
Amaranth Dew
•
Aug 10
My understanding was the Notification Inbox errors for system-level issues like
don’t trigger notification policies, which is kind of what I was hoping this feature request could solve. The Github/Slack integration piece here is nice but the original problem still exists for us
Ovidiu Moise
Team•
Aug 11
Gotcha. Noted, indeed this requires a separate enhancement.
Azure Chipmunk
•
Jul 31, 2025
Agreed. Since these are “system level errors”, they’re arguably important to know about. If the only way to know about them is for a root admin to happen to notice the red dot in the bottom left of their Spacelift UI window, then that’s not very reliable.
Maybe a special notification policy could be used? or just another built-in integration, like how the audit logs can be sent to something like Sumo or whatever. A single-option for either email, Slack, whatever. Could be a webhook target, whatever.
Log in to comment and vote
Comments7
Ovidiu Moise
Aug 7
@Evan Strat, @Zach Himsel this might actually be possible now. We’ve just launched Personal Settings → External Accounts linking, where a user can connect their external accounts (Github, Slack, soon Teams) to their Spacelift user, and now you can create notification policies that target exactly that user and they get notified in Slack etc. having the error as input. You must first set up the initial integration first, and then the users to connect their accounts. What do you think?
Azure Chipmunk
Aug 7
I’d be cool with that.
Ovidiu Moise
Aug 10
Awesome. Feel free to try it, and let me know if you have any issues. Docs: https://docs.spacelift.io/concepts/identity-access-management/external-accounts.html
Azure Chipmunk
Aug 10
How does that work with regard to the “system” level notifications? i.e. the ones in
https://<org>.app.spacelift.io/notifications?AFAIK, those notifications don’t evaluate any kind of notify policy…
Amaranth Dew
Aug 10
My understanding was the Notification Inbox errors for system-level issues like
don’t trigger notification policies, which is kind of what I was hoping this feature request could solve. The Github/Slack integration piece here is nice but the original problem still exists for us
Ovidiu Moise
Aug 11
Gotcha. Noted, indeed this requires a separate enhancement.
Azure Chipmunk
Jul 31, 2025
Agreed. Since these are “system level errors”, they’re arguably important to know about. If the only way to know about them is for a root admin to happen to notice the red dot in the bottom left of their Spacelift UI window, then that’s not very reliable.
Maybe a special notification policy could be used? or just another built-in integration, like how the audit logs can be sent to something like Sumo or whatever. A single-option for either email, Slack, whatever. Could be a webhook target, whatever.