Hello, I'm trying to find a way to standardise our address formatting in Hubspot.
We're B2C, and people can submit their address details using forms, or the sales team can input address details into the contact. However everybody inputs their addresses differently and it makes the data a mess.
The ideal solution would allow a user, either a sales team member or a user on a form, to type in their postcode. A postcode finder would then list the available addresses, which the user would select and it would populate 'Street Address' 'Town' 'City' accordingly.
Does anyone know of any postcode finders or software that is either provided by Hubspot, or can be integrated with it, to create a way for uniform address inputting? We're based in the UK so this will need to work for UK addresses.
I think the best approach would be to export the data, clean it up, and then re-import it into HubSpot. This would ensure a clean and uniform database moving forward.
One thing to keep in mind: for large-scale operations, Make can become quite expensive. If you have a lot of historical data to fix, an alternative could be to process addresses through an automated workflow using n8n before re-importing them.
Once the database is clean, integrating Make would be ideal to ensure that all new addresses are properly formatted as they are entered.
Thanks so much for your suggestion. How would this work for existing data? At the moment, our address data is mismatched between Street Address / Postal Code (e.g. 'Street Address' contains 1 Example Street, Sample Road, and then Postal Code has the postcode (e.g. AB1 2CD), but then other contacts have the full address under 'Street Address' and 'Postal Code' is left blank (e.g. 1 Example Street, SAMPLE Road, AB1 2CD).
Would this Make integration also work for historical address data, or would we have to export all contacts, tidy up their address data in an Excel / Google sheet, and then re-import and use this integration for future address data inputting?
Hope this all makes sense! Thank you again for your help.
I think the best approach would be to export the data, clean it up, and then re-import it into HubSpot. This would ensure a clean and uniform database moving forward.
One thing to keep in mind: for large-scale operations, Make can become quite expensive. If you have a lot of historical data to fix, an alternative could be to process addresses through an automated workflow using n8n before re-importing them.
Once the database is clean, integrating Make would be ideal to ensure that all new addresses are properly formatted as they are entered.
I don’t think it’s possible to directly integrate a postcode finder into the form. However, you could set up workflows (or n8n/make.com automation) that communicate with an API like Google Places (or Google API Address Validation) to enrich and standardize address properties based on the form inputs.
The general idea would be to take the raw data from the form and then process it through workflows to reformat and enhance the information. Concretely, the goal is that if an address is entered incorrectly or inconsistently, the API we integrate with should be able to “correct” it and properly format it before storing it in HubSpot.
Feel free to reach out if you have any questions!😊