Skip to main content
Every automation has exactly one triggerType. When a matching event occurs (or a schedule fires, or the API runs the workflow), the engine starts an execution with event.data populated from that source.
Source of truth: trigger types are stored in the API (VALID_TRIGGER_TYPES in the automations schema). The UI lists the same values with labels and filters in the Workflow Builder.

​
Trigger Catalog

​
Who Emits Which Trigger?

  • Reactive events (alert, investigation, entity, transaction, KYC): the corresponding services emit the event to the automation engine (processEvent).
  • rule_triggered: synthetic event when a rule action runs the automation.
  • manual_execution: only when you call run with an automation whose trigger is manual.
  • scheduled: the automations scheduler process.
  • create_entity_flow: entity creation / onboarding path calling runAutomationById with the right workflow id.

​
Condition Contexts per Trigger

The product only shows condition fields that make sense for the trigger you picked. The UI maps each trigger to allowed contexts (transaction, investigation, alert, entity, KYC, rule): See also Context and standby for how event.data is shaped.

​
Notes

  • Disabled or archived automations do not run.
  • KYC: kyc_approved / kyc_rejected / kyc_validation_finished may overlap in policy; design automations so you do not double-run the same business logic unless intended.
Maintenance: When the product adds a trigger, update this page and the synergy tables in Synergy.