Zapier HubSpot trigger not working or running late: how to find the cause

When a Zap with a HubSpot trigger doesn't fire, or fires late, the cause is often the trigger type. Many HubSpot triggers on Zapier are polling triggers, which means Zapier asks HubSpot for new data on a schedule set by your Zapier plan. On the Free plan that check runs every 15 minutes, so a contact created now can take up to 15 minutes to reach the Zap. The other frequent causes are a broken HubSpot connection and records that existed before the Zap was switched on.

The first thing to check is the Zap's run history for the time the change happened in HubSpot. If there's no run at all, the problem is the trigger or the connection. If there is a run marked Filtered, Errored or On hold, the trigger worked and something later stopped it.

Why a HubSpot trigger doesn't fire in Zapier

The trigger polls, and the interval is longer than you expect

Zapier labels each HubSpot trigger as Polling or Instant in its HubSpot integration guide. New Deal, New Form Submission, New Contact in List, Deal Property Change and New Contact Property Change are instant. New Contact, New Company, New Ticket, Contact Recently Created or Updated and Updated Deal Stage poll. Instant triggers show a lightning bolt icon in the Zap editor.

As of October 2026, Zapier's trigger guide lists polling every 15 minutes on Free, every 2 minutes on Professional and every minute on Team and Enterprise. Paid plans can change when polling runs for each Zap and can poll by hand in the editor. If timing matters, an instant trigger is the better choice. Deal Property Change on the Deal stage property fires when the stage changes, and a filter step can then check for the stage you want. Updated Deal Stage waits for the next poll.

The record existed before the Zap was turned on

Zaps don't trigger on old data, including records created before the Zap was switched on. A polling trigger also compares each item's ID with the IDs it has already received, and it skips anything it has seen before. So editing an old contact won't fire a New Contact Zap, and a test in the editor only shows the three most recent items Zapier found. For records that already exist, Zapier points you to its Transfer feature.

The HubSpot connection broke

Zapier allows one app connection to a HubSpot account at a time. If someone connects the same HubSpot account again, the earlier connection stops working, along with every Zap that used it. On the HubSpot side, connecting needs a Super Admin or a user with App Marketplace access permissions, according to HubSpot's Zapier article.

To check, open the trigger step, go to its Account tab and confirm the right HubSpot account is selected and working. Reconnect it if not. While an app account is disconnected, Zapier puts runs on hold and keeps the trigger data, so nothing is lost while you fix it.

The trigger event or its options don't match

Updated Deal Stage watches one specified stage. New Contact in List watches one list. Property change triggers watch one named property. If the Zap points at the wrong stage, list or property, it will never see the change you made. Check the App & event tab and the Configure tab of the trigger step. If the Zap waits on a HubSpot workflow to set a property or add a contact to a list, check that workflow too, using why a HubSpot workflow isn't triggering.

The Zap ran and something later stopped it

Each run has a status. Filtered means a filter's conditions weren't met. Errored means a step failed, and a Zap that errors repeatedly turns itself off. On hold covers disconnected accounts, plan changes and task limit overages. On plans without pay-per-task billing, Zapier holds new runs once you reach your task limit until the billing cycle resets. Zapier's page on run statuses explains each one.

How to fix a HubSpot trigger that isn't firing

1. Open the Zap's run history for the time the HubSpot change happened and note whether a run exists and its status.
2. Confirm the Zap is on, using the switch in the top left of the Zap editor.
3. In the trigger step's Account tab, confirm the HubSpot connection works. Reconnect it with a user who has Super Admin or App Marketplace access if it doesn't.
4. Check the trigger event and every option in the Configure tab against the stage, list, form or property you expect.
5. Make a fresh change on a test record in HubSpot. Then wait one polling interval, or poll by hand on a paid plan.
6. If the run was Filtered, Errored or On hold, fix the filter, the failing step, the connection or the task limit, then replay the held runs.
7. If the Zap works but too slowly, switch to an instant trigger or adjust the polling schedule.
8. If nothing changes, turn the Zap off and on again. Zapier suggests this to refresh the connection.

How to stop it happening again

Keep one person in charge of the HubSpot connection in Zapier, so nobody reconnects it from another account. Set up alerts with Zapier Manager, which has New Zap Error and Zap Turned Off triggers you can connect to an email step. Zapier also emails you at 80% and 100% of your task limit. Put filters near the start of each Zap, since filter steps don't count as tasks, though filters need a paid Zapier plan. Keep a written list of every Zap and what it does.

From client work

At Phoenix Industrial Cleaning, Zapier use was heading to 4,000 to 5,000 tasks a month on a 2,000-task plan. I removed the dead Zaps, merged the two job Zaps and moved the filters first, so routine job edits now cost zero tasks and use is projected at 1,500 to 1,900 tasks a month.

In the Zapier build for IAP Foundation, an error alert Zap sends the team a link to any failed run, and Storage by Zapier remembers each donation ID so an updated donation is never logged twice.

If your Zaps keep breaking or the task count keeps climbing, I can go through your Zapier and HubSpot setup and rebuild the Zaps.

Questions

How long should a HubSpot trigger take in Zapier?

Instant triggers receive data as each event happens. Polling triggers wait for the next check, which runs every 1 to 15 minutes depending on your Zapier plan.

Why did my Zap turn itself off?

Zapier turns a Zap off automatically when it errors repeatedly. Open the errored runs, fix the failing step, then turn the Zap back on.

Do HubSpot triggers use Zapier tasks?

No. Trigger steps and filter steps don't count as tasks. Successful action steps do.

Can a HubSpot workflow start a Zap directly?

Yes, with the Send a webhook workflow action pointed at a Webhooks by Zapier catch hook. Webhook actions need Data Hub Professional or Enterprise, and Webhooks by Zapier is a premium app, which needs a paid Zapier plan or a trial.