Record the start of a workflow node execution
Creates a workflow_run_steps row when the data platform starts executing a node. Idempotent via the composite key (workflow_run_id, node_id): retries upsert the existing row. Requires Bearer token authentication.
Authorizations
Static internal-ops token used by the data platform and internal cron jobs (e.g. zombie-run sweep). Validated via requireBearerToken inside the handler against a service-specific environment variable.
Path Parameters
Unique identifier of the workflow run
1Body
Unique node identifier from the workflow flow definition
1Node type: TRIGGER (entry point) or ACTION (executable step)
TRIGGER, ACTION Organization UUID for tenant isolation
1Action type for ACTION nodes; null or omitted for TRIGGER nodes
CREATE_OR_GET_PLAN, ADD_ITEMS_TO_PLAN, CALL_WEBHOOK, SEND_EMAIL Resolved input parameters passed to the node after variable substitution
Timestamp when this node started executing; defaults to server time
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$Initial status; defaults to RUNNING
PENDING, RUNNING, SUCCEEDED, FAILED, SKIPPED, CANCELLED 
