We are currently facing some difficulties connecting our form to HubSpot. We use several forms on our website (TYPO3) that have some special features that cannot be replicated with native HubSpot forms (or at least it seems so and our HubSpot agency says so). One example is this form: Vergütungssatzverhandlungen in der Kinder- und Jugendhilfe Furthermore, we have contact forms for our Experts that send a notification with the request itself to them when somebody fills in the form. Currently, it is not an option for them to just use HubSpot itself and use native contact form there.
So up until now we used the third party form integration in HubSpot. However, the result was that only the Email got routed correctly. Everything else could not be routed correctly because the forms on our site have German field names.
So now we come to the question at hand: Our TYPO3 and our HubSpot Agency proposed that we implement an API. This API, however, does not transfer the URL where the form got filled in. This is a bit problematic for us, looking for example at the booked seminars. Therefore, they came up with implementing a new property "last_from_url" that would store the url the user visited when filling in a form. However, this would get overwritten as soon as the user fills in another form. Hence we still would not be able to use the information in workflows or the likes.
Has anybody any ideas on other solutions for the problem? Either by another workaround or another method of implementing the HubSpot forms directly.
This endpoint allows passing in context parameters, such as pageUri and pageName, that would get stored with each form submission. This will not require using a contact property (which would get overwritten as you have mentioned) and you can then use the pageUri in your worfklows to target form submissions that happen on specific URLs.
Hope this helps!
✔️ Did this post help answer your query? Help the community by marking it as a solution.
This endpoint allows passing in context parameters, such as pageUri and pageName, that would get stored with each form submission. This will not require using a contact property (which would get overwritten as you have mentioned) and you can then use the pageUri in your worfklows to target form submissions that happen on specific URLs.
Hope this helps!
✔️ Did this post help answer your query? Help the community by marking it as a solution.
