Automations · the rules engine

When something happens,
do something.

One rules engine over your whole book. A lead lands, a deal closes won, a prospect asks a question in a zone, a record goes quiet for two weeks — and youdou runs the play you wrote: enroll, task, enrich, notify, or wait for your say-so.

Trigger
Deal closed wonDetected however it happened, including imports and sync
→
Conditions
Amount ≥ 10k · company-owned domainThe same filters your saved views use
→
Actions
Task for onboarding · enroll in welcome sequenceQueued for your approval, then run
In plain terms

youdou’s automations are one rules engine over your whole book of business: sixteen triggers (a new lead, a deal closed won or lost, a zone viewed or a question asked, an email opened, clicked, replied or bounced, a sequence finishing with no reply, an event attended or no-showed, no touch in N days, an overdue task) and eighteen actions (set a field, add a note, enroll in a sequence, send a template, create a task, notify you, enrich, run a website audit, draft an AI follow-up, POST a webhook). Every rule can dry-run, shows its work in a log, and can wait for your approval — nothing sends by itself.

Triggers

Sixteen ways a rule starts.

Records

A new lead, contact or company — from your website, an import, a check-in, or by hand. Every creation path counts, and a new rule never fires retroactively on your history.

Deals

An opportunity moves stage, closes won, or closes lost — detected however it happened.

Zones

First view by a prospect, a question asked, a form submitted, a quote requested — a zone is a trigger surface. Your own team’s activity never fires anything.

Email engagement

A link clicked, opened three-plus times, a reply received, a bounce, an unsubscribe — straight off your tracked sends.

Sequences & events

A sequence finishes with no reply. Someone attends your event, or no-shows it. An import completes.

Timers

No touch in N days. A task goes overdue. A zone expires within a week. The quiet things that cost deals, watched for you.

Actions

Eighteen things a rule can do.

Work the record

Mark hot, set a field, add a note, add to a list, create an opportunity, move a stage — the writes you would do by hand, done the moment they matter.

Reach out

Enroll in a sequence, or send a template — through your normal send path with tracking, your unsubscribe footer and merge tags intact. Or pause a sequence when they reply.

Hand off

Create a task and assign it to a teammate. Notify yourself. Re-send a zone invite. Add them to an event.

Enrich & analyse

Run enrichment on company-owned domains only. Run a website audit. Ask the AI a question about the record and keep the answer as a note.

AI follow-up

Have the AI draft the follow-up from the thread and the record — it waits in your drafts, never auto-sent.

Webhook

POST the event to any URL you run — the power exit for everything else.

Control

Automation you can’t trust is worse than none.

So every rule shows its work, tests before it runs, and can ask you first.

  • See the flow — trigger → conditions → actions, drawn live while you edit. The picture cannot disagree with what Save stores.
  • Test before you trust — a dry run against your newest matching record: which gates pass, whether it would fire, exactly what it would do. Nothing executes.
  • Approve first, per rule — queue matches for your approval instead of acting. Sending a template? Behind the gate. Marking hot? Let it run.
  • An honest run log — every run records what it did, per action, with the date, including the skips: “already enrolled”, “do-not-contact”, “no email”.
Rule · Quiet for 14 days
Dry run · Meridian Dental Group
Newest matching record · nothing executed
GateResult
No touch in 14 dayspass · 19 days
Stage is Proposalpass
Not do-not-contactpass
Would fireyes · 2 actions
ActionsTask “Check in with Meridian” · AI draft to your drafts · awaiting approval
Conditions

Filter like your saved views.

Field, operator, value

The same conditions your lists and reports use. Match all or any. Reference the record, the deal, the person, the last email.

Company-owned domains only

One checkbox skips free-mail domains — so enrichment and sequences spend only on real prospects.

Questions

Straight answers.

Everything people ask, on one page: the full FAQ →

What can trigger an automation?

New records from any source, deal stage changes and closes, zone activity (first view, question, form, quote request), email engagement (click, three-plus opens, reply, bounce, unsubscribe), sequence and event outcomes, imports, and timers such as no touch in N days or an overdue task.

What actions can a rule take?

Work the record (mark hot, set a field, note, list, opportunity, stage), reach out (enroll in a sequence, send a template, pause a sequence), hand off (task, notify, re-send a zone invite, add to an event), enrich and analyse (enrichment, website audit, AI question kept as a note), an AI-drafted follow-up left in drafts, and a webhook POST to any URL.

Can an automation send email without me?

Only if you let that rule run without approval. Rules can be queued for your say-so, AI drafts always wait in your drafts, and every send goes through your normal send path with tracking and your unsubscribe footer intact.

Does a new rule fire on my old records?

No. A new rule never fires retroactively on your history, and your own team’s activity never triggers anything.

Can I test a rule before trusting it?

Yes. Every rule has a dry run that shows what it would have done, and an honest log of what it did.

Write the play once. Approve it every time, if you like.

Rules run on your machine, against your file. Nothing goes out unless you set it to.