Skip to main content
Reactions are the top-level term for Omneo’s automation system. A reaction executes pre-configured logic without manual intervention, and there are exactly two kinds, distinguished by what decides who the logic runs against.

​
The two kinds

This is the distinction to hold onto: an event already knows its subject, a query has to go and find them. A transaction.created event arrives carrying the transaction and the profile it belongs to, so a Trigger can act immediately, on that one profile. A schedule carries nothing, so an Automation cannot act until it has run a query to produce a list of subjects. That is why query is required on every Automation and why an Automation’s actions run once per result row. Calling Automations “scheduled reactions” is a half-truth worth unlearning. The schedule only decides when the query runs. The query decides what happens, and it is the part you spend your time configuring.

​
Which one do you want?

  • Something happened and you want to respond to it: Trigger.
  • You need to find people matching a condition that no single event announces (lapsed for 90 days, birthday next week, reward expiring soon): Automation.
The second case is the giveaway. There is no “customer became lapsed” event, because lapsing is the absence of activity. Only a query can find that.

​
What both share

Once a reaction knows its subject, everything downstream is identical. Both kinds run actions, an ordered chain attached to the reaction:
  • The same set of actions is available to both. Anything you can do in response to an event you can also do from a query result.
  • Actions run in sort_order sequence, and if one returns false (a filter whose condition fails, for example) the rest of the chain is skipped.
  • Each action validates its own arguments.

​
Common action types

This is the commonly used subset. The platform registers around fifty in total, including transaction, list, connection, and credit actions. For every action with its arguments, see Reaction Actions.

​
Where reactions are configured

Both kinds are configured in CX Manager under Settings > Reactions, or via the API: /api/v3/triggers for Triggers and /api/v3/automations for Automations. A reaction only runs when is_active is true.
The API uses “Trigger” and “Automation” as the two concrete object names. “Reaction” is the umbrella term for both and is not itself an API resource.