Skip to content
PulsVaultDocs
Get started
Solo ProTeamBusinessEnterprise

Connecting Slack

Create a Slack incoming webhook and add it to PulsVault as a destination — one webhook per channel, tested before you rely on it.

Slack delivery uses an incoming webhook: a URL Slack gives you that posts into one specific channel. Creating one takes a couple of minutes and only has to be done once per channel.

In Slack#

  1. Go to api.slack.com/apps and click Create an App.
  2. Under Or start your own way, choose Blank app, then Continue.
  3. Name it — PulsVault Alerts is a good default — pick your workspace, and click Create.
  4. In the left sidebar open Features → Incoming Webhooks, and switch Activate Incoming Webhooks to On.
  5. Scroll down and click Add New Webhook.
  6. On the permission screen that appears, choose the channel under Channel for webhook and click Allow.
  7. Copy the URL from the Webhook URL column.
One webhook per channel

The webhook you just created posts to that channel and only that channel — it cannot be repointed later. To alert a second channel, repeat steps 5–7 in the same app; you do not need a second app.

In PulsVault#

  1. Open Ops → DevOps → Configure → Integrations. On the Solo Professional plan it is also under App settings → Slack & webhooks.
  2. Add a Slack integration if you do not have one yet.
  3. Add a destination: give it a name you will recognise in a dropdown (#platform-oncall) and paste the webhook URL.
  4. Click Send test and check the message arrives in Slack.

That destination is now selectable anywhere PulsVault delivers messages — starting with alert routes.

Alerting different channels per project#

Create one webhook per channel in Slack, add each as its own destination, then build an alert route per project pointing at the right one. One integration, several destinations, no duplicated setup.

If the test does not arrive#

  • Check the channel. The webhook posts where it was authorised in step 6, which is not necessarily the channel you expected.
  • Re-copy the URL. A truncated paste fails immediately; the test result will say so.
  • Check the app is still installed in the workspace. Removing the app invalidates its webhooks, and the test will report the rejection.

Rotating the URL#

The webhook URL is the credential — anyone holding it can post to that channel. PulsVault stores it encrypted and never displays it again, showing only a hint like hooks.slack.com/services/T04ABC/B05XYZ/•••.

To rotate: create a new webhook in Slack, paste it over the existing destination, Send test, then delete the old webhook in Slack. Routes pointing at the destination keep working throughout — they reference it by name, not by URL.

Was this page helpful?