Skip to main content
Pulse receives operational events through platform integrations. Configure sources from Resolve → Integrations, where each platform groups its connections, signal paths, and outcomes.

Connect a source

1

Open Resolve integrations

Go to Resolve → Integrations and select the platform that produces the operational events you need.
2

Add or select a connection

Authenticate the account or workspace that Resolve should read. The required fields depend on the platform.
3

Configure a signal path

Enable a webhook, polling, or chat path. For a webhook, map the incoming fields and severity values before you activate it.
4

Verify delivery

Send or retrieve a test event and confirm that it appears in Pulse as a Signal.
Pulse source configuration for operational events

Configure the event source, then verify one real Signal before relying on it.

Understand readiness

The Integrations page reports whether each platform is ready or still needs work. A platform can be ready, need a connection, need setup, be partially configured, have an error, need review, or remain unconfigured. At least one signal path must succeed before the platform is a working Pulse source. A valid connection alone does not prove that Resolve receives events.

Decide when RCA starts

A source sends raw events. Pulse suppresses known noise, groups related survivors into a Cluster, classifies the Cluster into a Signal, and decides whether it should create an Incident. For supported webhooks, automatic RCA is on by default with a minimum severity of Medium. The workspace-level On Duty setting (automatic investigation) still controls whether eligible Incidents start RCA automatically.

Configure webhooks

Map third-party events into Pulse Signals and test delivery.

Understand clusters

See how related events become one Signal and operational problem.

Manage integrations

Review connections, signal paths, and operational outcomes.

Tune Resolve behavior

Control automatic RCA and re-investigation sensitivity.