Connecting Slack

On the Connections screen, connect Slack so billing events can post to a channel. You can connect in one of two ways. Either way, notifications go to a single channel, and your credentials are encrypted at rest and never shown again after you connect.

Add to Slack (OAuth) vs an Incoming Webhook #

• Add to Slack (OAuth) — click Add to Slack and authorize through Slack. The app is unlisted (installed directly into your workspace, not from the public directory). During the flow you pick the single channel that notifications post to.
• Incoming Webhook URL — if you’d rather not run the OAuth flow, create an Incoming Webhook in Slack and paste its URL. The webhook is already bound to one channel, so that’s the channel notifications go to.

Whichever method you choose, notifications post to one channel. To change the channel, reconnect (OAuth) or paste a new webhook URL.

Verifying the connection #

Slack has no separate access probe — it’s verified by actually posting. Once connected, click Send test message on the Slack card to post a sample notification to the channel. If it arrives, the connection works.

Testing and disconnecting #

• Send test message re-posts a sample notification to confirm the channel is still reachable. (This replaces the generic Test action used by other connectors — Slack is verified by posting.)
• Disconnect removes the connection and its stored credentials.

GET    /v1/connections
GET    /v1/connections/slack
GET    /v1/connections/slack/oauth-url
POST   /v1/connections/slack/key
POST   /v1/connections/slack/test-message
DELETE /v1/connections/slack

The OAuth flow returns to /api/connections/slack/callback.

Where to next #

• Slack notifications — choose which events post and customize each message body.