Guides/CRM

How to build automations for your business

By Brad Bone, co-founder of RiverX AI · Updated October 2026

An automation is a rule that does a boring task for you every time, without you thinking about it. When a lead comes in, it gets a text. When a job is booked, it goes on the calendar. When a job is done, a review request goes out. The alternative is you or your office person doing each of those by hand, every day, until one of you forgets.

2 of 7 · 12 steps
Short answer

An automation is a rule that fires when something happens, so a repetitive task runs without you. List the tasks you do over and over, pick a tool that fits the flow, start from the trigger, clean the data, test with a fake lead, and add a failure alert so a broken automation never drops a lead silently.

Time2 to 4 hours to set up your first few, then 15 minutes a month to check them
Cost to do it yourselfFree to about $50 a month for a tool like Zapier, Make, or n8n
DifficultyMedium. Simple automations are easy. Multi step flows take care.
Best forAny business that does the same follow up, booking, or logging tasks every day
Why it matters

Every task you do by hand is a task you will eventually forget. A lead that does not get a text back, a job that never goes on the calendar, a review request that never goes out. An automation does it every time, the same way, without you remembering.

The businesses that automate the repetitive stuff are not the ones with the most software. They are the ones whose leads never sit waiting for someone to get around to them. A simple automation that texts a new lead in under a minute beats a perfect process that runs when someone has time.

What you need
  • A list of the tasks you or your team do over and over by hand
  • An automation platform: Zapier for simple flows, Make or n8n for complex ones
  • API or webhook access to the tools you use, like your CRM, calendar, and phone
  • A test environment so you do not break a live automation on a real customer
  • A way to get alerted when an automation fails, like an email or a text to yourself
Step by step
  1. 1

    List the tasks you repeat every day

    Before you build anything, write down the tasks you or your team do over and over. These are the automations worth building. Do not automate things you do once a month. Automate the ones you do ten times a day.

    1. 1. For one day, write down every time you copy info from one place to another, or send the same kind of message.
    2. 2. Mark the ones you do more than once a day. Those are your first automations.
    3. 3. Mark the ones that, if you forgot them, would cost you a lead or a job.
    4. 4. Leave the once a month tasks off the list for now.
    Example

    Your list: text a new lead back, add a website lead to the CRM, text a confirmation when a job is booked, send a review request when a job is done, remind a tech about tomorrow. Five tasks, all repeated every day, all easy to forget.

  2. 2

    Pick the right tool for the job

    Zapier is the easiest for simple, one step automations and it connects to almost everything. Make and n8n are better for multi step flows with branches and conditions. Match the tool to the flow, not the other way around.

    1. 1. If your automation is one trigger and one action, like a form submit sends a text, use Zapier.
    2. 2. If it has branches, like check if the lead is new, then route by zip code, use Make or n8n.
    3. 3. Check that the tool connects to your CRM, calendar, and phone before you commit.
    4. 4. Start on the free or cheapest plan. Upgrade only when you outgrow it.
    Example

    A missed call text back is one trigger and one text, so Zapier handles it. A new lead flow that checks for duplicates, routes by territory, and books by availability has branches, so it belongs in Make or n8n.

  3. 3

    Start with the trigger

    Every automation starts with a trigger, the event that kicks it off. A new lead, a booked job, a completed job, a form submission. Get the trigger right, because a wrong trigger fires the automation at the wrong time or not at all.

    1. 1. Name the exact event that should start the automation, like a new contact in the CRM or a webhook from your website.
    2. 2. Find that event in your tool's trigger list and connect it.
    3. 3. Send a test event and confirm the automation sees it.
    4. 4. If the trigger does not fire, check the webhook or the connection before you build the rest.
    Example

    Your trigger is a new form submission on your website. You connect the webhook, submit a test form, and the automation logs the lead. If nothing shows up, the webhook URL is wrong or the form is not sending to it. Fix that before you add the next step.

  4. 4

    Clean the data before it moves

    Before the automation does anything with a lead, clean the data. Fix the phone number format, standardize the address, split the name into first and last. If you push a messy lead into your CRM, you get a messy contact, and a phone number missing the area code breaks the SMS step later.

    1. 1. Add a step right after the trigger that formats the phone number to a single standard.
    2. 2. Split a full name into first and last if your CRM needs them separate.
    3. 3. Trim extra spaces and fix common typos, like a missing zip code.
    4. 4. If a required field is empty, like no phone number, stop the automation and flag it instead of sending a half lead.
    Example

    A lead comes in as '555-1234' with no area code. Your cleanup step sees it is missing the area code, adds your local area code, and formats it as '+16615551234'. The SMS step now works. Without the cleanup, the text fails and you never know.

  5. 5

    Send the right message to the right person

    The most common automation is a text or email that goes out when a lead comes in. Write it like a person, not a robot. The message is the first thing the lead sees, so make it sound like you.

    1. 1. Use the customer's first name, your name, and the company name.
    2. 2. Ask one clear question that moves the lead toward a booking.
    3. 3. Send it within a minute of the trigger, not an hour later.
    4. 4. Do not send a form letter that says a representative will contact you. Send something a person would send.
    Example

    A good first text: 'Hi Maria, it's Brad with Henley Roofing. I saw you reached out about a leak. I can come out Tuesday at 10 or Wednesday at 2, which works?' A bad one: 'Thank you for your inquiry. A representative will be in touch.'

  6. 6

    Build your three starter automations

    Start with the three automations that pay for themselves fastest: a missed call text back, a new lead alert, and a job done review request. Build these three first, get them working, then add more. These three cover the leads you lose to voicemail, the leads you lose to a slow reply, and the reviews you lose to never asking.

    Example

    You build the missed call text back first. A customer calls at 6 PM while you are on a roof. The call goes to voicemail, but the automation texts them back in under a minute. They reply, you call them when you are off the roof, and you book the job. Without the text, they call the next roofer on the list.

    Copy thisMissed call text back: Trigger: Missed call on your business number Action: Text the caller within 60 seconds Message: 'Hi, sorry we missed your call. This is {company}. How can we help? If you need to book a job, we have openings {times}.' New lead alert: Trigger: New form submission or new CRM contact Action: Text you and your team the lead's name, number, and what they need Message: 'New lead: {name} at {phone}. They asked about {service}. Call them back.' Job done review request: Trigger: Job marked complete in your CRM or job software Action: Wait 30 to 60 minutes, then text the customer a review link Message: 'Hi {first name}, it's {company}. Thanks for having us out. If we did a good job, would you leave us a quick review? {review link}'
  7. 7

    Route leads to the right person

    If you have more than one tech or rep, route the lead to the right one based on the job. Do not send every lead to the owner, because the owner is on a roof and cannot call them back. Route by territory or job type and the right person handles it.

    1. 1. List your techs or reps and the territory or job type each one handles.
    2. 2. Add a branch in the automation that checks the lead's zip code or the service they asked for.
    3. 3. Send the lead to the matching person, and only that person.
    4. 4. If no one matches, send it to the owner as a fallback so it never sits unassigned.
    Example

    A lead in Bakersfield goes to your Bakersfield tech. A commercial account goes to your sales rep. A lead with no clear match goes to you, the owner, so it never falls through. Every lead lands with the person who can actually call it back.

  8. 8

    Connect your accounting tool

    When a job is won, push it to QuickBooks or your invoicing tool so the invoice goes out without someone typing it in by hand. If you invoice by hand, you forget some, mistype others, and wait three days to send them. An automation that creates the invoice when the job is marked won gets it out the same day and you get paid faster.

    1. 1. Find the event in your CRM that means a job is won, like a stage change to Won.
    2. 2. Connect that event to QuickBooks or your invoicing tool.
    3. 3. Map the job details, customer, and amount to the invoice fields.
    4. 4. Send a test invoice to yourself to confirm it looks right before it goes to a customer.
    Example

    You mark a job Won on Friday. The automation creates a draft invoice in QuickBooks with the customer, the job, and the amount. You review it Monday morning and send it. Without the automation, that invoice sits in a notebook until you remember it, and the customer pays two weeks later.

  9. 9

    Build in failure alerts

    Every automation should tell you when it breaks. If the webhook does not fire, or the API call fails, or the SMS does not send, you need to know. An automation that fails silently is worse than no automation, because you think it is working when it is not.

    1. 1. Add an error path to every automation that sends you a text or email when it fails.
    2. 2. Include what broke, which automation it was, and the lead it was working on.
    3. 3. Send the alert to yourself and one other person, so it is not missed on a busy day.
    4. 4. Test the alert by breaking the automation on purpose once, so you know it fires.
    Example

    Your new lead automation tries to send a text, but the phone API is down. The error path texts you: 'New lead automation failed. Lead: Maria at 555-1234. SMS did not send.' You call Maria yourself instead of losing the lead to a silent failure.

  10. 10

    Test with a fake lead first

    Before you turn an automation on for real, run a fake lead through it. Submit a test form, book a test job, mark a test job done. Watch what happens at each step. You want to find out in testing, not when a real customer is waiting for a reply.

    1. 1. Create a fake lead with a phone number you control, like your own cell.
    2. 2. Run it through the full automation, trigger to last step.
    3. 3. Check that each step did what it should, and that the message looks right.
    4. 4. Fix anything that broke, then run the fake lead again until it is clean.
    Example

    You submit a test form as 'Test Tester' with your own number. The automation sends you a text, creates a CRM contact, and routes it to you. You see the message has a typo in the company name. You fix it, run the test again, and it is clean. Now you turn it on for real.

  11. 11

    Document what each automation does

    Write down what each automation does, in plain English, in one place. When you forget what it does, or someone new joins, the documentation is how you avoid breaking it. An automation with no documentation breaks the day the person who built it leaves.

    1. 1. For each automation, write one sentence on what triggers it and what it does.
    2. 2. Note which tool it lives in and who built it.
    3. 3. Keep the list where your team can find it, not in one person's head.
    4. 4. Update the note any time you change the automation.
    Example

    Your note: 'Missed call text back, in Zapier. When a call to the business number goes unanswered, it texts the caller within 60 seconds with a link to book. Built by Brad. Last updated October 2026.' When someone asks what it does, you point at the note instead of digging through Zapier.

  12. 12

    Review the automations monthly

    Once a month, check that every automation is still running and still doing what you want. Tools change, APIs change, and automations break quietly. A monthly check catches the broken ones before they cost you leads. If you do not check, the first sign an automation broke is a customer who never got a reply.

    1. 1. Open your automation tool and look at the run history for each automation.
    2. 2. Check for failures and fix the ones that broke in the last month.
    3. 3. Confirm each one is still doing what you want, or update it.
    4. 4. Turn off any automation you no longer use, so it does not fire by mistake.
    Example

    Your monthly check shows the review request automation has not fired in two weeks. You look and find the trigger changed when your job software updated. You reconnect it, run a test, and it works again. Without the check, you would have gone a month with no review requests and never known.

What to avoid
  • Automating tasks you only do once a month instead of the ones you do every day.
  • Building a complex flow in a simple tool, or a simple flow in a complex one.
  • Pushing messy data through the automation without cleaning it first.
  • No failure alerts, so a broken automation drops leads silently.
  • Turning it on without testing, so the first real lead gets a broken message.
  • No documentation, so no one knows how it works when the builder leaves.
  • Building ten automations at once instead of three that actually work.
Common questions
What is the difference between Zapier and Make or n8n?

Zapier is easiest for simple, one step connections. Make and n8n handle multi step flows with branches and conditions, and cost less at scale. Use Zapier for simple, Make or n8n for complex.

How do I know if an automation broke?

Set up a failure alert that emails or texts you when an automation fails. Without it, the first sign is a customer who never got a reply, weeks later. With it, you find out the same day.

What should I automate first?

Start with the three that pay for themselves fastest: a missed call text back, a new lead alert, and a job done review request. Build those, get them working, then add more.

Do I need to know how to code to build automations?

No. Zapier, Make, and n8n all use visual builders where you connect triggers and actions without writing code. You do need to understand your tools' settings and be careful with the data, but you do not need to program.

What if I do not have time to maintain automations?

Then they will break and you will not know. An automation only helps if someone checks it monthly and fixes it when a tool changes. If you cannot keep up, that is what RiverX is for. We build and run them for you.

Doing this with RiverX
RainmakerCustom
RiverX does
  • Builds the automations around your tools and your process
  • Connects your phone, calendar, CRM, and accounting in one flow
  • Adds failure alerts so a broken automation never drops a lead silently
  • Reviews and fixes them monthly so they keep running
You do
  • Tell us your process
  • Work the leads and jobs the automations bring in
Book a demoSee how it works in RiverXOr call the live demo at (661) 561-6461
Next guideHow to set up a business phone system
Was this helpful?

Related guides