Automations

1Start from a recipe

1. Open Automations. A gallery of ready-made recipes ships with every workspace, switched off: reply alerts, investor welcome, meeting prep, handoff follow-up, re-engage quiet investors, nudge the owner of a stale deal, and more.
2. Turn one on. Enabling a recipe makes it yours. Open it to see exactly what it does and edit any step.

2Build your own

1. Press New automation and pick a trigger. Thirty-seven to choose from, across everything: contact created or updated, a contact replied by text or by email, owner changed, investor stalled, a handoff created, accepted, declined, or overdue, deal created, stage changed or gone stale, task coming due, form submitted, form started but abandoned, meeting booked, cancelled, or held, event attended, a text received, email opened or a link clicked (security scanners left out), engagement changed, scorecard off track, call completed, missed, or voicemail, quote signed, invoice paid, payment failed, checkout abandoned, payment link purchased, subscription started or cancelled, refund issued, and a Facebook lead received.
2. Add conditions if the rule shouldn't fire every time. Conditions use the same plain filters as your tables. And they know their trigger: pick "payment link is purchased" and the condition builder offers your actual payment links by name, not a text box to guess in. You can't build a rule that silently never matches.
3. Add actions, in order. Nineteen of them: send an email (written inline or from a template), send a text, create a task or a deal, notify someone in the app, update any field (on the record, its company, or a contact's open deal), put the record on one of your stages, add to a list, move a deal to any stage (only from the stages you pick, if you like), write to a scorecard, create or move Convoy items, register someone for an event, call a webhook, wait, and stop.
4. Save and switch it on.

Wait

Pauses the rule for minutes, hours, or days before the next action. A wait between two emails is how you build a drip sequence.

Stop

Ends the rule early. Give each step its own condition and add stops, and one automation reads like a decision tree: six payment links can send six different welcome emails from one rule, with a catch-all at the bottom.

Notify by role

A notification can go to the record owner, teammates you pick, "Owners and admins" or "Everyone in the workspace". The last two are worked out each time the rule runs, so a new teammate is included without editing it, and only people whose role and access groups let them see the record get it.

When it runs

Update field can set a date and time field to the moment the step runs, or a date field to the day it runs (in your workspace's time zone). Tick "Only if the field is empty" and the first value stays: "First contacted at" is stamped once and never moved. A 0 or a No counts as a value.

Answers in words

A form's choice question stores a short value ("knee"); add .label to print what the person picked in your wording: {{custom.area.label}} reads "Knee", several picks joined with commas. The Insert row lists the chosen form's questions. A webhook's payload carries the same words beside each answer (area.label next to area).

Webhook

Posts the event, signed, to any URL. If some tool must stay in your stack, the rule can call it. This is also the door to Zapier or Make if you keep them around.

Run history

Every firing is logged: what triggered it, which steps ran, what happened. When you wonder "did it send?", the answer is here.

3Check what actually ran

4Three rules worth stealing

1. Speed to lead. When a form is submitted, text a booking link within the minute, open a deal, and create a task for the owner. The lead is answered while the interest is warm.
2. Money aftercare. When a payment link is purchased, send a welcome email that names the product and amount (the trigger carries the money with it), and notify the right teammate.
3. Nothing rots. When a deal goes stale (no activity for longer than its pipeline's "Rotting after" days, the deals the board flags as rotting) or an investor goes quiet, open a task and nudge the owner, or move the deal to a Stalled stage. It runs once per quiet spell and only for deals that go stale after you turn it on, so nobody is nagged every hour, and won and lost deals never trip it. Quiet things stop dying quietly.