The widest surface on this site, metered by the minute your plan polls at.
A Super Admin in HubSpot and a Zapier plan sized to your task volume. No HubSpot upgrade.
Contacts, Companies, Deals, Custom objects, two-way sync.
This is the widest integration surface in the directory: 27 triggers and 66 actions against contacts, companies, deals, tickets, line items and custom objects, on a HubSpot free plan if that is what you hold. What you are buying is not access, it is latency and throughput. Polling runs every 15 minutes on Zapier's free plan and every minute on Team, tasks are counted on successful actions rather than on polls, and the one HubSpot limit that will actually find you is the shared daily cap of 625,000 requests on Professional. Zapier's own help page quotes a different daily figure, so size against HubSpot's published numbers rather than Zapier's.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| Contacts, companies and deals | Both ways | Create, update, find and find-or-create on each, in either direction. The core of what most teams build here. |
| Custom objects | Both ways | Create, update, find and delete, which is more than several native connectors in this directory manage. |
| Tickets and line items | Both ways | Full create, update and search. Useful where the CRM is doing service work as well as sales. |
| List membership | Both ways | Static lists only; active lists do not appear in the dropdown, and the contact has to exist first. Needs Marketing Hub Starter or above. |
| Property change events | One way, out | Triggers on a named property changing, which is how most useful Zaps start. |
| Anything in under a minute | Event only | Not on a poll. The fastest documented interval is one minute, on Team and Enterprise. |
Four of those six rows move in both directions. The one that does not is Property change events, and those are the rows that decide how you design around this rather than the ones in the brochure.
Zapier exposes most of the CRM, so the useful table is not what is available but where the edges are: the two data types that behave oddly and the one list type that is missing.
| In HubSpot | In Zapier | What to know about the match |
|---|---|---|
| Contacts, companies, deals, tickets, line items | Create, update, find or find-or-create | In either direction, with custom objects included, which is more than several native connectors manage. |
| A date or date-time value | A HubSpot date property | Sent as a UNIX timestamp and rounded down to UTC midnight. Time of day does not survive the trip. |
| Add Contact to List | A static list only | Active lists are membership rules rather than containers, so they do not appear in the dropdown and cannot be written to. |
| A named property changing | An instant trigger | Deal Property Change fires on the event. Most other triggers poll, so the choice of trigger is the choice of latency. |
| A contact created by a Zap | A record sourced to Zapier | Original source attribution follows the thing that created the record, which is now the automation rather than the campaign. |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: five field mappings and three documented exclusions, each one's note, and the four vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
The date rounding is the one to design around rather than work around: if your process needs the hour, store it in a separate text or number property that Zapier can write without HubSpot reinterpreting it.
Both vendors gate something here and they gate different things, which is why this pair gets scoped wrong. Zapier decides how fast you may poll; HubSpot decides which triggers exist at all and how many requests a day you get. Pick one on each side and the grid marks the answer.
Pick one on each side.
| Zapier plan | Free or Starter | Professional | Enterprise |
|---|---|---|---|
| Free | Core objects, default polling | Plus the paid-plan triggers | Plus the paid-plan triggers |
| Professional | Plus polling control | Both | Both |
| Team or Enterprise | Plus polling control | Both | Both |
Counted off that grid, of nine pairings: one gives you core objects, default polling, two give you plus the paid-plan triggers, two give you plus polling control, four give you both. Notice that the burst limit is the same on both HubSpot tiers. Upgrading HubSpot raises the daily ceiling and not the rate, so a Zap that fires in bursts is constrained by a number an upgrade will not move.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
HubSpot: Users and Teams
Zapier documents Super Admin as the requirement, and separately that only one app connection to a HubSpot account can exist at a time. Connecting a second invalidates the first, so a colleague quietly reconnecting is enough to break every Zap you own.
Zapier: Apps, Add connection
Search for HubSpot, click Add connection, log in in the new tab and grant access. There is no install on the HubSpot side, which is also why nothing in HubSpot tells you it exists.
The Zap editor: trigger step
HubSpot offers both. Deal Property Change is instant; New Company and most of the recently-created triggers poll. Instant means the event arrives when it happens rather than on a schedule, and choosing it costs nothing.
Zap editor: Advanced settings
Polling interval control is unavailable on Zapier Free and available on Professional, Team and Enterprise. The intervals on offer depend on both your plan and the trigger app, and the setting is hidden entirely for instant triggers because they do not poll.
The Zap editor: action step
HubSpot wants dates as UNIX timestamps, and Zapier documents that date and time values sent to HubSpot are rounded down to UTC midnight. If a time of day matters to your process, it is gone by the time the record is written.
Before the first Zap goes live
A contact created by a Zap arrives with Zapier as its source rather than the form or campaign that produced it. Practitioners report losing original-source reporting exactly this way, and the fix is to decide now whether the native form or the Forms API should be creating the record instead.
The two steps worth slowing down on are the first and the last: one protects the connection somebody else can break, and the other protects the attribution nobody notices losing until the quarterly report.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/hubspot-zapier/SKILL.md https://www.reversecontact.com/integrations-hub/skills/hubspot-zapier.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhySomebody added a second Zapier connection to the same HubSpot account, which invalidates the previous one.
Reconnect, then agree who owns the connection. There is no way to run two, so this is a people problem with a technical symptom.
WhyHubSpot takes dates as UNIX timestamps and Zapier rounds date-time values down to UTC midnight.
Store the precise value in a separate property if you need it. Nothing in the mapping screen prevents the rounding.
WhyIt is an active list. Only static lists appear.
Write a property instead and let an active list pick the contact up by rule, which is what active lists are for.
WhyA polling trigger on an account without polling control, or an app-imposed minimum interval.
Switch to an instant trigger if one covers your event. Deal Property Change is instant; most of the created-or-updated triggers are not.
WhyA record created by an automation is attributed to that automation.
Create the contact through the native form or the Forms API where attribution matters, and use the Zap for everything after creation.
WhyHubSpot allows 190 requests per 10 seconds regardless of tier, so a Zap that fans out hits the rate limit before the daily cap.
Add a delay step or batch the work. A HubSpot upgrade raises the daily ceiling and leaves the burst limit where it was.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for this pair by name, in the words a person would use. 14 threads from 2024 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
I was wondering if there is a way to build certain workflows outside of HubSpot's native automation, without requiring the higher HubSpot licenses.
r/hubspot·January 2026·4 points
A fair strategy and the one this pair is genuinely good at, because Zapier reaches custom objects, tickets and line items without any HubSpot tier change. The grid above is where it stops working: the triggers Zapier marks as paid-HubSpot-only are not reachable this way.
I have done this with a client who needed more advanced logic around status management on a custom object and syncing data with another platform. We initially handled most of the logic externally using Zapier since it has solid HubSpot triggers and actions
r/hubspot·January 2026·3 points
Worth noting the word initially. Logic that starts outside the CRM tends to stay there, which is fine as long as somebody writes down that it exists, because nothing inside HubSpot will tell the next admin.
We have a non-HubSpot form on our website for sign-ups. Zapier transfers data from our database to HubSpot. But we lose out the original sources of acquisition
r/hubspot·May 2024·4 points
The clearest statement of the problem in the set, and the reason the last setup step above exists. The record gets created by the automation, so the automation becomes the source, and the campaign that actually produced the lead disappears from the drill-down.
add the tracking code to the page you have the form on or add an iframe with the form on one of your landing pages, do not use zapier use the forms api to send the form data to hubspot
r/hubspot·May 2024·3 points
Transcribed with the contraction expanded. The advice is right and narrower than it sounds: use the native path for record creation where attribution matters, and keep Zapier for everything that happens to a record afterwards.
I am a heavy user of Zapier, since their AI automation has been better than HubSpot's
r/hubspot·September 2024·5 points
One person's comparison and a dated one, so treat it as a preference rather than a finding. What it does illustrate is the pattern across these threads: Zapier is used here as a capability upgrade rather than as a bridge to another tool.
Two uses dominate and they pull against each other. One is deliberate: people using Zapier to buy automation they would otherwise have to upgrade HubSpot for, which works and is the main reason this pair exists. The other is accidental: Zapier quietly becoming the thing that creates contacts, which is where attribution goes to die. Nobody in these threads complains that the integration is unreliable.
The split those threads suggest is the useful rule for this pair: let HubSpot create the record, and let Zapier do everything that happens to it next.
The honest way to read this pair is that Zapier sells latency and breadth, and HubSpot gives away the access. Nothing on HubSpot's side needs upgrading: the app is available on all products and plans and a Super Admin can connect it on the free CRM. What a Zapier plan buys is how often your Zaps look, how many successful actions you may run, and a route to thousands of applications that will never build a HubSpot app of their own. Price it against the number of records you expect to move in a month, which is almost always a much smaller number than the size of your database.
Where this stops being the right answer is speed and volume, and both have clean thresholds. Speed first: the fastest documented poll is one minute, so anything that has to happen while a form submission is still warm belongs on a webhook rather than a poll. HubSpot can send one, but the webhook action in workflows is a Data Hub Professional feature, which is the same licence wall that shapes the Reverse Contact guide and is usually more expensive than a middle layer. Volume second: per-task pricing is excellent at hundreds of runs a month and poor at hundreds of thousands, and the crossover is where teams move to n8n or a Clay table instead.
The limit that actually breaks things is the quietest one. Zapier permits a single HubSpot connection per account, and reconnecting replaces it, so in any team where two people have wired up their own automations the second reconnection takes down the first person's Zaps with no announcement. Decide early that one service account owns the connection, document which one, and keep personal logins out of it. It is the same discipline a Salesforce admin applies to an integration user, and it is just as load-bearing here even though nothing in the interface suggests it.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under HubSpot, Zapier and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
Not on the HubSpot side. HubSpot lists the Zapier app as available on all products and plans, including the free CRM, and asks only that the person connecting it is a Super Admin or holds App Marketplace permissions. Zapier's free plan includes 100 tasks a month, so the real question is how many records a month you expect to move, not which HubSpot you own. A handful of triggers and actions do need a paid HubSpot subscription, and the list is specific rather than general.
That is your Zapier plan, not your HubSpot plan. Polling runs every 15 minutes on Zapier's free plan, every 2 minutes on Professional, and every minute on Team and Enterprise. Polls themselves consume no tasks; only successful actions do. If you need a HubSpot change to reach another system in seconds rather than minutes, the right tool is a webhook rather than a poll, and that is a different route with a different gate.
Zapier documents a short list rather than a tier split. The New COS Blog Article, New Calendar Task and New Email Event triggers and the Create Calendar Task action require a paid HubSpot subscription. Separately, the list triggers and actions need Marketing Hub Starter or above, and Create Enterprise Event is Marketing Hub Enterprise only. Everything else in a very large catalogue runs on the free CRM.
Because Zapier sends dates to HubSpot as UNIX timestamps and rounds date and time values down to UTC midnight. A date entered in a timezone behind UTC therefore lands on the previous day in HubSpot. It is documented rather than a fault, it is the single most common support thread on this pair, and the fix is to normalise the date in a formatter step before the HubSpot action rather than to argue with the field.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.