Before you start
Works on free HubSpot. Webhooks by Zapier is a premium Zapier app, so the Zap needs a paid Zapier plan (or use Pabbly Connect / Make).
Steps use Zapier. Pabbly Connect and Make work the same way: same trigger, then their send-to-URL action (API by Pabbly / HTTP - Make a request) with the LeedsApp URL.
Your HubSpot Forms lead URL
Your lead URL appears here when you open this page from the LeedsApp app: open the project, then Lead integrations and HubSpot Forms.
Set it up in HubSpot Forms
1
Start a Zap with HubSpotIn Zapier click + Create › Zap workflows. For the trigger pick HubSpot, event New Form Submission, connect your HubSpot account and choose the form.
2
Test the triggerSubmit the form once yourself, then click Test trigger so Zapier picks up a real submission to map.
3
Add Webhooks by ZapierAdd the action Webhooks by Zapier, event POST.
4
Paste your LeedsApp URLPaste your LeedsApp URL in URL and set Payload Type to JSON.
5
Map the fields and testUnder Data add name (First name + Last name), phone, email and city, then click Test step; a reply with code: success means LeedsApp got the lead.
6
PublishClick Publish. New submissions reach the project within a minute or two.
What LeedsApp saves
HubSpot Forms sendsSaved on the lead as
Lead source: HubSpot. If you have Data Hub (Operations Hub) Professional, a workflow's Send a webhook action can post the same keys directly instead.nameNamephoneMobile numberemailEmailcityCitymessageNotesany other keyCustom fieldIf leads don't arrive
- Add a Phone number field to the HubSpot form and map it to phone; a submission with no phone is not saved.
- Check the Zap is on and the right form is picked in the trigger.
- New submissions usually arrive within a minute. If not, open Zap runs in Zapier and check the Webhooks step.
- A 400 reply saying The mobile number is not valid means the phone answer was not a real mobile number. Map the phone question, not another field.
Need help? Write to support@leedsapp.com