Reaction
A reaction waits for an event in the system, a record being added or changed, and responds to it with a chain of actions. This is classic automation: a payment arrives and an email goes out, a client's status changes and the manager gets a task.
What you can do
- Create a reaction in the wizard
- Build a chain of actions on the canvas
- Process the companies the agent added through an Initiative
How to create a reaction
Open automation, click Add, and go through the three steps of the wizard:
- Kind: select Reaction.
- Condition: the section (clients, tasks, deals, documents, finance), the event (Add, Change, or Any), and the record's Type assigned and Status set.
- Summary: check the condition and save. The scenario is created with No action: right after adding it, choose on the canvas what exactly automation should do.
Scenario canvas
On the left of the reaction canvas is the Trigger block with the event label (for example, Any change), the section, the type, and the status. From it, the Will execute connector leads to the actions; the + button adds the next action to the chain.
Note
The trigger of a saved scenario can't be changed: the system builds all the steps of the scenario based on the section and the trigger. To run actions on a different trigger, add a new scenario.
What each action can do (email, SMS, task, deal, change of type or status) and how to choose the responsible person is covered in Setting up actions. For more about the trigger, see Triggers.
Reaction after an Initiative
A reaction also fires for records added by an AI agent through an Initiative: every company from the agent is the same Add event as manual entry. How to link them by type and status is described in How a Reaction continues the work of an Initiative.
A comparison of the two kinds is on the Automation page.