The CRM Automation Playbook: 15 Workflows Every Sales Team Needs

Sales teams lose hours every week between systems: retyping form leads, chasing missing fields, posting updates by hand and handing deals to onboarding over email. These 15 workflows remove that work. Each one comes with a template: the trigger, the steps and the result, using standard n8n nodes, so you can build it yourself or hand it to us.

The examples use HubSpot and Salesforce. The same patterns work with Pipedrive, Zoho or any CRM with an API.

Three rules before you build

• One workflow per outcome. "New lead to CRM" and "route lead to owner" are separate workflows. They are easier to test, fix and hand over.
• Search before you create. Match on email, then company domain, before creating a contact or company. Duplicates are the most common CRM automation bug.
• Share one error workflow. Point every workflow at the same error workflow, which posts the failed run and its link to a Slack channel someone watches.

Lead capture and routing

1. Web form to CRM, without duplicates

Every form submission becomes one clean CRM record with its source attached.

Template: Webhook or form trigger → Set node to clean names, emails and phone numbers → search the CRM by email → IF found, update the contact; otherwise create it → save UTM source, campaign and landing page → associate the company by domain.

2. Lead enrichment

Reps see company size, industry and location before the first call.

Template: CRM trigger on "contact created" → HTTP Request to your enrichment provider → map the fields you actually use → update the contact and company → tag records the provider could not match, so nobody waits on them.

3. Lead scoring

Reps work the best leads first, with a score the whole team understands.

Template: CRM trigger on create or update → Code node that scores fit (title, company size, industry) and intent (form type, pages viewed, replies) using rules agreed with sales → write the score and a one-line reason to CRM properties → optional AI node that summarizes why the lead looks promising.

4. Territory and round-robin routing

Every qualified lead gets the right owner within seconds.

Template: Trigger when a lead becomes qualified → Switch node by region, segment or account size → pick the next rep in that team with a counter stored in Postgres or Google Sheets → set the owner in the CRM → hand off to workflow 5.

5. Speed-to-lead alert

The owner hears about a new lead immediately, and a manager hears if nobody acts.

Template: Owner assigned → Slack message to the rep with name, company, source, score and a link to the record → Wait node for your response window → check the CRM for a logged call or email → IF nothing, post to the sales manager's channel.

6. Meeting booked to CRM

Booked meetings land in the CRM with the deal created and a prep brief ready.

Template: Calendly or Cal.com webhook → find or create the contact and company → create the meeting activity and a deal at the right stage → AI node writes a short brief from the form answers and the company's website → send the brief to the owner.

7. Follow-up tasks after meetings

No meeting ends without a next step on the record.

Template: Schedule trigger each morning → search for meetings held yesterday with no follow-up activity → create a follow-up task for each owner → send one Slack digest per rep.

Pipeline hygiene

8. Stale deal alerts

Deals that stop moving get attention before the forecast meeting.

Template: Schedule trigger → search open deals with no activity for longer than you allow at each stage → group by owner → send each rep a digest with links → copy managers on the oldest ones.

9. Missing data checks

Forecasts stay trustworthy because required fields are filled in.

Template: Schedule trigger → search deals with a close date in the past, no amount or no next step → create a task on each deal for its owner → send the sales manager a weekly summary by rep.

10. Stage-based actions

Moving a deal to a new stage starts the work that stage needs.

Template: CRM trigger on "deal stage changed" → Switch on the new stage → for "Proposal", create a quote from a Google Docs template and attach it → for "Contract", notify whoever reviews contracts → for "Closed lost", ask the owner for a loss reason and add the contact to a nurture list.

11. Call and meeting notes to the CRM

Notes and next steps reach the CRM without anyone typing them.

Template: Webhook from your recording or transcription tool when a transcript is ready → AI node summarizes it into the fields you track, such as pain points, timeline, decision makers and next step → Slack message to the rep with approve and edit buttons → write the approved notes and properties to the deal.

12. Product usage and churn signals

Account owners see who is growing and who is going quiet.

Template: Schedule trigger → query product usage per account from your database or warehouse → update company properties in the CRM → IF usage drops sharply or an account hits an upgrade signal you define, alert the owner with context.

Handoffs and reporting

13. Closed-won handoff to onboarding

The customer gets a smooth start, and nobody re-asks what sales already knows.

Template: Deal moves to "Closed won" → create a project from a template in Asana, Jira or ClickUp with the deal details → post a handoff summary in the onboarding channel → send the welcome email → create the customer in your help desk.

14. Closed-won to invoicing

Finance has a draft invoice without retyping the deal.

Template: Deal moves to "Closed won" → find or create the customer in QuickBooks, Xero or Stripe → create a draft invoice from the deal's line items → notify finance to review → when payment arrives, update the deal and company in the CRM.

15. Weekly pipeline report

Everyone starts Monday with the same numbers.

Template: Schedule trigger on Monday morning → pull deals by stage and owner, plus deals created and closed last week → Code node totals the numbers → post a summary to Slack and email it to leadership → optional AI node adds a few lines on what changed.

How to roll them out

1. Week one: workflows 1, 4 and 5. They touch every new lead and give you clean data to build on.
2. Next: enrichment, scoring and meeting workflows (2, 3, 6 and 7), once routing is stable.
3. Then: hygiene checks and stage actions (8 to 12), agreed with sales leadership so alerts match how the team is managed.
4. Last: handoffs and reporting (13 to 15), with onboarding and finance in the room.

Build each one against a CRM sandbox first, agree on field definitions with the sales team, and watch the error channel closely for the first two weeks.

Get them built

Our CRM automation team builds these workflows in n8n, connects them to your CRM and keeps them running, and lead automation covers capture, enrichment and routing in more depth. See how we connect HubSpot, Salesforce and Slack.