Guide
Send Any Webhook to Slack or Discord (No Code)
Plenty of services can send a webhook but cannot post to your team chat, or post something unreadable. A small automation in between fixes that in a few minutes.
What you will build
A webhook URL that receives events from a service, keeps only the ones you care about, turns each into a readable message and posts it to a channel.
Step 1: get the channel's incoming webhook
- Slack: create an app at api.slack.com, enable Incoming Webhooks, add one to a channel and copy the URL. It starts with
https://hooks.slack.com/services/. - Discord: open the channel's settings, choose Integrations → Webhooks → New Webhook and copy the URL. It starts with
https://discord.com/api/webhooks/.
Treat these URLs as secrets. Anyone who has one can post to your channel.
Step 2: capture a sample event
Create a webhook.stream URL, register it with the sending service and trigger one event. Having a real request in the inspector lets you build the message against real field names instead of guessing from documentation.
Step 3: add the automation
Open Automations and choose Notify Slack or Notify Discord. Paste the channel's webhook URL as the destination.
Filter
Add conditions so the channel only hears what matters. For example, only failed payments above a threshold:
| Field | Operator | Value |
|---|---|---|
body.type | equals | invoice.payment_failed |
body.data.object.amount_due | is greater than | 5000 |
Format
The body is a template. Put fields from the incoming request anywhere in it with double braces. For Slack:
{
"text": ":warning: Payment failed for *{{body.data.object.customer_email}}*\nAmount: {{body.data.object.amount_due}} {{body.data.object.currency | upper}}\n<{{body.data.object.hosted_invoice_url}}|Open invoice>"
}For Discord, the field is content rather than text, and it is limited to 2,000 characters:
{
"content": "**Deploy {{body.status}}** on `{{body.repository | default: \"unknown repo\"}}`\n{{body.message | truncate: 300}}"
}The preview beside the editor shows the exact JSON that would be sent for the request you are viewing, so you can adjust until it reads well.
Step 4: test and save
Press Send test to deliver the selected request to your channel once. When the message looks right, save. From then on every matching request is delivered, and the Deliveries tab on each request shows the status and response.
Things worth knowing
- Lifetime. A free URL lives for up to 7 days. For a notification you want to keep, a Pro pass keeps the same URL alive for a month or a year.
- Failures. If the channel webhook is deleted or starts rejecting requests, the automation pauses itself after repeated failures and tells you why.
- Other destinations. The same approach works for Telegram bots, ntfy topics and any HTTPS API. See automations.