Zapier

Estimate tasks and overage

Zapier counts successful Classic Zap action steps rather than whole workflow runs. Model each form submission through searches, creates and updates, including branches and any downstream loops. A single lead can produce multiple billable actions; a filtered submission may produce none.

Zapier’s pay-per-task guide says enabled accounts can continue above their allowance at an account-specific rate, subject to a maximum. Its availability and default depend on account and plan; inspect billing settings and ask what happens to held runs and charges.

Zapier’s usage guide specifies different treatment for other products and says Next Gen Zaps billing begins December 1, 2026. Do not assume the Classic Zap calculation covers every product or a future plan.

Zapier says Next Gen Zap and SDK task billing starts December 1, 2026 at 17:00 UTC. Completed Next Gen runs have a one-task minimum, including runs stopped by a filter. The minimum is not an additional task when another charge already applies.

Design replay around side effects

Zapier says replay resumes eligible errored steps and requires sufficient tasks; Filters and Paths are not replayed. Check whether earlier CRM writes succeeded before replaying a failed step, especially after a timeout where the remote result is unknown.

Use a stable submission ID as a destination idempotency key where supported, or search and update a matching record under an agreed rule. Reconcile source submissions, Zap history and CRM records; alert an owner to failures rather than silently discarding them.

Zapier warns that importing a Classic Zap into Next Gen creates a copy while the original keeps running. Turnover requires an explicit cutover and a duplicate-write test.

See Zapier’s illustrated replay guide for vendor screenshots of replay in Zap history and the editor.

Separate workflow access from connection access

Zapier says app connections are private by default and can be shared on Team or Enterprise accounts. Shared users can use the connection and view test data. Give a dedicated integration identity only the destination permissions required.

Zapier’s role guide says private connections restrict who can edit their steps, while users with Zap access may see data in history. Review folder sharing, logs and departure procedures with the actual account roles.

Accept the lead in the CRM

For a form-to-CRM workflow, map source ID, email, campaign fields and consent deliberately. Confirm the CRM accepts the record and assigns the intended owner; a successful automation step alone does not prove the correct business outcome. Test rejected fields, rate limits, duplicate submissions and permission changes with authorized test data.

Agree on a monitoring owner, recovery window and a way to export or reconcile source records before switching providers. Review who can see payloads in execution history and how long the chosen plan retains them.

HubSpot says CRM API writes using its 2026-09 version enforce administrator-configured required and conditional properties. User-level OAuth association changes can also require permission. Confirm the connector’s API version and test validation errors; HubSpot says required associations remain enforced in the app UI, not public API writes.

Zapier’s history guide says it guarantees at most 60 days of run data and displays up to 10,000 runs. Plan an appropriate export and secure retention policy if your investigation window is longer.

How to compare the alternatives

Compare the same form-to-CRM handoff with Make and n8n. The Zapier vs Make comparison compares the billing and recovery questions. See the forms and CRM guides for the endpoints.

Common questions

Does one Zap run equal one task?

Zapier counts successful action steps, so one run can consume more than one task. Check the actions and product-specific rules.

Does replay prevent duplicate CRM records?

Zapier describes replaying eligible errors; duplicate protection depends on the workflow and destination. Verify existing writes before retrying.

Sources and scope

We read the linked vendor documentation on November 5, 2026. This is documentation-only research; we have not used these products, executed workflows or tested integrations.

Inclusion and corrections are free; sponsorship does not determine our conclusions. Confirm current terms and test your own configuration.

Sponsorship never changes this page. How we research.