Integrations

Slack notifications

Post your app's events to the channels your team already watches: orders, signups, support requests.

The Slack connector turns your app's events into messages where your team already looks. New order, new signup, new support request: post it to a channel as it happens. This guide covers connecting Slack and the patterns that work.

Connect it

  1. Approve in Slack

    Open Vault → Connectors and pick Slack. Slack's own authorization window opens; sign in to the workspace you want and approve. No keys to copy.

  2. Ask for the notifications

    Say what should trigger a message, where it goes, and what it should say:

    When a new order is placed, post to #orders: the customer name, the total, and a link to the order in my admin page.

  3. Test it in the preview

    Trigger the event in your preview and watch the channel. Connected services are live in the preview, so the message really posts; aim the first tests at a quiet channel.

What your app can do with it

Post messages to channels, list the channels available, and read a channel's recent history (useful for showing a feed inside your app). Workspace administration is not on the menu; the endpoint policy keeps a published app to messaging.

Whose Slack is it?

Notifications to your own team are the common case, and that is an owner-shared connection: your app posts to your workspace no matter who triggered the event.

The other shape is per-user: a feature like "let each user post to their own Slack" asks each user of your app to approve Slack access themselves, and posts on their behalf to their workspace. Say which one you mean when you ask for the feature; "Connector limits and scope" explains the difference in depth.

Frequently asked

Messages are not arriving in a private channel

Slack only lets the connection post where it has been added. Invite the connected app to the private channel in Slack, then try again. Public channels work without this step.

Can messages use rich formatting, buttons, or threads?

Formatted text and structured layouts, yes; ask for what you want the message to look like. Interactive elements that call back into your app when clicked are more involved; describe the goal and the agent will tell you what is feasible.

Every test posts to the real channel. Can I separate test from live?

Ask for it: "post to #test-orders from the preview and #orders when published" is a normal request, and the agent wires the environment split.

Was this page helpful?