Automation events and runs

Emit an event

curl "$ALL2CF_SEND_URL/v1/workflows/events" \
  -H "Authorization: Bearer $ALL2CF_SEND_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event":"user.created","eventKey":"user_42_created","payload":{"user":{"email":"alex@example.com","activated":false}}}'

event is required and limited to 160 characters. eventKey is required and limited to 256 characters. The serialized payload must be at most 64 KiB. The 202 response reports matched active workflows and accepted new runs.

Idempotency

The event key is the Idempotency boundary for each matching workflow. Repeating it does not insert a second run. Use a stable source event ID, not a timestamp regenerated on retry.

Run states

• queued: ready for the next scheduled workflow pass.
• waiting: a Delay recorded a future nextRunAt.
• completed: all steps finished.
• failed: Send or Webhook returned an error or execution failed.

Recent runs show workflow version, event key, current step, next run time and error. The Runtime processes up to 50 due runs per pass and leases a claim for five minutes to prevent concurrent execution. The lease is not a deliberate five-minute customer delay; an interrupted claim becomes eligible again after it expires.

Recovery

Correct the missing template/topic, address, DNS/provider issue or webhook endpoint. Failed runs do not automatically repeat a side effect; emit a new eventKey after confirming it is safe. Pause the workflow to stop new events while investigating. Existing runs remain pinned to their accepted version.