Module 03 of 06 · Automation Flow

Visual flows that move contacts — without locking you into our email.

Most "automation" tools assume you want to send emails. AuriusCRM doesn't. Build the workflow, then wire it to your own SMTP / SES / Resend / Slack / anything-with-a-webhook. We give you the triggers, conditions, and actions. You pick the messaging stack.

7Trigger types
8Action types
Branches
0Email nodes
Seven trigger types · the "when"

Every flow starts with something happening.

Each trigger is rate-limited per-contact to prevent runaway loops. Test fire any trigger against a sample contact before you flip the flow active.

Form submitted

most common

Fire when a contact submits any form — by name, ID, or "any form on this page". Passes the form payload to downstream actions.

payload: email, fields, ip, referrer, timestamp

Tag added / removed

React when a contact is tagged. Useful for "if they get tagged 'churned', start the win-back flow".

conditions: specific tag · any tag · tag pattern

Score threshold reached

"Score reaches 60" fires once per contact when they cross the line. Re-fires only after a reset.

operators: reaches · drops below · changes by ≥

Field changed

Fire when a custom field on a contact is changed. "If 'plan' becomes 'enterprise' → notify CSM."

operators: equals · contains · changes from X to Y

Inbound webhook

Any external system POSTs to your unique webhook URL. Stripe payment, Intercom message, GitHub event — all become trigger sources.

payload: full JSON body · signed for verification

Scheduled / recurring

Daily / weekly / cron-like schedule. "Every Monday 9am: pull contacts with no activity 30d → fire re-engage flow".

resolution: minute-level · timezone-aware

Funnel step completed

Tighter integration with the Funnel Builder. Fire when a contact passes a specific funnel step.

pairs with: tag · score · webhook (most common)

Eight action types · the "what to do"

Mutate the contact. Or call your own messaging stack.

Tag · score · update · note · enroll in another flow · branch · delay · webhook. That's the entire action vocabulary. No "send email" action because your email tool stays yours.

Want to send an email? Wire a webhook to Postmark / SES / Resend / Customer.io. AuriusCRM stays out of the deliverability business.

No "send email" action by design

Use the webhook action to call your own email service. We don't manage SPF / DKIM / IP reputation — you already have a tool for that.

Install-inactive workflow · safety by default

Every new flow lands INACTIVE. Activated by you. Never by accident.

AI-generated flow? Inactive. Pasted from a template? Inactive. Edited an active flow? Changes stash as a draft — the live flow keeps running. Three explicit gates before contacts hit production.

● INACTIVE — DRAFT

1. Build / generate the flow

Drop nodes manually, paste from a template, or describe what you want and let AI Copilot assemble the tree.

  1. Tree is schema-validated
  2. Saved as draft v1
  3. Zero contacts touched
● TEST FIRE — REVIEW

2. Test fire against a sample

Pick any real contact (or a synthetic test contact) and run the flow end-to-end. See exactly which actions would fire.

  1. Dry-run mode: no DB writes
  2. Replay against historical contacts
  3. Each step shows actual vs expected
● ACTIVE — LIVE

3. Flip the switch — once

One toggle. The flow becomes active for matching trigger events. Toggle off anytime; in-flight contacts complete or halt — your call.

  1. Activation logged with actor + timestamp
  2. Per-flow kill switch
  3. Edits go back to draft v2 → repeat
Audit log · undo stack · tree validation

Every change tracked. Every change reversible. For 24 hours.

Every node added, removed, edited, or moved lands on a per-flow audit log. Every save is a new version of the tree. One click reverts any change made in the last 24h — by you, a teammate, or the AI Copilot.

Tree validation runs before every save: invalid trees (orphan branches, infinite loops, missing actions) never persist. Validation errors surface inline next to the offending node.

flow · webinar-signup · audit log · last 24h
2m ago Sarah Chen edited condition: team_size > 50 → ≥ 50 undo
17m ago AI Copilot added action: tag "hot-enterprise" after condition[true] undo
1h ago Sarah Chen activated flow (was: INACTIVE → ACTIVE) undo
3h ago Sarah Chen test fire on contact #4821 → 4 actions would fire · approved
5h ago AI Copilot created flow from prompt: "tag hot leads & ping sales" undo
5h ago System tree validation passed · 5 nodes · 0 errors · 0 email nodes

Trigger, branch, act. Inactive until you say so.

Build a flow in the playground at demo.auriuscrm.com. Drag triggers, drop actions, see the tree validate live.