Creating custom HubSpot contact properties directly from flng.ai

When you publish a form, every field needs somewhere to live in HubSpot. Most of the time you map to a property that already exists. But when you are collecting something new, you need a new property, and flng.ai lets you create one without ever leaving the publishing page.

Field versus property: the distinction that matters

A field is the input a visitor fills out on your form, like a text box or a dropdown. A property is where that answer is stored on the contact record inside HubSpot. Publishing a form is really the act of connecting each field to a property so the data has a home.

Mapping to an existing property

For standard fields like first name, email, and phone, HubSpot already has matching properties. During publishing, you map your form field to the existing property with a click. Done.

Creating a new property on the spot

Say your form asks "What is your budget range?" and you have no property for that yet. Instead of stopping to go build one in HubSpot settings and coming back, you create it right there in flng.ai. Give it a name, pick a type, and flng.ai creates the property (and a property group to keep things tidy) in your HubSpot account through the HubSpot API.

Why this saves real time

The old workflow meant bouncing between two tabs: build the property in HubSpot, switch back, refresh, map it. Doing it inline keeps you in one place and one train of thought. For a form with several custom questions, that adds up quickly.

What happens after you publish

Once the form is live, every submission writes to the properties you mapped. If a contact already exists, their properties update in real time. If not, a new contact is created with those property values filled in. Your new custom property behaves exactly like any other HubSpot property from that point on: you can segment on it, use it in workflows, and report on it.

A few tips

• Name properties clearly so future-you knows what they hold.
• Pick the right field type (dropdown, number, date) so HubSpot can filter and report on it properly.
• Reuse existing properties where you can, to avoid cluttering your CRM with near-duplicates.

The takeaway

Creating HubSpot properties used to be a separate chore. With flng.ai it is part of publishing, so your form and your CRM stay in sync without the tab-switching.