The Automation hub
An automation scenario always consists of two elements: a trigger — the event that starts the scenario — and a chain of actions that then run, optionally separated by delays.
Triggers from across the suite
Because all the hubs live in the same suite, a scenario can be triggered from any one of them:
- a form submission (see Web forms),
- an appointment booking (Meetings hub),
- a CRM event — for example a deal moving to a different stage,
- the creation or modification of a custom object (see Custom objects).
Actions that act, not decorate
Once triggered, a scenario can chain several actions together:
- send an email or an SMS,
- create a task for a member of your team,
- update a CRM record (for example add the contact to a segment or change a property).
Scheduled delays
Between two actions, you can insert a scheduled delay — for example waiting two days before sending a follow-up SMS. The scenario resumes automatically once the delay has elapsed.
tip
The variables available in your campaigns (contact, company, custom objects) are also available in the actions of a scenario.