Workflow automations run on their own triggers inside HeyX. The public API
offers read-only discovery — list and get — and does not launch or edit
automations. To drive an event-triggered automation from an integration,
publish a customer event with
CreateCustomerEvent; the matching automation reacts on its own schedule.
Only published, non-archived automations appear here. definitionType filters
by trigger style: triggered reacts to events, polling runs on a schedule.
subjectType filters by the record an automation acts on, such as customer,
appointment, work_order, problem, advanced_task, order, or
correspondence.
Results use stable newest-first cursor pagination. Pass nextCursor from one
response as cursor on the next request. A page may hold fewer than pageSize
entries after unpublished and filtered-out automations are dropped, so continue
until nextCursor is absent or empty rather than stopping on a short page.