Slack
Route Produl alert notifications into a Slack channel using a Slack Incoming Webhook.
What it does
The Slack integration delivers Produl alerts into a Slack channel using an Incoming Webhook. When an alert fires — whether it's a threshold breach, an anomaly detection, or a custom event alert — Produl POSTs a Block Kit-formatted message to the webhook URL you provided.
Slack is a notification channel only. Produl does not read messages from Slack and does not pull any data from your workspace. Each Produl account stores one Slack webhook, which binds to a single channel.
Setup
- 1
Create a Slack app
Go to api.slack.com/apps and click Create New App → From scratch. Give it a name (e.g. "Produl Alerts") and pick the workspace where you want alerts delivered. - 2
Enable Incoming Webhooks
In the app's sidebar, open Incoming Webhooks and toggle Activate Incoming Webhooks to On. - 3
Add a webhook to a channel
Scroll down and click Add New Webhook to Workspace. Choose the channel that should receive alerts (e.g.#alerts) and click Allow. Slack will generate a webhook URL that looks likehttps://hooks.slack.com/services/T.../B.../.... - 4
Paste the URL into Produl
Copy the webhook URL, open Integrations in the Produl dashboard, and paste it into the Slack card. Click Save Webhook. Produl will post a confirmation message to the channel to verify the connection.
One channel per Produl account
Alternative: the Incoming Webhooks app
What is sent
Each time an alert fires, Produl POSTs a Slack Block Kit message to your webhook. Messages include:
- Alert name and a bell indicator
- The metric and current value that triggered the alert
- The configured threshold (when applicable)
- The site name and a "View Dashboard" button linking back to Produl
- The timestamp of when the condition was detected
Produl does not send weekly digests or periodic summaries via Slack — only alert-triggered notifications.
Troubleshooting
"That doesn't look like a Slack Incoming Webhook URL"
The URL you pasted must start with https://hooks.slack.com/services/followed by three path segments (team, bot, and secret). If you're seeing a different format, you likely copied the wrong URL from Slack — return to Your Apps → Incoming Webhooks and copy the URL listed under Webhook URLs for Your Workspace.
"Slack rejected the webhook"
This usually means the webhook was revoked in Slack, or the channel it was bound to was archived or deleted. Generate a new webhook from your Slack app's settings and paste the new URL.
No confirmation message appeared
Check the channel the webhook was bound to when it was created — not every channel in the workspace. If the channel still doesn't show the confirmation, the webhook may have been deleted. Regenerate it and try again.
Testing an alert delivery
To test the end-to-end pipeline, create a threshold alert with a condition that will immediately trigger (e.g. pageviews > 0 over the last hour) and add Slack as a destination. Delete or update the test alert afterward.