CRM Workflow Automation: What to Build First

CRM workflow automation is a set of rules inside your CRM that do something when a record changes: a new lead comes in, so it gets assigned and texted; a deal moves to Proposal, so a follow-up task appears; nobody has touched a deal in 14 days, so the owner gets a nudge. Every rule has the same three parts: a trigger, optional conditions, and one or more actions. Most small sales teams need six of these, not sixty, and every major CRM includes a builder for them, though usually not on the cheapest plan.

This post covers the six workflows I would build first, what HubSpot, Salesforce, Pipedrive, GoHighLevel and Zoho include on each plan (checked on their pricing pages in October 2026), when it makes sense to move a workflow out of the CRM into a tool like n8n or Make, and the mistakes that make automations quietly fail.

How a CRM workflow is put together

The trigger is the event that starts it: a record is created, a field changes, a date arrives, or a set amount of time passes. Conditions narrow it down, so the rule only fires for leads from a certain source, deals over a certain size, or contacts in a certain state. Actions are what happens: assign an owner, send an email or text, create a task, update a field, notify someone in Slack, or call a webhook to hand the record to another system.

A plain example, written the way you would sketch it before building it:

• Trigger: a lead is created from the website form
• Condition: the lead has a phone number and has opted in to texts
• Actions: assign to the next rep in rotation, send a text confirming we got the request, create a "call within 5 minutes" task, post the lead to the sales channel

If you cannot write a workflow out in four lines like that, it is not ready to build.

The six CRM workflows to build first

These are in the order I would build them. Each one depends on the one before it working.

1. Lead routing

Every new lead gets an owner immediately, by territory, by source, or by round robin. The part people skip is the fallback: if no rule matches, the lead should go to a named person, never to nobody. An unassigned lead in a shared queue is a lead nobody calls.

2. Speed-to-lead follow-up

The moment a lead is assigned, the CRM sends a first touch and puts a call task at the top of the rep's list, with an alert if that task is still open after a few minutes. The first touch is usually an email, a text, or both. The faster a real person gets on the phone, the better, and this is the workflow that makes "fast" happen on a Saturday afternoon. Our post on automating lead follow-up goes deeper on the sequence after the first touch.

Texting and calling have rules that a CRM will not enforce for you. Marketing texts need the person's prior express written consent. Registering for A2P 10DLC, which carriers have required for business texting from local numbers since February 1, 2025, is a carrier requirement and is not consent. If an automation places calls with an AI or prerecorded voice, the FCC's February 2024 ruling (FCC 24-17) treats that voice as "artificial" under the TCPA, so those calls need prior express consent as well, and ringless voicemail counts as a call. Any AI agent in the flow should say it is an AI. We cover the texting side in AI SMS compliance and the calling side in AI vs human cold callers. This is not legal advice.

The practical rule for the workflow: store consent as its own field, default it to "no", and make the text action conditional on it.

3. Deal stage tasks

When a deal enters a stage, the CRM creates the tasks that stage requires: book the walkthrough, send the proposal, collect the signed agreement. Pair this with required fields per stage, so a deal cannot move to Proposal without an amount and a close date. This is what makes your pipeline report mean something.

4. Reminders and stale deal alerts

If a deal has had no activity for a set number of days, the owner gets a task or a message. If a proposal has been out for a week with no reply, a follow-up task appears. Pick the number of days from your actual sales cycle. A rule that fires too often gets ignored within a month.

5. Data hygiene

Check for an existing contact with the same email or phone before creating a new one, and merge or flag it. Normalize phone numbers to one format so the dedupe check works. Capture the lead source on every record at creation, from the form or the UTM parameters, because you cannot add it later. Bad data is the main reason automations misfire, so this one protects the other five.

6. Reporting

A weekly summary sent to the owner or manager: new leads by source, time to first contact, deals that moved, deals that stalled. The CRM's dashboards can show this, but a report that arrives in the inbox on Monday morning gets read. It also shows you when one of the other workflows has stopped firing.

What CRM workflow automation costs on each platform

All five of these CRMs include a workflow builder. What differs is which plan unlocks it and how much it can do. Prices below are per user or seat per month as listed on each vendor's pricing page in October 2026, and they change often, so check before you buy.

A few notes from the vendor pages that change the math:

HubSpot's Professional and Enterprise tiers carry one-time onboarding fees ($1,500 and $3,500), and Enterprise at $150 per seat raises the cap to 1,000 workflows and adds workflow health monitoring. The Starter tier is fine for routing and simple follow-ups; the restricted triggers are what push most teams to Professional.

Salesforce gives you the most power and the most setup. Core, at $195 per user billed annually, is the first edition its comparison table shows without the 5-flow note, and building anything nontrivial in Flow Builder usually needs an admin.

Pipedrive is the simplest of the five for a sales team that lives in a pipeline. Automations start at Growth, and Ultimate ($79 per seat billed annually) adds a sandbox account for testing workflows away from live data.

GoHighLevel prices the account, not the seat, so it gets cheaper per person as the team grows. Budget for usage: the plan price does not include the texts, emails and calls your workflows send.

Zoho is the cheapest way to get real workflow rules, and the free plan includes them. The limits per module are what you outgrow, along with Blueprints (guided stage-by-stage processes), which start at Professional.

When to use n8n or Make instead of the CRM's builder

Keep a workflow inside the CRM when it only touches the CRM: assign, create a task, update a field, send an email the CRM sends anyway. Native workflows are easier for the next person to find and fix.

Move it to an external tool when it crosses systems, needs logic the CRM builder cannot express, or when you do not want the only copy of a lead to live in one vendor's database. Our own website is an example. When someone submits a form, the lead is written to our own Postgres database first, and only then does it fire a webhook to n8n, which handles the notifications and the CRM sync. If n8n is down, the lead is already saved, and each lead records whether the webhook delivery succeeded, so failed ones can be resent. SMS and call consent are stored in their own columns that default to false, so a missing opt-in reads as a refusal. No CRM builder would have given us that order of operations.

Two common choices:

n8n bills per workflow execution, not per step, which makes long workflows cheap. The self-hosted Community Edition is free. The hosted Starter plan is listed at €20 a month billed annually for 2,500 executions, and Pro at €50 for 10,000.

Make bills in credits, where most module actions use one credit. The free plan has 1,000 credits a month; Core is listed at $12 a month on annual billing. A workflow with many steps uses credits faster than you expect, so estimate before you commit.

If you are choosing between them, our Make vs n8n comparison and the n8n beginner tutorial go through the tradeoffs.

Common CRM automation mistakes

Automating a process nobody has written down

If two reps handle a new lead two different ways, automation will lock in one of them by accident. Agree on the process first, then build it.

Two systems doing the same job

A CRM workflow sends the welcome text, and a Zapier or Make scenario someone built last year sends it too. The lead gets two texts and starts to wonder who you are. Keep a list of every automation and what it sends.

Building on duplicate records

If the same person exists three times, they get three sequences. Build the hygiene workflow before the follow-up ones.

Launching without a test record

Run a test record through every branch before turning a workflow on for real leads. HubSpot Enterprise, Salesforce Core and above, Pipedrive Ultimate and Zoho Enterprise include sandbox accounts for this. On lower plans, use a test contact with your own email and phone.

Silent failures

A workflow that stops firing does not send an error to anyone by default. Set an alert for failed runs (n8n has error workflows for exactly this), and watch the Monday report for numbers that drop to zero.

Texting without consent on record

The CRM will happily send a marketing text to a number with no opt-in. The consent check has to be a condition in the workflow, not a habit.

If you would rather have this built and maintained for you, that is what our AI workflow automation service does.