I’m trying to set up an automated workflow that sends form submissions from my Netlify website directly into HubSpot using Zapier as the connector. I want to make sure that whenever someone fills out a contact form on my Netlify site, their information gets automatically added to my HubSpot CRM.
I’ve been looking at both platforms but I’m not sure about the exact configuration steps needed to make this integration work properly. Has anyone successfully set up this kind of automation before?
What I’m specifically looking for:
- Step by step process to connect these three services
- Any webhook configurations needed on the Netlify side
- How to map the form fields correctly in Zapier
- Best practices for testing the integration
Any guidance on setting up this automated pipeline would be really helpful. I want to make sure I don’t miss any important configuration details that could cause the integration to fail.
Just completed this integration last month for a client project and ran into a few gotchas that might save you some headache. Beyond the basic webhook setup that Grace mentioned, you’ll want to enable form detection in your Netlify site settings first - sometimes the forms don’t get recognized automatically. One issue I encountered was that Zapier’s webhook sometimes received malformed data when users submitted forms with special characters or empty optional fields. I solved this by adding validation on the Zapier side using their ‘Filter’ step to only process complete submissions. Also worth noting that HubSpot has rate limits on API calls, so if you’re expecting high volume submissions you might want to add a delay step in your Zap. The field mapping is pretty straightforward but make sure you’re using HubSpot’s internal property names rather than the display names - they’re different and it’ll cause silent failures otherwise. Test thoroughly with various input scenarios including edge cases like really long text entries.
been using this setup for about a year now and one thing nobody mentioned - make sure your netlify form has the proper action attribute pointing to the same page, otherwise submissions might not trigger the webhook correctly. also double check that your hubspot api key has the right permissions for contact creation, learned that the hard way when contacts weren’t showing up but zapier was showing successful runs.
Worth mentioning that the webhook payload from Netlify includes some extra metadata fields that you might not need in HubSpot, so configure your Zapier mapping to only pull the actual form data rather than sending everything through. I discovered this when my HubSpot contacts started getting populated with random Netlify-specific fields like submission timestamps and form IDs. Another practical tip is to set up email notifications in Zapier for failed Zaps because the integration can break silently if HubSpot changes their API or if your webhook URL gets corrupted somehow. The error messages aren’t always obvious and you might miss failed submissions for days without realizing it. Also consider adding a confirmation page redirect on your Netlify form so users know their submission went through successfully, independent of whether the backend integration worked.
I actually implemented this exact setup about six months ago and it works perfectly once you get the webhook URL configured correctly. The key thing that tripped me up initially was that Netlify requires you to add a hidden form field with name=“form-name” that matches your form’s name attribute for the submissions to be captured properly. After setting up the form with proper Netlify handling, you create a new Zap in Zapier using “Webhooks by Zapier” as the trigger since Netlify doesn’t have a native Zapier integration. Copy the webhook URL from Zapier and add it to your Netlify site’s form notifications settings under Site Settings > Forms > Form notifications. For the action side, connect to HubSpot and map your form fields to the corresponding HubSpot contact properties. I’d strongly recommend testing with dummy data first because debugging failed submissions can be frustrating when you’re not sure if the issue is on the Netlify, Zapier, or HubSpot side.