Skip to main content
An automation stores the event_data you would send to POST /v1/events and submits it when its trigger fires, either once to the program or individually to each matching participant. The trigger.type can be cron, one_time, or participant_state. All endpoints are under /v1/programs/{programId}/automations.

​
Endpoints

  • Create, list, get, update, and delete automations
  • Cancel a pending or in-progress automation run
  • Refresh subscriptions for a participant_state automation (re-evaluate filters)
  • List subscriptions for a participant_state automation
For usage patterns and examples, see the Automations guide.