- Product
- Automation
No-code automation built into the data graph.
Triggers from Sales, Finance, Support, Projects, Docs, Drive, Mail and more, conditions on the triggering record, and actions that create tasks, route work, send email and convert documents. Automation runs your rules; Ask Cyril plans and acts when you ask.
What Automation does for you
A no-code engine that connects modules: an event in one app can create work in another. It is separate from Ask Cyril — automation runs your rules every time; Ask Cyril plans and acts when you ask.
- Triggers across Cyril
- Sales stage changes, deals won, invoices and payments, ticket events, project and task changes, Docs, Drive and Mail events, and dates on a record.
- Conditions on the record
- Filters on the triggering record’s fields, with actions that can loop over its related invoices, deals or tasks.
- Actions that do the work
- Send email, create tasks, assign and route, change status, convert an estimate to an invoice, run dunning steps, call webhooks and wait for an approval.
- Auditable, testable
- Every run is logged step by step, with what each action did. Test mode replays a trigger without taking action.
Rules for what should happen every time.
Automation and Ask Cyril are separate on purpose. Ask Cyril handles one-off requests, with your approval each time; automation runs the rules your operator builds in the no-code builder, the same way every time. Every run is logged step by step.
- Rules run every time; Ask Cyril handles the one-offs
- Test mode replays a real trigger without producing side effects
- Export any automation as JSON and import it to restore a copy
Test mode replays a real trigger without taking the action.
An automation that spans modules can do real damage, so a rule can be replayed against a real event with the actions withheld — you see what it would have done before it does it. Every run that does execute is logged step by step, which is what makes an automated write reviewable rather than merely fast.
- Replay a trigger with actions withheld, then arm it
- Every run logged step by step
- Ask Cyril runs are recorded too, with who approved each one
Common Automation questions
Do I need automation if I have the AI layer?
They do different jobs. Automation runs the rules you define, every time, without anyone asking. Ask Cyril plans and acts when you ask, and waits for your approval first. Rules are for what should happen every time; Ask Cyril is for what needs judgement.
What stops a rule from looping?
Runs are logged and testable before arming, which is the practical control. If you are designing something that writes to the records that trigger it, replay it in test mode first — that is precisely the case the mode exists for.
Can automations reach outside Cyril?
The engine is built to join modules at the graph level rather than to be a general-purpose iPaaS. If your requirement is orchestrating several external SaaS products, a dedicated automation product is still the better tool — the value here is that the internal joins need no connector at all.
Be one of the first to use Cyril.
Join the waitlist for early access. We’ll only email you when there’s something real to share.
One email when your place opens. Nothing else.
