Skip to main content
Six events, covering signals, runs, pipeline moves and content. Each example below is the same example Openpulse serves in its OpenAPI document, so a payload shown here is exactly what a POST to your endpoint contains — never a paraphrase of it.

signal.created

A new signal was kept. One delivery per signal, the first time it is seen.

signal.urgent

A signal cleared your urgency bar. These also fire signal.created — subscribe to this one alone if you only want the interruptions. Carries the whole signal body plus the urgency block: the threshold that was crossed, the level, and the score that crossed it.

run.completed

A listener finished a pass, with what it searched and kept.

run.failed

A listener run could not finish. The one worth alerting on.

pipeline.stage_changed

Somebody moved a deal to another stage. The event a CRM wants — carries where it moved from, where it moved to, and who moved it.

content.piece.ready

A generated content draft finished. One delivery per piece, so four channels on the same idea arrive as four events.

Every event’s response contract

Any 2XX response marks the delivery accepted. Anything else — including a timeout — is retried with backoff. See Webhooks for signing, verification and delivery history.