Webhook to Slack Integration

Send Webhook alerts to Slack with on-call and escalation.

Alert ⚠️

Communicate

Alert ⚠️

Communicate

The webhook to Slack integration sends alerts from any tool that can make an HTTP request to Slack through All Quiet. Your tool sends a request to an All Quiet webhook URL. All Quiet creates an incident, notifies the on-call engineer and posts the incident to the Slack channels you chose. You don't create a Slack incoming webhook: All Quiet posts through its Slack app.

Start free trial

How the Webhook Slack integration works

1

In All Quiet, open Inbound Integrations, click + Create, choose Webhook as the type, select a team and copy the webhook URL.
2

Optionally turn on Enable additional Authentication & Security to allow only certain IP addresses or require a Bearer token.
3

Send a test request from your tool, or with the cURL command below.
4

Open the integration's details page, select the request and map its fields to incident fields on the Payload tab.
5

Open Outbound Integrations, click + Create, choose Slack, click Add to Slack and approve access in Slack.
6

Invite the app with /invite @All Quiet (or @All Quiet EU on allquiet.eu) and select the channels that receive incidents, for all severities or only the ones you choose.

Full guides: Webhook setup guide Slack setup guide

What you get

Any tool that can send a Webhook can open an incident
Incident messages in the Slack channels you choose
Escalation to the next person if nobody responds
Incident status and updates in one place

curl -X POST 'https://allquiet.app/api/webhook/YOUR-WEBHOOK' \
  -H 'Content-Type: application/json' \
  -d '{"alertName": "Demo Alert", "alertStatus": "firing", "description": "This is a Demo Alert"}'

A test alert sent to an All Quiet inbound webhook. It becomes an incident and is posted to Slack.

Use cases

Tools without a native integration.

Anything that can send an HTTP request, from a backup job to an on-premise appliance, can open an incident. All Quiet accepts JSON, form data, plain text and XML, so the tool doesn't need to change its format.

Internal scripts and CI jobs.

A failed deploy, a nightly job that didn't finish or a script that detects bad data can call the webhook. The incident reaches the engineer on call and the team's Slack channel at the same time.

Custom monitoring with on-call behind it.

In-house health checks often post straight to Slack, where alerts get lost. Sending them to All Quiet adds escalation, so an unanswered alert reaches the next person instead of scrolling away.

FAQ

How do I connect Webhook to Slack?

Create an inbound integration for Webhook in All Quiet and add its webhook URL in Webhook. Then create an outbound integration for Slack. The Webhook setup guide and the Slack setup guide on docs.allquiet.app walk through each step.

What does All Quiet add between Webhook and Slack?

All Quiet turns each Webhook alert into an incident, notifies the engineer on call, escalates if nobody responds and keeps a record of the incident. Slack receives the incident with that context.

Can I try the Webhook Slack integration for free?

Yes. Start a free trial of All Quiet and connect Webhook and Slack during the trial.

Where is my data hosted?

All Quiet is a European incident management platform: built in Berlin, with selectable EU data residency in Frankfurt, GDPR compliance, and ISO 27001 certification. Alert data for EU customers is stored and processed in Frankfurt. That matters for on-call specifically because alert and escalation data routinely contains production system details.

Do I need to create a Slack incoming webhook?

No. A Slack incoming webhook URL posts messages into a single channel. With All Quiet you install the All Quiet app in Slack once, invite it to the channels you want and All Quiet posts incidents there. Your tool only needs the All Quiet webhook URL.

What payload format does the All Quiet webhook accept?

JSON, form data, plain text and XML, detected from the Content-Type header, sent with any HTTP method. Each request appears on the integration's details page, where you map its fields to incident fields on the Payload tab. You can require a Bearer token or limit requests to certain IP addresses.