Typed, not scripted
Automations are configuration over a known set of triggers and actions. That keeps them reviewable and keeps a misconfiguration from turning into a security question.
Automations
Automate the routine, and be able to explain it afterwards.
Automations are typed trigger and action pairs defined per Brand. Every execution writes a run, and every action within it writes its result.
Recorded runs
When a customer says they were emailed twice, there is a record of what ran and when — not a guess.
Brand-scoped
An automation acts inside its own Brand. It cannot reach another Brand's records, whatever it is configured to do.
Where it helps in service work
Status-driven follow-ups, internal notifications, and recurring housekeeping around jobs and agreements.
Visual builder
In active development. Automations are defined through the API and control plane today; a self-serve visual builder is not finished.
See Field Service & CRM against your own workflow.
Tell us how your business runs today and we will walk through what is available now, what is still being built, and what would need to be connected for you.