Zapier for Sales Teams: 7 Workflows That Automate Your Entire Sales Process
Your sales reps don't have a selling problem. They have a data-entry problem.
Every morning, someone pulls up HubSpot or Pipedrive and spends 20 minutes logging last week's activity. Leads from the website form are sitting in a spreadsheet nobody checked. A deal moved to βProposal Sentβ three days ago but the follow-up task still hasn't been created. The Monday pipeline report? Still being built manually in Google Sheets. And somewhere in the CRM, a deal that's been stale for 11 days is quietly dying because nobody got an alert.
This is the reality for most sales teams β not because they're disorganized, but because the tools don't talk to each other without someone in the middle connecting them. That's where Zapier for sales teams changes everything. Zapier sits between your CRM, your forms, your email tools, and Slack and handles the connective tissue automatically. No code. No developer. No Monday morning data entry.
This post walks through 7 specific Zapier sales workflows β the ones that eliminate the most manual work for sales ops and RevOps teams. Each one includes the exact trigger, the exact actions, and the tools involved. By the end, you'll have a blueprint you can start building today.
What Is Zapier and Why Do Sales Teams Use It?
Zapier is a no-code automation platform that connects over 7,000 apps. You define a trigger (something that happens in one app) and one or more actions (things that should happen automatically in other apps). The result is a βZapβ β a workflow that runs in the background without anyone touching it.
For sales teams, the most common use cases for sales automation with Zapier are:
- βRouting leads from forms into CRMs without manual input
- βEnriching new contacts with firmographic data
- βAlerting reps in Slack when deals go stale or close
- βTriggering onboarding or re-engagement sequences automatically
These aren't theoretical. They're the exact workflows that save sales ops managers 5β10 hours a week and make pipeline data trustworthy enough to actually plan around.
7 Zapier Sales Workflows for Teams That Want to Stop Doing It Manually
Workflow 1: Auto-Enrich New Leads in the CRM
The problem it solves: Reps get a new contact in HubSpot or Pipedrive β just a name and email. Before they can prioritize the call, someone has to look up the company, the industry, employee count, and LinkedIn profile. This takes 5β10 minutes per lead, every day.
- Trigger:
- New Contact in HubSpot or New Person in Pipedrive
- Actions:
- Clearbit β Enrich Person (using the contact's email address)
- HubSpot / Pipedrive β Update Contact with enriched fields: Company Size, Industry, LinkedIn URL, Company Domain
- Slack β Send Direct Message to assigned SDR with a formatted lead summary
- Tools:
- HubSpot or Pipedrive + Clearbit + Slack
What it eliminates: Manual lead research before outreach. Every new contact lands in your CRM pre-enriched β your reps know the company size, industry, and LinkedIn profile before they dial.
Field-level detail
In the Clearbit Enrich Person step, map {{Contact Email}} as the input. Clearbit returns employees, industry, linkedinHandle, domain, and more. Map these back to your CRM's custom fields in the Update Contact step. In the Slack message, include {{Clearbit: Company Name}}, {{Clearbit: Employees}}, and {{Clearbit: Industry}} so the SDR alert is immediately actionable.
Workflow 2: Route Inbound Demo Requests to the Right Rep
The problem it solves: A prospect fills out your Typeform demo request form. Someone has to check the form dashboard, create a deal in the CRM, figure out which rep owns that territory, and notify them in Slack. All of this happens manually β sometimes hours later.
- Trigger:
- New Submission in Typeform (or Invitee Created in Calendly)
- Actions:
- HubSpot / Pipedrive / Salesforce β Create Deal, associate with contact, set stage to New Demo Request
- Slack β Send message to #demos-booked channel with lead name, company, form answers, and assigned rep
- Slack β Send Direct Message to the rep assigned to that territory (use Zapier Paths to route by company size or geography)
- Tools:
- Typeform or Calendly + HubSpot / Pipedrive / Salesforce + Slack
What it eliminates: Manual deal creation and rep assignment. Every demo request becomes a deal in the CRM and a Slack alert within 30 seconds of form submission β no one checks a form dashboard, no one copies and pastes lead data.
Field-level detail
In the Typeform trigger, map {{Company Name}}, {{Email}}, {{Job Title}}, and {{What are you trying to solve?}} from your form fields. In the HubSpot Create Deal step, set Deal Name to {{Company Name}} β Demo {{Today's Date}}, Pipeline to your main pipeline, and Stage to your top-of-funnel stage. Use Zapier Paths to route the Slack DM: Path A for companies with fewer than 50 employees to SDR 1, Path B for 50β500 to SDR 2, Path C for 500+ to your enterprise AE.
Workflow 3: Stale Deal Alert β Surface Dying Deals Before They're Gone
The problem it solves: Open deals rot quietly. A rep got busy, a prospect went cold, a follow-up was forgotten β and the deal just sits there, inflating your pipeline without any chance of closing. Nobody finds out until the end-of-quarter review.
- Trigger:
- Schedule by Zapier β Every Day at 8:00 AM, Weekdays Only
- Actions:
- HubSpot / Pipedrive β Search Deals where Last Activity Date is more than 7 days ago AND Stage does not contain "Closed"
- Filter by Zapier β Only continue if results count is greater than 0
- Slack β Send message to #pipeline-alerts listing each stale deal (name, owner, stage, last activity date)
- Asana / Notion β Create Task for each deal owner: Follow up needed: {{Deal Name}}
- Tools:
- Schedule by Zapier + HubSpot / Pipedrive + Slack + Asana or Notion
What it eliminates: Silent pipeline decay. Reps get a Slack alert and a task every morning for any deal that hasn't been touched in over a week β before the deal goes cold, not after the quarter closes.
Field-level detail
In the HubSpot Search Deals step, filter by Last Modified Date is before {{7 days ago}}. Use Formatter by Zapier to calculate the date: subtract 7 days from {{zap_meta_human_now}}. In the Asana Create Task step, set the task name to "Stale: {{Deal Name}}", assign to {{Deal Owner}}, and set due date to today. For Notion, create a database item in a "Sales Tasks" database with the same fields.
Workflow 4: Closed-Won Automation β Fire the Confetti, Then Handle the Handoff
The problem it solves: A deal closes. The rep marks it Closed Won in the CRM. Then nothing happens automatically. Someone has to create the invoice, send the welcome email, notify the CS team, and post the win in Slack. Half of these steps get skipped, delayed, or done inconsistently.
- Trigger:
- Deal Stage Changed to "Closed Won" in HubSpot, Pipedrive, or Salesforce
- Actions:
- QuickBooks / Xero β Create Invoice for the deal amount, associated contact, and due date
- Gmail / Outlook β Send welcome email to the new customer from the AE's account
- Slack β Post to #wins channel: {{Deal Name}} β ${{Deal Amount}} β closed by {{AE Name}}
- Notion / Airtable β Create customer onboarding record with status "Not Started"
- Tools:
- HubSpot / Pipedrive / Salesforce + QuickBooks or Xero + Gmail + Slack + Notion or Airtable
What it eliminates: Manual post-close admin. The invoice goes to accounting, the welcome email goes to the customer, the CS handoff record gets created, and the team sees the win in Slack β all within 60 seconds of the deal closing. No one gets missed, no step gets skipped.
Field-level detail
Add a Filter by Zapier step immediately after the trigger: {{Deal Stage}} exactly matches "Closed Won" (copy the exact stage name from your CRM β it's case-sensitive). In QuickBooks Create Invoice, map {{Contact Email}}, {{Deal Amount}} to the line item, and set the due date to 30 days from today using Formatter. For the Slack post, format the message: *{{Deal Name}}* just closed! ${{Deal Amount}} β {{AE Name}} β {{Close Date}}.
Workflow 5: Lead Re-Engagement β Don't Let Lost Deals Stay Lost
The problem it solves: A deal gets marked Lost. The prospect goes cold. Three months later, the timing might be right again β but nobody's following up because the deal fell out of the active pipeline and out of everyone's mind.
- Trigger:
- Deal Stage Changed to "Closed Lost" in HubSpot / Pipedrive (filtered: 90 days ago, via a daily scheduled check)
- Actions:
- Filter by Zapier β Only continue if Close Date was approximately 90 days ago (use Formatter to calculate the date window)
- Mailchimp / ActiveCampaign β Add contact to re-engagement email drip sequence: "Lost Deal β 90 Day Re-engagement"
- Slack β Notify the original deal owner: {{Contact Name}} at {{Company}} was lost 90 days ago β re-engagement sequence triggered
- Tools:
- Schedule by Zapier + HubSpot / Pipedrive + Mailchimp or ActiveCampaign + Slack
What it eliminates: Lost revenue that gets permanently abandoned. Deals lost 90 days ago are some of your warmest re-engagement targets β budget cycles reset, situations change, competing solutions fail to deliver. This Zap makes sure every lost deal gets a second look automatically, without anyone having to track it manually.
Field-level detail
In ActiveCampaign, pre-build an automation called "Lost Deal Re-engagement" with 3 emails: Day 1 (check-in, low pressure), Day 7 (new value prop or case study), Day 14 (last-touch offer). In the Zapier action, use "Add Contact to Automation" and pass {{Contact Email}} and {{First Name}} as personalization fields. In Mailchimp, use "Add/Update Subscriber" and add the contact to your re-engagement audience segment tagged lost-90-day.
Workflow 6: Weekly Pipeline Snapshot to Slack
The problem it solves: Sales managers and VPs of Sales need pipeline visibility without logging into the CRM every morning. Without automation, someone pulls the report manually β if they remember to do it at all.
- Trigger:
- Schedule by Zapier β Every Monday at 8:00 AM
- Actions:
- HubSpot / Pipedrive / Salesforce β Search Open Deals (stage not "Closed", sorted by deal value)
- Formatter by Zapier β Format total pipeline value as currency ($142,500)
- Slack β Post formatted pipeline summary to #sales-pipeline channel
- Tools:
- Schedule by Zapier + HubSpot / Pipedrive / Salesforce + Formatter by Zapier + Slack
What it eliminates: Manual Monday morning pipeline reports. Every Monday at 8am, the sales team sees a clean pipeline snapshot in Slack β open deals, total value, deals in proposal stage β before standup starts. No one has to pull it.
Field-level detail
In HubSpot Search Deals, filter for Stage does not contain "Closed" and sort by Amount descending. The Slack message includes: open deal count, total pipeline value, deals in proposal stage, stale deal count, and the top 3 open deals by value. For Pipedrive teams, use the Pipedrive "Get Deals" action filtered by status open.
Workflow 7: Inbound Lead Deduplication β No More Duplicate Contacts
The problem it solves: A lead fills out your web form. Zapier creates a new contact in HubSpot β but the contact already exists from a conference last year. Now you have two records, duplicate outreach, and a CRM that's slowly becoming unreliable.
- Trigger:
- New Form Submission via Typeform, Webflow Form, or Webhooks by Zapier
- Actions:
- HubSpot / Pipedrive / Salesforce β Search Contacts for existing record matching {{Email}}
- Filter by Zapier β Branch on whether a match was found: if match found, Update existing contact with new form data; if no match, Create new contact + assign to rep
- Slack β Notify sales rep: New lead: {{Name}} at {{Company}} β [existing contact updated / new contact created]
- Tools:
- Typeform / Webflow / Webhooks by Zapier + HubSpot / Pipedrive / Salesforce + Slack
What it eliminates: Duplicate contacts and the CRM hygiene problems they cause. Every inbound submission either creates a fresh contact or updates an existing one β never both, never a duplicate. The rep gets a Slack notification either way, with context on whether this is a new lead or a returning one.
Field-level detail
In HubSpot's "Find Contact" action, search by Email using the {{form_email}} field from your trigger. If the result returns a Contact ID, the Filter routes to the Update step. If the result is empty, it routes to Create. In the Slack message, include a line that says "Existing contact β last active {{Last Activity Date}}" vs. "New contact created" so the rep immediately knows the context.
How to Get Started with Zapier for Sales Teams
You don't need to build all 7 workflows this week. Start with one.
If you're just getting started with Zapier CRM automation: Build Workflow 7 (lead deduplication) first. It's a two-step Zap, it's free-tier compatible, and you'll feel the impact immediately β no more messy duplicate contacts from web forms.
If your reps are drowning in manual research: Build Workflow 1 (lead enrichment with Clearbit) next. It's the single highest-leverage workflow for SDR teams β every new contact arrives pre-researched.
If your pipeline is a black box: Build Workflow 6 (weekly Slack snapshot). Takes 15 minutes to set up, and your Monday standups will never be the same.
Step 1: Create a free Zapier account at zapier.com. The free tier supports 5 active Zaps with 2 steps each β enough to start.
Step 2: Connect your apps. Go to My Apps and authenticate HubSpot (or Pipedrive or Salesforce) and Slack. These are the two tools involved in almost every sales workflow above.
Step 3: Build your first Zap. Click Create Zap, pick your trigger app and event, connect the action, and map the fields. Use the Test Step button after every action β don't skip this. One bad field mapping means data goes in wrong and you won't catch it until it's already happened 50 times.
Step 4: Turn it on and monitor it for a week. Check Zap History for errors. The most common issues are expired API tokens and CRM field name mismatches β both easy to fix.
Once your first workflow is running cleanly, add one per week. By the end of the month, you'll have the foundation of a fully automated Zapier sales workflow stack.
Skip the Setup: Get 7 Pre-Built Workflows for $27
If you'd rather skip the setup and start with 7 pre-built workflows, the Sales Ops Automation Pack has everything above for $27. It includes step-by-step instructions for every Zap, 3 copy-paste email templates (post-demo follow-up, re-engagement, Closed Won handoff), a monthly sales ops checklist, and a quick-start guide to get your first workflow live in under an hour.
Ready to automate?
Sales Ops Automation Pack
7 sales Zap workflows. Pre-built and ready to deploy.
Frequently Asked Questions
Is Zapier good for sales teams?
Yes β Zapier is one of the highest-ROI tools a sales ops or RevOps team can use, especially at the SMB and mid-market level. The reason is that sales workflows are almost entirely event-driven: a lead fills out a form, a deal changes stage, a rep closes a win. These are all perfect Zapier triggers. The challenge isn't whether Zapier is good for sales β it's figuring out which workflows to build first. That's exactly what this post covers.
What CRMs does Zapier work with?
Zapier integrates with every major CRM. HubSpot, Pipedrive, and Salesforce have the deepest Zapier integrations β you can trigger on deal stage changes, new contacts, form submissions, and property updates, and write back to almost any CRM field. Zapier also supports Zoho CRM, Copper, Close, Freshsales, and dozens of others. If your CRM is in the top 50, it has a Zapier integration.
How much does Zapier cost for sales automation?
Zapier's free tier supports 5 active Zaps with 2 steps each β enough for simple lead routing and basic notifications. For multi-step Zaps (like the workflows in this post that involve 3-4 actions), you'll need the Starter plan at $19.99/month, which gives you 20 Zaps and 750 tasks/month. Most sales teams running 5-10 workflows land on the Professional plan at $49/month for unlimited Zaps and 2,000 tasks/month. Zapier's ROI for sales ops is almost always positive in the first week β even the $49/month plan saves more time than it costs.
Do I need coding skills to use Zapier for sales?
No. Zapier is built specifically for non-technical users. You pick your trigger app, your action app, and map the fields using a point-and-click interface. The only thing that looks "technical" is field mapping β connecting {{Contact Email}} in your form to the Email field in HubSpot β and even that is just a dropdown. Sales managers, sales ops leads, and RevOps professionals build Zapier workflows every day without any developer involvement. The workflows in this post are all buildable by anyone who can use a spreadsheet.
What's the difference between Zapier and a native CRM automation?
CRM-native automation (like HubSpot Workflows or Pipedrive Automations) is best for actions that stay within the CRM β updating fields, creating tasks, sending sequences. Zapier is best for cross-app automation β connecting your CRM to Slack, Clearbit, QuickBooks, Asana, Typeform, or any other tool in your stack. In practice, most sales teams use both: HubSpot Workflows for internal CRM logic, and Zapier for anything that needs to cross an app boundary. The workflows in this post are all cross-app by design.
FlowPack HQ sells workflow automation template packs for sales, ops, and growth teams. All packs are digital downloads with step-by-step setup instructions β no coding required.