Skip to main content

Event format

Events follow an object.action naming convention. Every event is delivered with the same envelope. The data field contains a summary of the resource at the time of the event.
Fields that have no value yet are delivered as empty strings. For example, a task run that is not part of a workflow has "workflow_id": "".

Agent events

Source events

Credential events

Session events

Task events

Also fired when a task graduates to a new status after successful runs, for example learning to test.

Task run events

Task run payloads share the same fields. result is empty until the run reaches a final result, then becomes success or failure. runtime_ms appears once the run has finished. workflow_id is empty for runs that are not part of a workflow.
Includes an interaction object describing the input to collect. See Handling interactions for the full interaction object reference.

Storage events

Event destination events