Automations
Turn the follow-ups you keep forgetting into rules that run themselves, day and night.
About 11 minutes · Running the shop
An automation is a rule: when this happens, do that. When a form is submitted, text the person a booking link. When a call is missed, text them back. When an invoice fails, tell the owner. You set the rule once and it runs day and night, which is the point: the follow-ups you keep forgetting stop depending on your memory.
1Start from a recipe
- 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, and more.
- Turn one on. Enabling a recipe makes it yours. Open it to see exactly what it does and edit any step.
Automations
Missed call text-back
When a call is missed → text the caller
Form follow-up
When a form is submitted → text a booking link, open a deal, notify owner
Re-engage quiet investors
When an investor stalls 21 days → email from the owner
2Build your own
- Press New automation and pick a trigger. Thirty to choose from, across everything: contact created, deal stage changed, owner changed, form submitted, form started but abandoned, meeting booked or cancelled, email opened or clicked, text replied, call completed, missed, or voicemail, invoice paid or failed, payment link purchased, subscription started or cancelled, refund issued, scorecard off track, handoff overdue, investor stalled.
- 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.
- Add actions, in order. Sixteen of them: send an email (written inline or from a template), send a text, create a task, notify someone in the app, update any field, add to a list, move a deal stage, write to a scorecard, create or move Convoy items, call a webhook, wait, and stop.
- 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.
- 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
Automations › Form follow-up › Runs
Sarah Lin · form submitted
Texted booking link · deal opened · owner notified
Completed
James Okafor · form submitted
Waiting 1 day before the follow-up email
Waiting
Test entry · condition not met
Skipped: tag was not Investor
Skipped
4Three rules worth stealing
- 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.
- 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.
- Nothing rots. When a deal sits in a stage too long or an investor goes quiet, open a task and nudge the owner. Quiet things stop dying quietly.
Emails sent by automations respect every safety rule from Megaphone: suppression, unsubscribes, and the reputation firewall. Automated sends never override a block on their own.