Setting Up HubSpot Form Field API MappingsSet up HubSpot form field API mappings in LeanData BookIt for Forms.May 13, 2026Knowledge
InformationTitleSetting Up HubSpot Form Field API MappingsURL NameSettingUpHubSpotFormFieldAPIMappings6901f8b2357c9Step-by-StepThis guide explains how to configure form field API mappings so you can pass values from your form into variables used in logic within your BookIt for Forms Flowbuilder graph. These mappings are set within the Trigger Node of your router graph. When specifying Form Field API Names, you'll use the Internal Name of the corresponding Contact or Company property from your HubSpot form builder—with one important distinction: For Company properties, you must prefix the internal name with 0-2/ (e.g., 0-2/industry for the "Industry" company property) For Contact properties, use the internal name as-is (e.g., email or firstname) See below for examples of how to correctly map your HubSpot properties. Note: The appearance of the HubSpot form builder may vary depending on your account or UI version. The steps remain the same across both versions, and this guide includes side-by-side screenshots to support each. 🔍 Tip: If the images appear small, click on them to expand and view the details more clearly. Map a Contact Property (Example) Say you’re working with an Email form field like the one shown below. Start by identifying which HubSpot object the field belongs to—Contact or Company. In the legacy UI: The object type is indicated directly on the field, and the Internal Name appears in italics next to the field label. In the new UI: Click on the field, then check the Object Type and Internal Name under the Connected Property tab. Since this is a Contact property, you'll enter its Internal Name directly—without any prefix—into the Form Field API Name mapping in your Trigger Node. For the Email field, you will enter email Map a Company Property (Example) Now, let's say you’re working with an Annual Revenue form field like the one shown below. Start by identifying which HubSpot object the field belongs to—Contact or Company. In the legacy UI: The object type is indicated directly on the field, and the Internal Name appears in italics next to the field label. In the new UI: Click on the field, then check the Object Type and Internal Name under the Connected Property tab. Since this is a Company property, you’ll need to add the required 0-2/ prefix before the Internal Name when entering it into the Form Field API Name mapping in your Trigger Node. For the Annual Revenue field, you will enter 0-2/annualrevenue Set Your Variables and Data Types For each mapping, you can either select one of the default variable options, or define a custom variable name and data type. ⚠️ Note: Default variables have predefined data types. If your form value doesn't match the expected data type, you'll need to create a custom variable and assign the correct type manually. Example: LeanData’s default variable Phone Number is set to the data type Phone.However, in HubSpot, the Phone Number property value is stored as Text. In this case, instead of using the default variable, you should: Create a custom variable (e.g., phone) Set the data type to Text 💡 Tip: After setting up your mappings, be sure to test your form to confirm that values are passed correctly into the graph and that no data type mismatches occur. If implemented correctly, you should see your form values populate on the BookIt For Forms Audit Logs.