Skip to main content
Webhook integrations send raw provider events into Pulse. Pulse suppresses known noise, groups related surviving events into Clusters, and classifies each Cluster into a Signal. An actionable Signal Cluster can then route into an Incident.
A webhook event does not create an Incident directly. The Pulse routing decision sits between the incoming Signal and the Incident.

​
Create a webhook signal path

Open Resolve → Integrations, select a platform, and add a webhook under its Signals section.
1

Select the platform

Choose the monitoring or alerting platform that owns the event.
2

Map the payload

Map the JSON fields for the Signal title, description, severity, service, resource, and timestamp. Add authentication and a rate limit when the sender requires them.
3

Set automatic RCA behavior

Automatic RCA is on by default for a new incident webhook, with a minimum severity of Medium. Change either value here, or turn automatic RCA off. The workspace On Duty setting must also allow automatic investigation.
4

Send a test event

Copy the generated URL and request format, send one representative event, and confirm that Pulse receives a Signal.

​
Map stable fields

Use fields that remain stable across repeated deliveries: Map the sender’s native severity values to CloudThinker’s severity levels. Test a normal event and a critical event before you activate the path.

​
Verify the complete path

A successful HTTP response proves delivery only. Verify the resulting Signal in Pulse, its Cluster membership, and whether the Cluster routes as expected. If automatic RCA is enabled, verify that an eligible Incident enters AI is handling.

Connect CloudWatch

Send CloudWatch alarm events through EventBridge.

Understand Pulse

Follow Signals through suppression, correlation, and routing.

Manage integrations

Review each platform’s connections, Signals, and outcomes.

Tune automatic RCA

Control On Duty behavior and re-investigation sensitivity.