Hubdb data prepopulate on hubspot form

Developer Support
1

Hi guys,

am facing an issue with pre-populating contact properties in a form. I am using HubDB to store the contact properties because I have around 30 fields that need to be pre-populated. Using URL parameters/tokens for all 30 properties makes the URL too long.
Requirement:
I want to pre-populate around 30 contact properties in the form.
What I have built:
I created a workflow that triggers when a new contact is created.
The first custom code action retrieves the contact properties and stores them in HubDB.
The next action sends an email to the user with a link to the form.
The data is successfully being stored in HubDB, and the user receives the email.
However, the contact properties are not being pre-populated in the form.
I am using a custom ID field to retrieve the corresponding data from HubDB.
Issue:
The data is available in HubDB, but it is not being populated into the form when the user opens the form.

Thank you

3

Hey @vinayakhnr6,

Thanks for walking through your setup so clearly!

It sounds like the issue lies at the beginning of your process with your form population. Here are a few of things worth checking while you wait for some folks from the community to chime in. These resources might help point you in the right direction:

Tagging in a few folks who may have tackled something similar:

Hey @Josh, @anton, @lnorden – do you have any suggestions for @vinayakhnr6 on this?

Thanks in advance!!

Sam | Community Manager

4

Hi @vinayakhnr6 ! Thanks for the tag @stassey. Lets see if I can offer any help here.

I don’t have a ton of experience with this specific scenario, but I think there may be a disconnect between storing the data in HubDB and actually passing those values into the form.

From my understanding, having the contact data stored in HubDB wouldn’t cause a standard HubSpot form to retrieve that row and populate the corresponding fields. Something would still need to pass those values to the form, usually via query or custom code.

If you’re using dynamic query strings with HubSpot personalization tokens, there are some requirements that have tripped me up before:

  • The URL needs to point to a HubSpot-hosted page containing a HubSpot form. (<—this is the one that made our attempts unsuccessful, our page is not hosted through HubSpot)
  • The URL containing the dynamic query string needs to be placed in HubSpot content or on an external page containing the HubSpot tracking code.
  • Make sure you’re using the properties’ internal names in the query string.

Trying to populate 30+ fields is going to be a challenge with any route but I will admit, query strings/custom form development aren’t my deepest area of expertise, so someone with more dev experience may have more insight than I do, but those are the things I would be checking first!

When you find a good solution, I’d love to hear what worked for you!