HubSpot Zapier integration is the fastest way to connect HubSpot to the 7,000+ apps that don’t have a native integration in the App Marketplace. Done right, it replaces hours of manual data entry, syncs records between systems your team actually uses, and routes leads the moment they come in. Done wrong, it duplicates contacts, breaks reporting, and quietly burns through your Zapier task quota.
This is the setup guide I give every client who asks me whether they need Zapier. You’ll get the exact configuration steps, the triggers and actions that matter, five B2B use cases that pay for the subscription on day one, and the moments where Zapier is the wrong tool — even when it looks like the right one.
How the HubSpot Zapier integration actually works
Zapier is a middleware layer. It listens for events in one app (a “trigger”), then performs an action in another app. The HubSpot side is event-driven: a new contact, a new deal, a contact update, a form submission, or a lifecycle stage change can all kick off a Zap.
You can move data both directions. HubSpot can be the trigger (push data out) or the destination (pull data in). The integration is built and maintained by Zapier — it sits in the HubSpot App Marketplace and uses the HubSpot v3 API under the hood, which means it respects your standard property permissions and API rate limits.
Two things worth knowing before you build anything:
- You need Super Admin permissions in HubSpot to install or reauthorize the connection. Mason gets this question weekly — if you’re not a Super Admin, the connection screen will silently fail and nobody tells you why.
- Zapier tasks are billable. Every action your Zap takes counts as a task. A 1,000-task plan goes faster than people expect once you start syncing form submissions and deal updates.
How to set up the HubSpot Zapier integration
Set this up once and the rest of your Zaps share the connection.
- Create a Zapier account first. Use the same business email you use as a Super Admin in HubSpot. Free plans cover 100 tasks per month; most B2B teams need at least the Professional tier.
- In HubSpot, click the settings gear in the top nav, then go to Integrations > Connected Apps. Search for Zapier and click Connect app. HubSpot redirects you to Zapier’s authorization screen.
- Authorize the connection. Pick the HubSpot account you want to connect — if you manage multiple portals (agency setup, sandbox, production), be deliberate. The wrong portal is the most common setup mistake I clean up.
- Confirm the integration is live by going back to Integrations > Connected Apps. You’ll see Zapier listed with a status indicator. If it shows “Action required,” reauthorize before building any Zaps.
- Test the connection in Zapier by creating a new Zap with HubSpot as the trigger. Pick “New Contact” and run a test — Zapier should pull a real contact record. If it doesn’t, your auth scope is wrong; disconnect and redo step 3.
For the official walkthrough with screenshots, HubSpot maintains the Zapier integration setup guide. The steps above are the version I run for clients — same logic, fewer clicks.
The triggers and actions worth using
Zapier exposes dozens of HubSpot triggers and actions. Most of them you’ll never use. Here are the ones that show up in real B2B workflows.
Triggers (HubSpot pushes data out)
- New Contact — fires when a new contact is created. Use it for instant Slack alerts, lead routing, or syncing to a billing system.
- Contact Recently Created or Updated — fires on any change to a contact property. Powerful but noisy; filter on specific properties or you’ll burn tasks.
- New or Updated Deal — fires when a deal is created or modified. Best paired with a stage filter so you only trigger on meaningful changes (e.g., deal moves to Closed Won).
- New Form Submission — fires when a contact submits a HubSpot form. Useful when the form needs to trigger something HubSpot Workflows can’t reach.
- New Company — fires when a new company record is created. Pairs well with enrichment tools like Clearbit or Apollo.
Actions (HubSpot pulls data in)
- Create or Update Contact — the workhorse. Idempotent on email, so you don’t double up.
- Add Contact to Workflow — drops the contact into a HubSpot Workflow as if they enrolled normally. Useful for triggering nurture sequences from external events.
- Create Deal — generates a new deal and lets you map external data into deal properties.
- Add Contact to Static List — adds the contact to a static list. Static, not active — you can’t recreate active list logic in Zapier.
- Create Company — generates a new company record. Combine with the contact action to build full account records from a single trigger.
5 B2B use cases that pay back the Zapier subscription
These are the Zaps I build first for new clients. Every one of them earns back the cost of a Zapier Professional plan inside the first month.
- Slack alerts when a Closed Won deal hits the pipeline. Trigger on deal stage = Closed Won; action posts to your #wins Slack channel with deal name, amount, and owner. Zero-cost morale boost, plus your finance team sees revenue events in real time.
- Sync Calendly bookings to a HubSpot deal. Trigger on new Calendly event; action creates or updates the contact, then creates a deal in your “Discovery Booked” stage. Now your sales pipeline reflects calendar reality without reps logging anything manually.
- Push closed deals to QuickBooks or Xero for invoicing. Trigger on deal Closed Won; action creates a draft invoice. Saves about 10 minutes per deal and eliminates the “did finance know?” follow-ups.
- Add new contacts to LinkedIn ad audiences. Trigger on new contact with a specific lifecycle stage; action adds them to a LinkedIn Matched Audience. Closes the loop between your CRM and your ad targeting without exporting CSVs every week.
- Create an Asana or ClickUp task when a contact requests onboarding. Trigger on form submission; action creates a task in your project tool with the contact’s details and a deep link back to the HubSpot record. Your delivery team gets a real ticket, not a Slack ping that gets lost.
For more pre-built starting points, Zapier maintains a directory of HubSpot Zap templates covering 7,000+ destination apps.
When NOT to use Zapier (use HubSpot Workflows or a real integration instead)
Zapier is the right answer only when there’s no native integration and the use case is event-driven. Here’s where I tell clients to stop building Zaps and pick a different tool:
- The destination app has a native HubSpot integration. Salesforce, Mailchimp, Stripe, Slack, Google Ads — all native. Native integrations sync more fields, handle errors better, and don’t burn tasks.
- You need bidirectional, real-time sync of large data sets. Zapier is one event = one task. For continuous sync between systems (CRM to data warehouse, CRM to ERP), use a proper iPaaS like Workato, Make, or a custom-built integration on the HubSpot API.
- The logic should live inside HubSpot. If you’re using Zapier to trigger an internal HubSpot action — enrolling a contact in a workflow, updating a property, creating a task — there’s a 90% chance HubSpot Workflows can do it without leaving the platform. Workflows are unlimited; Zapier tasks are not.
- The Zap chains through three or more apps. Multi-step Zaps fail silently and are a nightmare to debug. If your automation needs that much logic, build it as a real integration.
If you’re already running into HubSpot configuration limits — workflow caps, custom property limits, reporting headaches — that’s a different problem. Our HubSpot optimization service covers the cleanup work before you start layering Zapier on top of a broken setup.
Frequently Asked Questions
Is the HubSpot Zapier integration free?
The integration itself is free to install in both HubSpot and Zapier. You only pay for Zapier itself. Free Zapier accounts include 100 tasks per month, which is enough to test but not enough to run a real B2B operation. Most teams I work with land on Zapier Professional ($19.99/month for 750 tasks at the time of writing) or Team plans once they have more than two production Zaps. HubSpot does not charge anything for the connection — every Hub tier supports the Zapier integration, including Free CRM.
What HubSpot subscription do I need to use Zapier?
Any HubSpot subscription works, including the free CRM. The Zapier integration uses the HubSpot v3 API, which is available across all tiers. The only caveat is feature-level: actions like “Add Contact to Workflow” require a Marketing Hub or Sales Hub subscription that includes Workflows. If you’re on Free CRM, you can still use Zapier to create and update contacts, deals, and companies — you just can’t enroll them in workflows because workflows don’t exist on free.
How long does it take to set up a HubSpot Zap?
A simple one-trigger, one-action Zap takes 10–15 minutes including testing. Multi-step Zaps with filters, formatting, or conditional logic take 30–60 minutes. The slowest part is usually mapping fields between systems with different data structures — for example, a Calendly event timezone doesn’t match HubSpot’s contact timezone field by default. Budget more time on the first Zap of any new app pairing because you’re learning both ends; subsequent Zaps to the same app are much faster.
Can Zapier replace a HubSpot Salesforce integration?
No, and you shouldn’t try. The native HubSpot Salesforce integration syncs hundreds of fields bidirectionally, handles ownership rules, manages duplicates, and runs continuously. Zapier is event-based, syncs one record at a time, and doesn’t handle conflict resolution between systems. For Salesforce specifically, use the native integration. Zapier is the right tool for connecting HubSpot to apps that don’t have a native option — Calendly, Typeform, niche industry tools, internal apps with a Zapier connector.
Why does my Zap keep failing?
The two most common causes are authentication expiration and field mapping errors. Authentication expires when the HubSpot user who installed Zapier loses Super Admin status, leaves the company, or revokes the OAuth token. Field mapping errors happen when a HubSpot property is required but the trigger app doesn’t send a value for it — Zapier returns an error and pauses the Zap. Check the Zap History tab in Zapier; the error log usually pinpoints the exact field that broke. Fix the field, replay the Zap, and turn it back on.
Build the integration before you build the Zap
Zapier is excellent at what it does, but it’s a finishing tool — not a foundation. If your HubSpot CRM isn’t configured properly, every Zap you build inherits the same data quality problems, just faster. Custom properties get duplicated. Lifecycle stages get out of sync. Lead routing fails on records that shouldn’t have been created in the first place.
Want to get more out of HubSpot? Book a call with Your HubSpot Expert and let’s talk about what’s slowing your team down — including the integration stack you’re trying to wire together with Zapier.