Creating a HubSpot contact
Someone leaves their details on your site and they land in HubSpot as a contact.
This is written and tested against our own rules, but it has never exchanged a single request with the real HubSpot service. Treat it as ready to connect, not as proven.
What it is for
An enquiry form is only useful if somebody follows it up, and follow-up lives in the CRM.
Name, company and phone travel with the email address.
When the site and the CRM are separate, somebody retypes the details, and retyping loses some of them.
What you need
A HubSpot private app with permission to write contacts, and its access token saved in Project secrets. Grant nothing beyond contact write.
The order to do it in
Decide which form fields matter before you connect. Email is required; everything else is optional.
Then save the token and point the form at it.
Line up the property names on both sides first and there is nothing to fix later.
How to check it worked
Submit the same email twice. The second submission updates the existing contact instead of making a duplicate.
Only the contact id is returned to the app. HubSpot's full record is not reflected back.
A failure is reported as a failure. HubSpot's own response text is not leaked onto your customer's screen.
What it will not do
- Deals, tickets and companies are not created from here. Contacts only.
- Names and company are capped at 100 characters, phone at 40.
- Up to 2,000 calls per project per day across Slack, Notion, HubSpot and Salesforce together.
- An address that is obviously not an email is refused before it leaves us.
- It writes. It does not read your contact list back into the app.