How to send Webflow form submissions to HubSpot via Zapier without losing data
The guide walks users through linking a published Webflow form to HubSpot using Zapier’s “New Form Submission” trigger and HubSpot’s “Create or Update Contact” action. It stresses publishing the form, making a test submission, and then creating the Zap—otherwise the form won’t appear in Zapier’s dropdown. Field names must match exactly, and custom HubSpot properties need the “Use in forms and bots” flag enabled, or Zapier won’t surface them. Each submission consumes one Zapier task; free accounts are capped at 100 tasks per month, while the Professional plan (US$19.99‑$29.99) offers 750 tasks and adds multi‑step Zaps and premium apps. The workflow runs in real time via Webflow’s webhook, falling back to polling every 2 minutes on paid Zapier tiers or every 15 minutes on the free tier, which can introduce a delay if the webhook fails.
This workaround reflects a broader pattern where SaaS platforms rely on integration hubs like Zapier to fill native connectivity gaps. Webflow and HubSpot both lack a built‑in two‑way sync, so marketers resort to low‑code bridges to keep lead data unified. Zapier’s pricing model and task quotas have become a de‑facto cost factor for small teams that otherwise use free tiers of Webflow and HubSpot. Competitors such as Make (formerly Integromat) and native API solutions offer similar capabilities, but Zapier’s extensive app catalog and user‑friendly UI keep it dominant for non‑developers. The emphasis on precise field naming and property setup mirrors a growing awareness that data hygiene at the integration layer is critical for downstream automation, reporting, and personalization.
Looking ahead, teams should monitor Zapier task consumption closely; hitting a limit mid‑month would silently drop leads, undermining sales pipelines. The reliance on webhook delivery means occasional latency or missed submissions if Zapier’s fallback polling is triggered. Organizations with higher volume or stricter latency requirements may need to invest in a paid Zapier tier, build a custom middleware, or push for a native Webflow‑HubSpot connector. Additionally, any changes to form names, property schemas, or account permissions will break the Zap, so a change‑management checklist is advisable.
Key Takeaways
Publishing the form and submitting a test entry are mandatory before the Zap can detect the Webflow form.
Free Zapier accounts only support 100 form submissions per month, so high‑traffic sites must upgrade to avoid data loss.
HubSpot deduplication hinges on the email field; mismatched property names or missing custom fields will prevent updates.
Webhook failures cause a fallback to polling, which can add up to a 15‑minute delay on Zapier’s free tier.
About the Source
This analysis is based on reporting by Webflow Blog. Here is a short excerpt for context:
Learn how to send Webflow form submissions to HubSpot via Zapier.Read the original at Webflow Blog
