Skip to main content

An event tracks what happened with a lead at a particular step in a flow. An event is a self-contained snapshot of the state of the lead at the time the lead visited the step. It contains a full copy of all lead data, along with all data that was appended before that step. Every event contains the below properties.

outcome
enum<string>
required

The outcome of the event

Available options:
success,
failure,
error
reason
string
required

The reason for a failure or error outcome

type
enum<string>
required

Recorded after a source submits a lead to a flow

Available options:
source
vars
Source Variables · object

All data available at the time LeadConduit started processing this event

host
string
start_timestamp
integer

The number of milliseconds elapsed since epoch at the start of the step processing

end_timestamp
integer

The number of milliseconds elapsed since epoch at the end of the step processing

firehose
object
ms
integer

The number of milliseconds that elapsed while processing the lead

wait_ms
integer

The number of milliseconds that LeadConduit spent waiting for all recipients to respond

overhead_ms
integer

The number of milliseconds of overhead that LeadConduit added while processing the step

lag_ms
integer
total_ms
integer

The number of milliseconds that elapsed since the lead was submitted

handler_version
string

The version of the lead handler

version
string

The schema version of the event

cap_reached
boolean
flow_ping_limits
Ping Limit · object

The ping limit configuration is defined in a flow on a source, or directly on the flow itself. The configuration controls the behavior of the ping limit by setting the maximum and the duration. The counter for a ping limit is kept as a standalone record which shares ping limit's ID.

source_ping_limits
Ping Limit · object

The ping limit configuration is defined in a flow on a source, or directly on the flow itself. The configuration controls the behavior of the ping limit by setting the maximum and the duration. The counter for a ping limit is kept as a standalone record which shares ping limit's ID.

ping_limit_reached
boolean
expires_at
string<date-time>

The time this event will be automatically deleted from LeadConduit (events are retained for 90 days)

module_id
string

The integration module ID configured for the source

package_version
string

The semantic version of the integration package

acceptance_criteria
Acceptance Criteria · object

The acceptance criteria configured on the source when the lead was processed

step_count
integer

The number of steps processed for this lead (>= 0 and <= total number of steps)

Example:

4

appended
object

All data appended while handing the lead

request
object

The inbound HTTP request

response
object

The inbound HTTP response