---
name: hubspot-zapier-integration
description: Connect HubSpot and Zapier: what syncs, which editions carry it, the setup order, and the failures to expect. Covers contacts, companies, deals, custom objects. Use when the user wants to set up, audit or troubleshoot HubSpot and Zapier together, or asks why data is not moving between them.
---

# HubSpot and Zapier

> Generated from https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-zapier-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** A Super Admin in HubSpot and a Zapier plan sized to your task volume. No HubSpot upgrade.

**What moves:** contacts, companies, deals, custom objects, both ways.
**How it is built:** zapier, make or n8n, marketplace app. **Effort:** minutes.

## The short version

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.

## Which plans carry what, on both sides

Rows: Zapier plan. Columns: HubSpot plan. 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.

| 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 |

- **Core objects, default polling.** Contacts, companies, deals, tickets, line items and custom objects, on whatever polling interval Zapier gives a free account. Enough for most small automations.
- **Plus the paid-plan triggers.** Adds the triggers and actions Zapier documents as paid-HubSpot-only, including New COS Blog Article, New Calendar Task, New Email Event and Create Calendar Task.
- **Plus polling control.** Adds control of the polling interval, which Zapier gates off its Free plan. The intervals offered still depend on the trigger app.
- **Both.** Everything above, plus the higher API ceiling: HubSpot documents 650,000 requests a day on Professional and 1 million on Enterprise, both at 190 requests per 10 seconds.

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.

## What actually syncs

Direction is written from HubSpot's point of view: out means out of HubSpot, in means into it.

| What | Direction | What that means in practice |
|---|---|---|
| Contacts, companies and deals | Two-way sync | Create, update, find and find-or-create on each, in either direction. The core of what most teams build here. |
| Custom objects | Two-way sync | Create, update, find and delete, which is more than several native connectors in this directory manage. |
| Tickets and line items | Two-way sync | Full create, update and search. Useful where the CRM is doing service work as well as sales. |
| List membership | Two-way sync | 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 | Events only | Not on a poll. The fastest documented interval is one minute, on Team and Enterprise. |

## Which field lands where

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. |

**What does not cross:**

- Active lists, as a destination. Only static lists are writable.
- The time of day on any date value. It is rounded down to UTC midnight on the way in.
- A second Zapier connection to the same HubSpot account. Adding one invalidates the existing connection rather than running alongside it.

## Connect it, in this order

**Who has to do it:** A HubSpot Super Admin. Zapier requires that permission level, so a marketing ops manager without it cannot connect the app.
**How long:** Five minutes to connect. The rest depends on how many Zaps you are about to not document.

### 1. Check you have Super Admin, and that nobody else has already connected

*Where:* 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.

### 2. Add the connection from Zapier, not from HubSpot

*Where:* 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.

### 3. Pick an instant trigger if one exists for your event

*Where:* 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.

### 4. Set the polling interval if you are on a paid Zapier plan

*Where:* 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.

### 5. Map fields with the date behaviour in mind

*Where:* 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.

### 6. Decide how contacts created this way will be attributed

*Where:* 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.

## How to check it worked

- Fire the trigger and time the gap. If it is minutes rather than seconds you are on a polling trigger, which may be fine and should be deliberate.
- Send a date with a time on it and read it back in HubSpot. It will be UTC midnight.
- Try the Add Contact to List action and look for your list. If it is missing, it is an active list, and only static lists appear.
- Create one test contact through the Zap and check its original source property before you build twenty more Zaps on the same pattern.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| Every Zap broke at once and nothing changed on your side | Somebody 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. |
| Dates arrive a day early, or at midnight | HubSpot 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. |
| The list you want is missing from Add Contact to List | It 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. |
| The Zap is slow and it is not Zapier's fault | A 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. |
| Original source reporting is full of Zapier | A 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. |
| Requests start failing in bursts | HubSpot 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. |

## What breaks, from the vendors' own docs

- **Latency is a line item.** Polling intervals are 15 minutes on the free plan, 2 minutes on Professional and 1 minute on Team and Enterprise, and a Zap can never poll faster than the greater of its plan minimum and the app minimum. Nothing you configure in HubSpot changes this. If the use case is speed to lead, read the interval as part of the price, because a 15 minute poll on a new inbound form is not speed to lead by any definition.
- **Dates round down to UTC midnight.** Zapier sends dates to HubSpot as UNIX timestamps and rounds date and time values down to UTC midnight, so a value entered west of UTC can land in HubSpot a day early. It is documented and it will not be fixed by mapping, so normalise the date in a formatter step before the HubSpot action.
- **One connection per HubSpot account.** Zapier allows a single HubSpot app connection per account at a time, and connecting another invalidates the previous one. In a team where two people have each wired up their own Zaps, the second person to reconnect silently breaks the first person's work, and nothing announces it.
- **The daily cap is shared, the burst limit is not.** HubSpot allows 190 requests per 10 seconds per app, and a daily cap of 625,000 requests on Professional and 1,000,000 on Enterprise that is shared across every app on the account. A chatty Zap therefore spends an allowance your native connectors also need, and the symptom is somebody else's integration returning 429. Zapier's help page quotes 650,000 a day for Professional, which does not match HubSpot's published figure; plan against HubSpot's.

## The APIs, if you are building around it instead

### HubSpot

- **Base:** `https://api.hubapi.com`
- **Auth:** `Authorization: Bearer <private-app-token>` for a private app, or OAuth for a marketplace app. Full CRM API access is on every tier including Free.

| Call | Request | What it does |
|---|---|---|
| `PATCH /crm/v3/objects/contacts/{contactId}` | `{ "properties": { "rc_title": "VP Sales" } }` | Update a contact. Send only the properties you own. |
| `POST /crm/v3/objects/contacts/search` | `{ "filterGroups": [...], "properties": [...] }` | Find records by property. Use this to pull the slice that is missing a field. |
| `POST /crm/v3/objects/contacts/batch/update` | `{ "inputs": [ { "id": "...", "properties": {...} } ] }` | Batch of up to 100. Prefer this over per-record PATCH at volume: it is one request against the rate limit. |

**Rules that will cost you time if you skip them:**

- **Rate limits.** A private app gets 190 requests per 10 seconds on Professional and Enterprise, 100 on Free and Starter. Daily caps are 250,000 / 625,000 / 1,000,000 calls **per account, shared across every app**. A public OAuth marketplace app is capped at 110 per 10 seconds per installing account.
- **Calling an external API from a workflow needs Data Hub Professional or Enterprise.** Both the webhook action and the custom code action live in that hub, not in Sales Hub. Check this before designing an in-HubSpot build.
- **Custom code actions get 20 seconds and 128 MB.** Combined length of all workflow secrets is capped at 1,000 characters. Secrets are read with `process.env.NAME`.
- **Workflows:** up to 50 simple on Starter, up to 300 fully customisable on Professional.
- **Never write to a property a human maintains.** Use prefixed properties (`rc_*`) and promote with a separate workflow only where the human field is empty.

**HubSpot custom code action (Node 20):**

```javascript
// Input field: email   Output fields: rc_status, rc_title, rc_company, rc_headcount
// Secret: RC_API_KEY
const axios = require('axios');

exports.main = async (event, callback) => {
  const email = event.inputFields['email'];
  const res = await axios.post(
    'https://api.reversecontact.com/v2/enrich/persons',
    { email },
    { headers: { Authorization: `Bearer ${process.env.RC_API_KEY}` } }
  );

  const person = res.data?.data?.person;
  const company = res.data?.data?.company;

  // null means "not found", not "try harder". Write nothing and flag it.
  if (!person) return callback({ outputFields: { rc_status: 'no_match' } });

  callback({ outputFields: {
    rc_status:    'matched',
    rc_title:     person.currentPosition?.title || '',
    rc_company:   company?.name || '',
    rc_headcount: company?.employeeCount || 0
  }});
};
```

Docs: https://developers.hubspot.com/docs/api/overview

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- Zapier: how to get started with HubSpot on Zapier: https://help.zapier.com/hc/en-us/articles/8495919882253-How-to-get-started-with-HubSpot-on-Zapier
- HubSpot knowledge base: use HubSpot's integration with Zapier: https://knowledge.hubspot.com/integrations/how-to-use-zapier-and-hubspot
- Zapier: control when your Zap runs: https://help.zapier.com/hc/en-us/articles/8495924437005-Control-when-your-Zap-runs
- HubSpot developers: API usage guidelines and limits: https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-zapier-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-zapier-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
