Automation

CRM automation in HubSpot and Salesforce, what to set up first

Dravik teamUpdated 6 min read

Set up lead assignment first, then tasks tied to deal stages, then data hygiene rules, then renewal and handoff alerts. These four cover most of the manual work in a CRM. In HubSpot you build them with workflows. In Salesforce you build them with Flow. Keep each automation small, named and owned.

Why CRM automation goes wrong

A CRM is only as useful as the data inside it, and reps hate data entry. So companies buy a CRM, add a dozen required fields, and watch adoption fall. Then someone builds fifty workflows to compensate, and nobody can tell which one changed a deal's owner last Tuesday.

The answer is a short list of automations, built in the right order, that remove work from reps and keep data clean. You do not need everything on day one.

HubSpot and Salesforce, side by side

Both platforms can do everything on this list. They differ in how you build it and who usually maintains it.

Area HubSpot Salesforce
Main automation tool Workflows Flow (Record-Triggered, Scheduled and Screen Flows)
Older tools to avoid for new work Rarely an issue Workflow Rules and Process Builder, which Salesforce has retired in favor of Flow
Typical builder Marketing ops or RevOps, often non-technical Salesforce admin, often a dedicated role
Lead routing Workflows with rotation actions Assignment rules, Flow, or routing apps
Strength Fast to build, easy to read Very flexible, handles complex data models
Watch out for Feature availability depends on your plan tier Complexity grows fast without an admin

Check which features your plan includes before you design anything. Both vendors gate some automation features by edition or tier.

Priority 1. Lead and contact assignment

Every new lead needs an owner within minutes. Build this first because it touches revenue directly.

What to set up:

  1. A rule set that assigns owner by territory, segment or round robin.
  2. A fallback owner for anything that does not match.
  3. A notification to the new owner with the lead's source and message.
  4. An alert to a manager if a lead has no activity after a set time.

In HubSpot, a contact-based workflow triggered on lifecycle stage or form submission can rotate owners and send notifications. In Salesforce, lead assignment rules handle simple cases, and a record-triggered Flow handles more complex logic.

Priority 2. Tasks tied to deal stages

When a deal moves stage, the next steps are usually predictable. Automate the reminders so reps do not have to remember.

Examples:

  • Deal moves to "Demo scheduled": create a prep task the day before.
  • Deal moves to "Proposal sent": create a follow-up task three business days later.
  • Deal moves to "Closed won": notify finance and customer success, and create the onboarding record.
  • Deal sits in one stage longer than your normal cycle: alert the owner and manager.

Keep the number of tasks small. If a rep gets ten automatic tasks per deal, they will ignore all of them.

Priority 3. Data hygiene

Bad data compounds. Set up rules that keep records clean without asking reps to do more.

  • Standardize values: state names, country codes, phone formats and job titles into fixed picklists.
  • Fill company fields from enrichment so reps do not have to type them.
  • Flag likely duplicates on creation. Both platforms have duplicate management features.
  • Set required fields only at the stage where they matter. Ask for contract value at proposal, not at first contact.
  • Stamp dates automatically, such as "date became customer," so reporting does not depend on memory.

Priority 4. Renewals and handoffs

For companies with recurring revenue, renewals are where automation pays quietly.

  • Create a renewal deal or opportunity automatically when a contract is signed, dated ahead of the end date.
  • Remind the account owner at intervals before renewal, such as 90, 60 and 30 days.
  • Alert customer success when product usage or support tickets suggest risk, if that data is connected.
  • On handoff from sales to customer success, push the deal notes and key contacts into the onboarding record. Our guide to automating customer onboarding covers the next steps.

Priority 5. Reporting inputs

Dashboards depend on fields being set at the right time. Automate those fields so reports are trustworthy.

  • Lead source captured from the first form or UTM values on creation.
  • Stage entry dates stamped automatically.
  • Close reason required when a deal is marked lost.

With these in place, reports on pipeline velocity and win rate become reliable. See automated reporting for turning them into a weekly dashboard.

How to build without creating a mess

Follow a few rules from the start.

  1. One trigger, one purpose. A workflow should do one job. Avoid giant workflows that handle everything about a contact.
  2. Name things clearly. Include the object, trigger and purpose, such as "Deal, stage to Closed won, notify CS."
  3. Document in the description field. Note who owns it and why it exists.
  4. Test in a sandbox or with test records. Salesforce offers sandboxes on many editions. In HubSpot, use test contacts and check enrollment history.
  5. Watch for loops. Two automations updating the same field can trigger each other repeatedly.
  6. Review quarterly. Turn off anything nobody can explain.

A first-month plan

Week Focus Outcome
1 Audit current automations and fields List of what exists, what is broken, what is missing
2 Lead assignment and alerts Every new lead has an owner fast
3 Deal stage tasks and stuck-deal alerts Reps get timely reminders
4 Hygiene rules and reporting fields Cleaner data and reliable dashboards

Renewals and deeper integrations come in month two, once the basics are stable.

What to add in month two

Once assignment, stage tasks and hygiene rules are stable, connect the CRM to the systems around it. These integrations remove the next layer of copy and paste.

  • Email and calendar sync, so meetings and replies log to the right record without reps doing anything.
  • Billing or accounting, so closed deals create customers and invoices without retyping.
  • Support desk, so account owners see open tickets on the company record before a renewal call.
  • Product usage data, if you sell software, so customer success can spot accounts that stopped logging in.
  • Contract signing tools, so a signed agreement moves the deal to closed won and attaches the document.

Each of these is a separate project with its own owner. Do them one at a time and test each with a handful of real records before switching it on for everyone. When an integration writes to fields that your workflows also watch, check that the two do not trigger each other in a loop.

Signs your CRM automation needs a cleanup

  • Reps complain about tasks they never asked for.
  • Owners change on records with no clear reason.
  • Reports show different numbers depending on who built them.
  • Nobody knows which automations are active.
  • Old Salesforce Workflow Rules or Process Builder processes are still running alongside Flows.

If several of these are true, audit before you build anything new.

Getting help with the setup

A clean CRM setup is mostly about choosing the right few automations and building them carefully. If you want a review of your HubSpot or Salesforce instance with a prioritized build list, book a business audit and we will show you what to fix first.

Frequently asked questions

Should we use HubSpot or Salesforce?

HubSpot is usually faster to set up and easier for non-technical teams. Salesforce suits companies with complex data models, many custom objects, or a dedicated admin. Both handle the automations in this guide well.

How many CRM workflows is too many?

There is no fixed number, but every workflow should have a clear owner and purpose. If nobody can explain what a workflow does, it is a risk. A smaller set of well-named automations is easier to trust and maintain.

Do we still need Zapier or Make if we have a CRM?

Often yes, for connecting tools the CRM does not integrate with natively. Use the CRM's own automation for anything that happens inside the CRM, and an external tool for moving data between the CRM and other systems.

How do we stop reps from ignoring automated tasks?

Create fewer tasks, make them specific, and tie them to moments that matter, like a proposal follow-up. Review with reps which tasks help and remove the rest.

What should we automate in Salesforce now that Process Builder is retired?

Build new automation in Flow, and plan to migrate any remaining Workflow Rules and Process Builder processes. Salesforce provides a migration tool for converting many of them to Flow.

Book a business audit

Find the leak. Then we hunt it down.

We look at your busywork, your Google rankings and how AI assistants describe your category, then hand you a prioritized plan.

  • $199 fixed price
  • 30 minute call
  • A written plan you keep
  • Full refund if not worth it
Book a business audit
Automation

9 signs your team needs automation

Nine practical warning signs that manual work is slowing your team, from copy and paste between tools to late reports, plus what to automate for each one.

6 min read

Automation

AI for customer support in a small business

How a small business can use AI in customer support safely. What to automate, what to keep human, how to set up a knowledge base and how to measure quality.

6 min read

Business audit, $19930 minute call plus a written plan

Find your leak