Build guides for the automations service businesses actually run
Every guide here is a full build: the trigger, the guards, the message copy, the compliance step everyone forgets, and a realistic cost estimate. Written for owners and operators of appointment-driven businesses, not for a demo video.
What this collection is for
These are build guides, not overviews. Each one takes a single workflow that service businesses run constantly, and writes out the whole thing: what fires the automation, the guards that stop it doing something stupid at 2am, the exact message copy, what happens when someone replies, and the compliance step that gets skipped in every YouTube version. You can follow one end to end and have the workflow running, without buying anything from us.
They are the same builds we ship on client projects, published in full. If you read one and think “I could do that”, you probably could. If you read one and think “I do not want to own this”, that is cheaper to discover here than three weeks into a build.
Twenty-three guides sit here. Three of them are the core workflows almost every appointment-driven business should consider; the rest are either the same workflow written against a specific piece of software you already pay for, or the unglamorous infrastructure that decides whether the build is legal and affordable. Not every guide applies to you, and most readers need two.
Skip this hub entirely if you do not yet know which task is worth automating. A build guide will happily walk you into automating the wrong thing beautifully. Work through the automation audit template or the task prioritizer first, and skip it too if the thing you want is a document rather than a running workflow - that is templates.
How to choose
Ask these three questions in order. The first one usually picks the guide on its own.
First: where are you losing money? Pick by the leak, not by which build sounds most interesting. The three core guides map onto three different leaks.
- Missed call text-back - if the phone is how work arrives. For trades, mobile services, and anyone who cannot answer while their hands are busy. A missed call is a customer who is already dialling the next name on the list, and a text within sixty seconds is usually enough to stop them. This is the cheapest genuinely useful automation most businesses will ever build, and the right first one for HVAC and plumbing firms and cleaning companies.
- Quote follow-up - if you send estimates and they go quiet. For anyone whose sale involves a number sent by email and then silence. The work here is mostly nerve: a four-touch cadence that stops the moment someone replies recovers a meaningful share of quotes that would otherwise die, and nobody has to feel like they are nagging. Most relevant to contract cleaners and job-based trades.
- Appointment reminders - if your calendar is your capacity. For dental practices, salons and barbershops, clinics, and anyone selling booked time. A no-show is an hour you can never resell, so the guide covers two-way confirmation and waitlist backfill rather than the one-way “see you tomorrow” text your booking tool already sends.
Four other leaks have their own guides. If money is sitting in unpaid invoices, read QuickBooks invoice chasing. If estimates go out and die, the specialised versions are unsold estimate follow-up for contractors and quote to booking for cleaning companies. If you buy leads, the difference between a reply in one minute and one hour is most of your return, which is what Facebook Lead Ads to SMS and the speed-to-lead entry are about. If new work arrives by referral, the compounding one is automated review requests, and for repeat-visit businesses, salon client win-back.
If more than one applies, build the one whose failure costs you the most per incident, not the one that happens most often. And if none of them is obviously your biggest leak, do not start with a guide at all - work through the automation audit template first and let the scoring pick for you.
Second: what software are you already paying for? Field service and practice management tools each have their own gaps, and a guide written against yours will save you a day of guesswork. On Jobber, start with the full Jobber and n8n integration then Jobber quote follow-ups. On Housecall Pro, the two are the missed call text-back gap and Housecall Pro to Google Sheets. On ServiceTitan, read ServiceTitan automation without Zapier. Dental practices on Open Dental want the recall automation guide and the wider dental industry page.
Third: does it send text messages, and what will it cost to run? Two guides are not workflows at all and are the ones most likely to save you real money. If your build texts customers in the US, the A2P 10DLC guide covers the registration everyone discovers after their messages start silently failing - see also A2P 10DLC and STOP handling. And before you self-host anything to save a subscription, the true cost of self-hosted n8n prices the hours you would be substituting for the fee.
The order to read them in
Twenty-three guides is a pile, not a path. Read in this order and each one assumes only what the previous stage taught you. Read out of order and you will hit an authentication wall, a carrier registration you did not know existed, or a bill you did not price - all three of which are covered in a guide you skipped.
Stage one: foundations, before you build anything. Assumes nothing. You need four ideas and roughly an hour. A webhook is how one system tells another that something happened, and the alternative is polling, which is what you fall back to when the software will not push. Idempotency is what stops a retry texting the same customer four times. Error handling is the difference between a workflow that fails loudly and one that fails silently at 2am. And an API key is the thing you will spend longer obtaining than building with. What is an AI agent and workflow design cover the rest of the vocabulary.
Stage two: one beginner build, end to end. Assumes stage one and an account on a workflow platform. Pick a single guide marked Beginner in the table below and finish it, including the parts that are boring. The point is not the workflow, it is finding out which step in your own business is actually the hard one. For most people it is the credentials, not the logic. Missed call text-back is the usual first build because its failure is visible within a minute and it costs almost nothing to run.
Stage three: the version written against your own software. Assumes you have built one thing and can read an API response without flinching. Jobber, Housecall Pro, ServiceTitan and Open Dental each have their own quirks - what they expose, what they refuse to expose, and which events fire late. A guide written against yours saves a day of guesswork, and the ServiceTitan and Open Dental builds are marked Advanced for a reason: both involve credentials that a third party has to approve.
Stage four: compliance and cost, before you scale. Assumes something is running. Two guides here are not workflows at all and both save more money than any build. If your automation texts anyone in the US, the A2P 10DLC guide covers the registration people discover only after their messages stop arriving, and it pairs with opt-in and STOP handling. Before you move anything to your own server to save a subscription, the true cost of self-hosted n8n prices the hours you would be substituting for the fee.
One honest caveat about the whole sequence: not everyone should complete it. If after stage two you find the build itself was fine but the thought of owning it in eighteen months makes you tired, that is a real answer and a cheap one to discover. Stage four is where the ongoing work lives, and it does not go away.
Every guide, the problem it solves, and what it costs you in time
Sorted roughly by how hard the first build is. The time and difficulty columns are our estimates for someone building it for the first time, not measured figures - the variable that actually decides them is how long it takes to get credentials approved, which is outside anyone's control.
| Guide | Problem it solves | Built on | Time (estimate) | Level |
|---|---|---|---|---|
| Missed call text-back | An unanswered call becomes the next firm's job | n8n + Twilio | Half a day | Beginner |
| Facebook Lead Ads to SMS | Paid leads go cold in the minutes before anyone calls | Meta Lead Ads + n8n + SMS | Half a day | Beginner |
| Automated review requests | Referrals depend on reviews nobody remembers to ask for | n8n + job source + SMS or email | Half a day | Beginner |
| Housecall Pro to Google Sheets | Reporting you cannot get out of the software you pay for | Housecall Pro API + Google Sheets | Half a day | Beginner |
| Quote follow-up | Estimates go out and then go quiet | n8n + email and SMS | About a day | Beginner |
| AI appointment reminders | A no-show is an hour of capacity you can never resell | n8n + booking system + SMS | About a day | Intermediate |
| QuickBooks invoice chasing | Cash sitting in invoices nobody has chased | QuickBooks Online + n8n | About a day | Intermediate |
| Unsold estimate follow-up | Contractor estimates that die without a decision | n8n + your estimating tool | About a day | Intermediate |
| Cleaning quote to booking | Quotes that never turn into a scheduled clean | n8n + scheduling | About a day | Intermediate |
| Salon client win-back | Regulars quietly stop rebooking and nobody notices | n8n + salon booking system | About a day | Intermediate |
| Jobber quote follow-ups | Jobber sends the quote and then stops | Jobber + n8n | About a day | Intermediate |
| Housecall Pro missed call text-back | The gap Housecall Pro leaves on missed calls | Housecall Pro + n8n + Twilio | About a day | Intermediate |
| Calendly no-show follow-up | A missed consultation gets one email and then nothing | Calendly API + n8n + SMS | Half a day | Beginner |
| ServiceM8 quote follow-up | Not knowing whether the built-in follow-up is enough | ServiceM8 Automation add-on + API | Half a day | Beginner |
| Square Appointments no-show follow-up | No-shows are marked and never invited back | Square Bookings API + n8n + SMS | About a day | Intermediate |
| Xero overdue invoice reminders | Email reminders that homeowners never open | Xero Accounting API + n8n + SMS | About a day | Intermediate |
| Housecall Pro estimate follow-up | Estimates still open after the third resend | Housecall Pro Pipeline + API + n8n | About a day | Intermediate |
| Clio Grow intake follow-up | Enquiries that wait until someone has time to reply | Clio Grow API + n8n | One to two days | Intermediate |
| Jobber and n8n, the full build | Jobber data that cannot reach anything else | Jobber API + n8n | One to two days | Intermediate |
| ServiceTitan without Zapier | Paying per task for automation the API gives you | ServiceTitan API + n8n | Around two days | Advanced |
| Open Dental recall automation | Overdue recalls that nobody has time to chase | Open Dental API + n8n | Around two days | Advanced |
| A2P 10DLC registration | US texts failing silently after everything looked fine | Twilio + carrier registration | An hour of forms, then days of waiting | Unavoidable |
| n8n self-hosted true cost | Deciding whether self-hosting really saves the subscription | n8n cloud against n8n self-hosted | A reading job, not a build | Decision |
Which guide fits my situation
Two ways in. Find your trade first, because the trade decides which leak is expensive. Then find your job, because the job decides how much of the build you will personally be doing.
By industry
Trades and field service. HVAC and plumbing firms and roofing contractors, whose numbers sit on the roofing receptionist cost page, lose most of their money at the phone and at the unsold estimate, so missed call text-back then unsold estimate follow-up is the pair. If you run Jobber, Housecall Pro or ServiceTitan, jump to the guide named after it after your first build rather than before.
Cleaning and recurring service. Cleaning companies convert on speed and on follow-up, so quote to booking is the highest-value first build, with review requests second because recurring contracts are won on reputation.
Clinics and appointment-driven practices. Dental practices, medical clinics and veterinary clinics sell booked time, so reminders come first and recall second. Read the compliance section of your industry page before the build, not after - patient data changes which steps can be automated at all.
Personal care and repeat visits. Salons and barbershops and gyms and fitness studios live on rebooking, which makes win-back by interval the one that compounds.
Professional services and property. Law firms, accounting firms, real estate agencies and property management usually leak at intake and at billing, so invoice chasing and speed-to-lead on new enquiries beat anything customer-facing. Confidentiality constrains which model can see the text, which is what the models directory is for.
Retail, restaurants and auto. Ecommerce and retail, restaurants and auto repair shops sit slightly outside this collection, since volume support and inventory matter more than quote chasing. Start at the industry page and treat the guides here as patterns.
By role
Owner-operator, doing it yourself in the evenings. Take one Beginner guide and nothing else. Your constraint is uninterrupted hours, so pick the build with the fewest systems in it, and use the ROI calculator first to make sure the hours are worth spending at all. If the payback is longer than a quarter, hand it over instead.
Office manager or operations lead. You know the process better than anyone and probably do not have admin rights on half the systems. Start by writing the process down with the process documenter and use the integration checker to find out what your software will actually let you connect to before you promise anyone a timeline.
Technical person at a non-technical company. The builds will not be your problem; the ownership will. Read the handover section below first, build second, and make sure someone other than you can restart the thing. The implementation checklist is the artefact that makes that real.
Agency or consultant building for clients. These guides are the same builds we ship, published in full, and you are welcome to use them. The commercial parts are elsewhere: the proposal template and the agency pricing calculator cover scoping and pricing, and the agency bootcamp covers the rest of the operation.
Someone evaluating whether to hire this out. Read one guide end to end. That is the fastest honest way to find out what you are buying, and it makes every quote you receive easier to judge. Then read consultant versus agency versus DIY and what a consultant actually does.
What to do after you finish one
A guide ends when the workflow runs. That is roughly halfway. The gap between a workflow that works on your laptop on a Tuesday and one the business can rely on for a year is four things, and none of them are difficult - they are just never in the tutorial.
Make it survive failure. Every external system in your build will be down at some point, will rate limit you at some point, and will return something unexpected at some point. Add retry with backoff on anything transient, make the whole run idempotent so a replay does not double-text anyone, and put a queue in front of anything bursty. The single highest-value change is a failure path that notifies a human, because the default failure mode of an automation is silence.
Watch it. Observability sounds like an engineering word and means something small here: for every run, you should be able to see that it happened, what it decided, what it sent, and what it cost. Three numbers on a weekly basis are enough to start - runs attempted, runs failed, and messages sent - plus an alert when failures exceed a threshold you set now rather than after the first incident. If the workflow uses a model, log spend per run too; a runaway loop is a four-figure surprise otherwise.
Know your platform well enough to fix it. The guide taught you one workflow on one platform. Everything else that platform does - versioning, credentials, environments, what happens on an upgrade - is on its page in the platforms directory. Start with n8n if that is what you built on, Make.com or Zapier if you translated the logic across, and Vapi if the next thing you build answers the phone. The n8n versus Zapier comparison is the one to read if the per-task bill has started to sting.
Hand it over properly, even to yourself. Write down what it does, what it must never do, who owns it, how to turn it off, and where the credentials live. That last item is the one that strands businesses: an automation wired to a personal account stops the day that person leaves. Handover is a deliverable, not a conversation, and it is the part we insist on in every build we ship. The workflow brief template gives you the format.
If you want the structured version of all four, the courses cover them at more depth than a hub page can: n8n AI agents for the build layer, production-grade agent engineering for the reliability and monitoring layer, and AI agents for operators if you are the person who will own it rather than the person who built it. All of them are listed on the courses page.
And once one workflow is stable, the second is far cheaper than the first, because the credentials, the guards and the monitoring already exist. That is the point at which most businesses stop treating automation as a project and start treating it as a capability. What the second and third builds typically cost, whether you do them or we do, is set out on the AI automation cost page and, per trade, on the HVAC cost breakdown and the dental one.
Where this sits next to the other hubs
Guides are the wiring: one workflow, built end to end, on a named stack. The neighbouring hubs each answer a different question, and mixing them up is why people read for hours without deciding anything. Agent playbooks describe the shape of a job without naming a stack. Platforms answers what you build on; models answers which LLM does the reasoning and what it costs per million tokens; and compare breaks a tie between two candidates from either.
Upstream of all of them, the free tools decide whether the workflow deserves automating at all, and the learning guides supply the vocabulary if terms like webhook or idempotency are new. Downstream, templates hold the documents a build produces and the blog holds the longer write-ups on evals, monitoring and cost.
What to do first
Before you open a workflow editor, do three things. Write down the process as it happens today, including who does it and what they do when it goes wrong - if you cannot write it, you cannot automate it. Check whether the tool you already pay for does it: an uncomfortable share of automation requests are features nobody switched on. Then decide your platform, because it sets your recurring bill for as long as the workflow lives. Our guides use n8n, but n8n versus Make covers the trade-off honestly, and the stack picker will shortlist from your own constraints.
Then run the numbers before you spend a weekend. Minutes per run, times runs per month, times the loaded hourly cost of whoever does it. The ROI calculator does the arithmetic, and what AI automation costs gives market-typical figures for the paid version of the same build, so you can see what your time is substituting for.
When to hand it off instead
Building it yourself is the right answer more often than an agency will admit, but not always. Hand it over when the workflow touches money or customers without a human check and you are unsure of the failure modes; when it spans three or more systems, because each one adds an authentication method, a rate limit, and a way to fail silently; when your data is inconsistent enough that no rule can classify it; or when nobody in the business will own the thing in six months. That last one is the real test - a workflow nobody maintains is a liability with a subscription attached.
The consultant versus agency versus DIY comparison puts the routes side by side on cost, speed, ownership, and maintenance, and the hiring checklist is worth reading before you pay anyone, us included.
What to read next
After your first build, the highest-value next read is your own trade rather than another guide. The industry pages list the four or five workflows worth building in a given business and, just as usefully, the ones to leave alone. If you would rather someone else scoped it, the free automation audit ends with a written roadmap you keep whether or not you hire us.
Questions people ask
Do I need to pay for anything to follow these guides?
No. Every guide is published in full, including the trigger, the guards, the message copy and the compliance step. You will pay for the tools the build runs on - a workflow platform and, for anything that texts or calls, a telephony provider - but nothing to us.
Which guide should I start with?
Whichever matches your biggest leak. If the phone is how work arrives, missed call text-back. If you send estimates that go quiet, quote follow-up. If booked time is your capacity, appointment reminders. If more than one applies, build the one whose failure costs the most per incident.
Do the guides only work with n8n?
The builds are written against n8n because that is what we ship on, but the logic transfers. The trigger, the guards, the stopping rules and the review points are the same on Make or Zapier; only the node names change. The platforms directory and the n8n versus Make comparison cover the trade-off.
How is a build guide different from an agent playbook?
A playbook describes the shape of a job - the workflow, the source data, the human review points - without naming a stack. A guide is one of those workflows built end to end on a specific stack, with the configuration left in.
What if my field service software is not covered?
Read the core guide for the workflow and treat the software-specific ones as worked examples of the same pattern. Most of these tools expose either a webhook or a polling API, and the integration checker will tell you which you are dealing with.
When should I hand the build over instead?
When it touches money or customers without a human check and you are unsure of the failure modes, when it spans three or more systems, when your data is inconsistent enough that no rule can classify it, or when nobody in the business will own it in six months. That last one is the real test.
In what order should I work through the guides?
Foundations first, then one beginner build end to end, then the software-specific version for the tool you already pay for, then the compliance and cost guides before you scale. Most people skip straight to the guide matching their software and hit an authentication or registration wall that a foundations read would have warned them about. The reading order section on this page lays out all four stages with what each one assumes.
How long does a first build actually take?
Our estimates run from half a day for missed call text-back to around two days for the ServiceTitan and Open Dental builds, and they are estimates rather than measurements. The variable is almost never the workflow. It is getting API credentials approved, waiting on carrier registration for SMS, and discovering that your data is messier than you thought. Budget double for anything touching software you do not administer yourself.
Build guide - n8n + Twilio
Missed Call Text-Back with n8n (Free Build Guide)
Build missed call text-back in n8n with Twilio: business-hours guard, AI qualification reply, and calendar booking - plus the A2P 10DLC step nobody covers.
Read the guide
Build guide - follow-up automation
Automate Quote Follow-Up (Build Guide + Templates)
A 24h/3d/7d/14d quote follow-up cadence with copy-paste message templates, stop-on-reply logic, and an n8n or Make build outline you can ship this week.
Read the guide
Build guide - reminders
AI Appointment Reminders That Cut No-Shows
Two-way appointment reminders that confirm, reschedule and backfill from a waitlist: the 48h, 24h and morning-of cadence, reply handling and SMS rules.
Read the guide
Build guide - Jobber + n8n
Jobber + n8n Integration: The Full Build
There is no Jobber node in n8n. How to authenticate to Jobber's GraphQL API from the HTTP Request node, verify webhooks and ship a working workflow.
Read the guide
Build guide - Jobber quotes
Jobber Quote Follow-Up Automation Past 2 Reminders
Jobber sends two automated quote follow-ups on Connect and up. The exact limit, and the four-touch sequence to build alongside it when two is not enough.
Read the guide
Build guide - Housecall Pro
Housecall Pro Missed Call Text Back: Setup and Gaps
Housecall Pro's missed call automation sends one text, then replies wait for a human. Here is how to build the two-way conversation that books the job.
Read the guide
Compliance guide - A2P 10DLC
A2P 10DLC Guide for SMS Automation Builds
The registration step that blocks every missed call text-back build: brand before campaign, the sole proprietor route, real fees and why campaigns fail.
Read the guide
Build guide - Housecall Pro + Sheets
Housecall Pro to Google Sheets, For Real
Housecall Pro's API and webhooks are MAX-plan only. Here is the real build: the events worth syncing, a sheet that does not fall over, and failure handling.
Read the guide
Build guide - Open Dental API
Open Dental Recall List Automation via the API
Pull the Open Dental recall list through the API and send a reminder cascade from it. ODFHIR auth, the permission tiers and prices, and the BAA step.
Read the guide
Cost guide - n8n hosting
n8n Self-Hosted True Cost vs Cloud (2026)
Self-hosting n8n is free to license and not free to run. Cloud prices as of August 2026, the real release cadence, and an honest hours-included comparison.
Read the guide
Build guide - Meta lead ads + SMS
Facebook Lead Ads to SMS: Instant Speed-to-Lead
Meta's leadgen webhook sends an ID, not a lead. Here is the Graph API retrieval, the permissions and 90-day limit, consent wording, and the first-minute text.
Read the guide
Build guide - review requests
Automated Review Requests After Every Job
Job completion, payment or a delay? The trigger decides everything. Google's policy on gating and incentives, the review link, and a two-message sequence.
Read the guide
Build guide - QuickBooks Online
QuickBooks Invoice Chasing: The Real Ladder
A three-stage overdue invoice sequence built on the QuickBooks Online API: soft, firm, then a human. Stop-on-payment logic and copy for every rung.
Read the guide
Build guide - unsold estimates
Automate Unsold Estimate Follow-Up for Contractors
Automate unsold estimate follow-up for HVAC, plumbing and electrical contractors: the estimate-state trigger, five touches of real copy and stop-on-reply.
Read the guide
Build guide - ServiceTitan API
ServiceTitan Automation API Without Zapier
ServiceTitan API access is plan-gated before you write a line of code. The plan gate, the client-credentials auth, the API surface, and the published limits.
Read the guide
Build guide - salon win-back
Salon Client Win-Back Automation by Interval
A flat 90-day win-back rule chases loyal clients and misses lapsed ones. Build it on each client's own service interval instead, with honest offer advice.
Read the guide
Build guide - cleaning quotes
Cleaning Company Quote to Booking Automation
Quote request to booked job for a cleaning company: instant acknowledgement, the questions that let you price without a site visit, and the follow-up ladder.
Read the guide
Build guide - Calendly
Calendly No-Show Follow-Up: Beyond One Email
Calendly emails no-shows on Standard and up, once you mark them. Here is the webhook build that adds a text, a second touch and a stop when they rebook.
Read the guide
Build guide - Square Appointments
Square Appointments No-Show Follow-Up Build
Square sends reminders and can charge a no-show fee. It does not document a rebooking message afterwards. Here is the Bookings API build that sends one.
Read the guide
Build guide - Xero
Xero Overdue Invoice Reminders by SMS and Email
Xero already emails payment reminders. Here is when that is enough, and the API build that adds a text, a personal email and a handover for the rest.
Read the guide
Build guide - Clio Grow
Clio Grow Intake Follow-Up: API Build Guide
The Clio Grow API documents no webhooks, so intake follow-up means polling. Here are the endpoints, permissions, rate limit and a three-touch sequence.
Read the guide
Build guide - ServiceM8
ServiceM8 Quote Follow-Up: Native or Custom?
ServiceM8's Automation add-on sends up to five quote follow-ups on every plan. Here is how to set it up well, and the four gaps worth a custom layer.
Read the guide
Build guide - Housecall Pro estimates
Housecall Pro Estimate Follow-Up: Past Touch 3
Housecall Pro's Pipeline resends an estimate three times, then declines it. Here is how to tune that, and the MAX-plan build that adds touches four and five.
Read the guide
Start here
Free AI Automation Audit Template
Score your recurring tasks and rank the top three worth automating before you pick a tool.
Done for you
Rather not build it yourself?
We scope and ship these workflows for businesses of any size, and the consult is free.
