HELP← All articles

Workflow automations

If-this-then-that rules that fire on backend events. Build the ones you'd otherwise nag your reps to remember.

Triggers

• deal_stage_changed — a deal moves between pipeline stages. Payload: contact_id, from, to, owner_user_id.
• deal_stale — a deal has sat in the same stage for N days (worker-driven, runs nightly). Payload: contact_id, stage, days_in_stage, owner_user_id.
• task_overdue — a task is past due. Payload: task_id, owner_user_id, days_overdue.
• contact_created — new contact added (via UI, CSV import, or Google Places). Payload: contact_id, owner_user_id.

Conditions (optional)

AND-list of field filters. Reference any key from the trigger payload. Operators: eq, ne, in, gt, lt, contains.

Example: only fire when a deal moves into proposal — condition { field: "to", op: "eq", value: "proposal" }.

Actions

• send_team_message — post to org / DM / a group. Body supports templates: {{owner_user_id}}, {{contact_id}}, etc.
• create_task — auto-spawn a task assigned to the deal owner (or a specific user). Title templated.
• send_email — outbound via Resend. Subject + body templated. Recipient can be the contact's email or a fixed address.

Build one

1. Settings → Manage automations.
2. Click + New rule.
3. Name it ("Notify Sam when a deal hits Proposal").
4. Choose trigger, then enter the action template body — Julie-style mustache: {{to}}, {{contact_id}}.
5. Save. It starts firing on the next matching event.

Testing before going live

Each rule has a Test button in its detail view. Paste a sample trigger payload and the rule shows you:

• Which conditions passed / failed
• What each action's rendered output would be
• Whether the rule WOULD fire if this were real

Nothing runs — it's a dry run.

Run history

Every fire — success, skipped (conditions failed), or error — is captured in workflow_runs. Visible per-rule in the detail view. Use this to debug rules that "should be firing but aren't" or that error during action execution.