Agents & Automations

Let the system act when something happens — from fixed steps to an AI agent that reasons over your records.

• GuideAgents and automations from first principlesAn automation watches for a trigger — a record changing, a scheduled time, an incoming message — and runs steps in response: a saved "when this, do that" the system carries out for you. When a response needs judgment rather than a fixed rule, a step hands off to an AI agent that reads the record and decides what to change — which is where a fixed workflow becomes agentic.
• ArticleCreate and activate an automationBuild an automation by choosing its trigger, adding the steps it should run, then testing it before it goes live. A new automation starts inactive on purpose — validate the trigger, do a dry run that changes nothing, and only then activate it.
• ArticleAutomation triggersTriggers come in four families: something happens to a record, a person or system starts it, time arrives, or a message comes in. The setting people miss most is which origins a record trigger listens to — by default it watches changes coming from your website, so edits made by hand in the CRM will not fire it until you say they should.