Skip to main content
Every event arrives in the same envelope: only data changes. The examples are fictional, and indented here for reading; the request body is compact JSON.

lead.created

A person who reacted to or commented on a post of a profile you track becomes a lead: it is sent when the lead gets its first score. Data: lead (lead) and signal (signal): the person’s first engagement in your workspace, with its post and its tracked profile.
A lead whose scoring failed is sent at its first score, usually at the next cycle.

lead.rescored

A lead is scored again and its score or fit band changes. A rescoring with the same result is not sent. Data: lead (lead), previous and current: each {score, fit_band, scored_at, icp_version_id}.

lead.engaged_again

A lead who already has a score reacts to or comments on another post of a profile you track. Data: lead (lead) and signal (signal): this new engagement, already counted in lead.engagement_count.
Not sent when the person comments on their own post, nor for a lead you discarded.
lead.engagement_count is counted when the event is sent: use it to write “you engaged N times”.

lead.status_changed

A lead’s status changes, for example when someone discards it in the console. Data: lead (lead), previous_status, status, changed_at and changed_by: console when someone signed in made the change, otherwise tikt.

lead.matched

A lead matches a workflow’s filters for the first time. Sent once per lead and per workflow, for the workflow’s whole life. Data: workflow (workflow): its id, its name and the reason (new, came_back, rescored or past); and lead (lead).
Sent only to the connection chosen in the workflow’s Send webhook action, in its format. You can’t subscribe to it, and All events doesn’t include it. See Workflows.
past: a lead from the last 30 days that already matched when the workflow was first turned on.