# HubSpot and Zapier: what a zap writes, and a weekly duplicate check

https://salesbond.app/blog/hubspot-zapier-integration-duplicate-records-owner-check/
Published: 2026-10-27 · Updated: 2026-11-14

The HubSpot Zapier integration writes through one connected user, so every record a zap creates needs an owner and a duplicate rule. Put a find step in front of every Create action, map the owner field instead of leaving it blank, and once a week open the records your zaps created that have no owner or match a contact you already had.

## Ways to connect Zapier and HubSpot

There are three routes, and most teams end up running two of them at once.

The first is the HubSpot app inside Zapier. Instant triggers fire as soon as the event happens; polling triggers check for new data on a schedule that depends on your Zapier plan ( [Zapier: update times for Zap triggers](https://help.zapier.com/hc/en-us/articles/8496181725453-Update-times-for-Zap-triggers)). A zap that feels late is usually on a polling trigger.

You can also start from HubSpot: in the HubSpot Marketplace, search for Zapier, click Install and log in (Super Admin or App Marketplace access permissions). Zapier then gets an Embedded Zaps tab under Settings > Integrations > Connected Apps, with zap templates you can start from inside HubSpot ( [HubSpot: use Zapier and HubSpot](https://knowledge.hubspot.com/integrations/how-to-use-zapier-and-hubspot)). It’s the same connection either way.

The second route is a HubSpot workflow with a webhook: POST sends data out, GET pulls data in. It sits under Data ops > Send a webhook, the URL must begin with HTTPS, and setup takes Edit permissions for workflows or Super Admin. HubSpot lists it under Data Hub Professional and Enterprise ( [HubSpot: use webhooks with HubSpot workflows](https://knowledge.hubspot.com/workflows/how-do-i-use-webhooks-with-hubspot-workflows)). We use it when the condition is complicated, because a workflow enrollment rule is visible to the whole team and a Zapier filter is not.

The third route is everything else: another automation platform, a script against the HubSpot API, or the source app’s own integration. If that app already has its own listing in the HubSpot Marketplace, compare it with the zap before building, and record the choice in your [allow-list of HubSpot integrations that write to deals](https://salesbond.app/blog/hubspot-integrations-write-to-deals-manager-allow-list/).

## Setup in one paragraph

To connect, you need an active HubSpot account (free or any paid plan) and Super Admin permissions in it. In Zapier, open the Apps page, click + Add connection, search for HubSpot, log in and grant access. One thing to know before you click: you can have only one Zapier connection to a HubSpot account at a time, and connecting another one invalidates the previous connection. Two more limits come up in sales teams. Add Contact to List works with static lists only; active lists do not show up in the dropdown. And date/time values sent through Zapier to HubSpot are rounded down to UTC midnight, so a close date written by a zap will never carry a time of day ( [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)). Our position on the connecting user: it should be a company admin account, not the sales manager’s login, because the day that person reconnects or leaves, every zap in the account goes with them.

## What a zap writes: deals, contacts, notes, tasks

The [HubSpot app on Zapier](https://zapier.com/apps/hubspot/integrations) can do more to a record than its builder usually expects, and five of its actions deserve a look first.

- Create Contact makes a new contact on every run; Create or Update Contact matches on email first, which makes it the safer default.
- Create Deal and Update Deal write owner, pipeline, stage, amount and close date.
- Create Associations links a deal to a contact. Skip it and the deal sits without a contact.
- Add Contact to Workflow enrolls the contact, so whatever that workflow writes is the zap’s doing too.
- Delete CRM Object removes the record.

Notes and tasks go through Create Engagement, which adds an engagement to a contact. Create or Update Contact also carries a HubSpot Owner field, with each owner’s ID in gray after the user’s name ( [Zapier: common problems with HubSpot](https://help.zapier.com/hc/en-us/articles/8495951826445-Common-Problems-with-HubSpot)). Leave it empty and the contact lands in nobody’s queue.

## Find-before-create: the duplicate rule

Zapier’s advice on duplicates starts with “use a find or create action in your Zap”, and the example it gives is HubSpot’s Find or Create Deal ( [Zapier: Zap is creating duplicate data](https://help.zapier.com/hc/en-us/articles/8496218141453-Zap-is-creating-duplicate-data)). One older deal search in the catalog is marked deprecated with a note to switch to Find Deal, so pick the current one.

Our order for a sales zap: Create or Update Contact keyed on email, then Find Deal, then a Filter that stops the zap when a deal was found, then Create Deal, then Create Associations.

What you search deals by matters more than the order. Deal names get retyped. Give the deal a custom property for the external ID (an order or request number from the source system), write it on create and search on it. For contacts trim and lowercase the email before searching; a trailing space makes the same person look new.

The general causes are in [why your Zaps create duplicate deals](https://salesbond.app/blog/pipedrive-zapier-duplicate-records/), written for Pipedrive. Two matter for HubSpot. A New Contact in List trigger on a dynamic list can fire before HubSpot has filled properties such as Original Source; Zapier’s fix is a “property X is known” condition on the list. And before replaying a run that timed out, search HubSpot for the email: Zapier warns the replay “may be creating duplicate data”.

## The weekly check in HubSpot

A duplicate or an ownerless contact is invisible from inside Zapier. The run is green.

So the check happens in HubSpot, and it needs the zap to mark its own records. Our practice is a custom “Created by” property that nothing else sets, filled with the zap’s name in the Create step. HubSpot’s own Record Source property shows how a contact was created, but the zap’s name helps more once you have six zaps. Then a saved view on contacts and one on deals, filtered on that property and a create date in the last seven days, read with three questions:

1. Which records have an empty Contact owner or Deal owner? Nobody will call those.
2. Sorted by email, who appears twice? Same email a minute apart is a double form submission; same email a month apart is a returning buyer who now has two histories.
3. Which deals have no task or note since they were created? That is pipeline in the report and nothing in anyone’s week.

![Weekly review flow: a saved view of zap-created records, three checks (owner, duplicate email, task or note), each with an action.](https://salesbond.app/wp-content/uploads/2026/10/hubspot-zapier-integration-duplicate-records-owner-check-2.png)

Write the three counts down each week. They tell you whether the fix belongs in the zap, in a HubSpot workflow that assigns an owner on create or in the habit of whoever owns the form.

## Who owns each zap

Ask a five-person sales team who owns the zap that turns demo requests into deals, and you will usually get the name of someone who no longer works there.

Keep one line per zap next to the allow-list: what triggers it, which records it creates, whose HubSpot connection it runs on, what it writes into “Created by”, and who answers for the weekly list. Map the record owner rather than hardcode it: the Get Owner by Email search looks the owner up from a rep’s email, so no ID goes stale when a rep leaves.

A disclosure: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive, and HubSpot is one of the 15 CRMs it works with. Its free CRM audit reads the last 30 days of the connected CRM and sends a PDF report with money at risk, managers, deal health and what to fix, then a second PDF a week later showing what changed. [Check your CRM with SalesBond](https://salesbond.app/) if you want that outside read next to your weekly list.

None of this makes Zapier stop creating records with no owner. Forms get submitted twice, a colleague clones a zap and skips the the Find step, someone reconnects the account on a Friday. What changes is that you find it on Monday, from the HubSpot side, before it is in the forecast.
