Understand the three parts
One platform does not need to support every part. The integration page shows what the selected platform can do and what remains unconfigured.
Configure the capability you need
Select a platform, then configure only the sections it supports and your incident process needs.Connections
Add the account, workspace, or project instances that DRE should read. Some platforms support several connection instances. Some webhook or outcome capabilities do not require a connection.Signals
When the platform is an event source, configure a webhook, polling, or chat path. Send or retrieve one representative event and confirm that Pulse produces the expected Signal.Outcomes
When the platform is a response destination, enable the supported Incident update, war room, follow-up ticket, draft fix, postmortem, or provider synchronization action. An outcome-only platform does not need a Signal path. A war room has its own minimum severity: Critical, High, or All. Set it so routine incidents do not open a channel. A postmortem is written on request and costs a model call. It is an outcome, not a lifecycle state, so requesting one does not change the Incident’s status.Read integration readiness
A platform can appear as ready, needing a connection, needing setup, partially configured, in error, needing review, or not configured. Readiness describes the complete platform setup, not authentication alone. For a Signal capability, use source-first verification: a webhook must deliver a Signal, polling must retrieve an event, or chat must produce the expected event. Only then treat that signal path as active.Related
Connect Pulse sources
Verify a webhook, polling, or chat event in Pulse.
Configure webhooks
Map third-party payloads into stable operational Signals.
Understand DRE
Follow the Detect, Analyze, Resolve, and Validate stages.
Tune DRE behavior
Control automatic RCA and re-investigation sensitivity.