Recipe book: ready-to-build automations
Written By Timothy Murenzi
Ready-to-build ideas, written as Trigger → (condition) → steps. Many have a matching template under + New automation; the rest take a minute to build or describe to Build with AI.
Client communication
Estimate approved → email the client a thank-you and next steps.
Payment made → email the client a thank-you. (Template: Thank-you after payment)
Project status changed → only if changed to On Hold → email the client an update.
Estimate viewed → wait 2 days → follow up to answer questions. (Template: Estimate follow-up)
Getting paid
Invoice created → wait for Invoice paid (7 days, continue anyway) → gentle reminder email. (Template: Overdue invoice reminder)
Invoice created → only if amount greater than 10000 → notify the owner to follow up personally.
Payment made → notify the project lead.
Contracts
Contract sent → wait for Contract signed (3 days, continue anyway) → reminder email. (Template: Unsigned contract reminder)
Contract signed → wait 1 day → welcome email + create kickoff task.
Project kickoff & flow
Project created → create your standard kickoff tasks and notify the team. (Template: Project kickoff checklist)
Estimate approved → set the project phase, create a kickoff task and email the client. (Template: Estimate approved → start the project)
Project phase changed → notify the team.
Leads & sales
Lead created (from a form) → welcome email, 24-hour follow-up task, alert the team. (Template: New lead welcome + follow-up)
Lead stage changed → wait a few days → check in. (Template: Stale lead nudge)
Lead status changed → only if changed to Won → onboarding tasks. (Template: Lead won → start onboarding)
Products & procurement
Product approved by client → create an order task and notify the team. (Template: Product approved → create order task)
Product status unchanged for 5 days → remind the assignee.
Item received → create an inspection task. (Template: Inspect the moment it arrives)
Silent shipment → task to chase the vendor. (Template: Silent shipment → chase the vendor)
Install confidence dropped → alert the project lead with {confidence-score} and {install-date}. (Template: Install confidence dropped)
Team & budget
Team member added → welcome email + setup tasks.
Time threshold reached → notify a manager when someone logs more than X hours in a week.
Change orders exceed budget % → notify the owner with {change-pct}. (Template: Scope creep alert)
Spec over allowance → flag it before the presentation. (Template: Allowance overrun alert)
Was this helpful?
More in Automations
Automations 101: What they are and how they work Getting started: enabling Automations and building your first one Trigger reference (the "when")Conditions: running only when it mattersStill need help? Ask the team