Skip to main content

User level Slack Integration

Feature RequestsPolicies

If it was possible to connect your slack account to you Spacelift account, then in a notification policy, you could potentially use that Slack user information for something like notifications to users directly on Slack when a stack requires approval.

Workaround
Problem
Status: ✅ Completed6 comments

Log in to comment and vote

Comments6

  • Ovidiu Moise changed status to ✅ Completed
    Team•

    Aug 7

    Pinned

    Thank you dear Upvoters for your input. This feature is now live, you can find it in Personal Settings → External accounts, where a user can link their Github/Slack/(soon Teams) account to their Spacelift account. From that moment, you can use notification policies to send notifications to them.

  • Tomato Melon

    •

    Jun 8

    I’d like to see similar functionality in the Slack message notifications created by Spacelift. Currently, they just mention the GitHub username of the committer. Swapping this with the appropriate Slack handle would create immensely more effective notifications.

    Our current approach is team based Slack Spacelift channels w/ alerts on all new messages, which get VERY noisy.

    • Ovidiu Moise

      Team•

      Aug 7

      @Adam Neumann your request is slightly different, and we can definitely build it based on what we just launched. Do you mind creating a separate FB request specifically for it?

  • Purple Mustard

    •

    Apr 3

    We’ve got a similar issue. We want to notify users via Slack when a stack failed that they made a change on (either a proposed run on a branch, or a tracked run on the main branch). We’ve got a few hundred engineers so it would be nice to not have to maintain a mapping of Spacelift login → Slack user id in order to accomplish this. I know for some Slack integrations I’ve worked with the user’s email is enough information to go off of to be able to DM them. That in my opinion would be the ideal situation here (where I can take the email of the person who committed the change and then pass it to the Slack integration and it would take care of the DM from there)

  • Fuchsia Skywalker

    •

    Jul 10, 2025

    Hi Natalia,

    Sure thing. Happy to give some more information :)

    • Right now we are only into approvals, so notifying the committer of the merge request about an approval waiting in Spacelift, e.g. when you need to promote the plan to production. When you have these approval gates in place, when you don’t trust the changes to be automatically applied, then depending on how long the pipelines takes, then you might forget about it.

      • It could also be for run failures, that’s a very good point actually. We don’t ue drift detection, as we are not on the appropriate plan.

    • Maintaining lists manually is not great when in an environment with a large amount of replacements, so if an employee at our organization is leaving, and we have to on/off-board him, then we have to remember to do it manually in the Rego list. We would like to avoid that. Hence this idea :)

    • The idea is to actually notify the commit author, so if the commit author username could be tied to an user in Spacelift, which should be possible since we are using Git SSO for login, then if user had a slack user connected to the Spacelift user, then it would be possible to do this mapping automatically when sending notifications.

  • Natalia Gazda

    Team•

    Jul 10, 2025

    Hi @Jens Rotne ! Thanks for raising the idea. A few questions to help us understand the real job here:

    • How often do you find yourself wanting to notify specific users via Slack? Is this mostly about approvals, or also run failures, drift, etc.?

    • What’s painful about the current approach using Rego lists—maintaining them, keeping them in sync, knowing who’s who?

    • Would the goal be to notify individual stack owners, or more like dynamically routing to whoever touched the code / triggered the run?

    A quick workaround that came to my mind was to have users have their individual slack channel on which they get notified, but I understand how that might not be ideal.