Test run without sending
Play any rule through against a sample record before it goes live. Nothing is sent and nothing is written.
Workflow
Your sales works too,
Your sales works too,
when you don't.
A rule has three parts: a trigger, a condition and an action. Put one together here — these are exactly the building blocks in the editor, in exactly this order.
Recipes:
When a lead is created and the source is “trade fair / event”, then send an email to the lead.
Passes through the consent gate: anyone who has objected is skipped — automatically, without anyone having to remember.
The editor
Readable from top to bottom.
No tangle of nodes, no formula language. A flow that someone who did not build it still understands — six months later.
Building blocks
What a rule can be made of.
| Kind | What is available |
|---|---|
| Triggers | Stage reached · opportunity created, won or lost · lead created or converted · activity logged · field changed (on opportunity, lead, contact and account, custom fields included) · date reached (yearly or once, optionally with lead time) · daily schedule · days since stage change |
| Conditions | Field, operator, value — combined with AND and OR. Plus history conditions: days since the last activity, number of activities by type and outcome, “there has already been a demo”. Your own fields are available with the operators that suit their type. |
| Branching | “If / then” splits the flow into two labelled lanes — met and not met. Each lane continues as its own sub-flow. |
| Waiting | From one hour to 90 days. Conditions after the pause always check the current state — “quote sent, wait three days, only follow up if nothing has happened”. |
| Actions | Email to contact, lead or primary contact · notify the owner · create a task or activity · set a field · change stage · assign a lead · create a contract from a template · send a signed webhook |
Control
Automation you can check.
A rule that quietly sends emails to your customers has to be verifiable. Otherwise it is a risk, not relief.
“Why didn't it fire?”
Pick a real record and read the step-by-step checklist: which condition failed against which actual value, marked at the first point that did not pass. No guesswork.
Impact in numbers
The last 90 days per rule: runs, emails sent, tasks created, contracts produced, webhooks dispatched — with a mini history. So you can see which rule actually moves something and which merely runs.
One-off run for the backlog
A new rule only applies to future events. The one-off run catches up on what already exists — with a preview, a confirmation and safe repetition if something goes wrong.
What would you automate first?
Usually it is whatever someone is doing by hand right now and regularly forgets.