-
-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Page title in Hubspot Form integration context data #2029
Comments
We already automatically include the It's not something we can map in the form integration settings without having it map to a Hidden field that you'd populate with the entry's title when rendering the form. We could maybe scrape it from the referrer's meta title, but I'd rather not add that sort of overhead. In Formie 3 for Craft 5, you'll be able to use PHP events in a module to add this sort of thing as context variables for the integration, to send along with the payload. For now, I've added "Page Name" and "Page URI" to the mapping interface where you can handle all this through hidden fields, and populate them in your templates. Updated for the next release. To get this early, run |
Excellent. Thank you very much! |
Hello @engram-design Checked. Works. Looks a bit dirty. |
Ah, that's my mistake not removing them from the mapping of the contact object. Updated for the next release. To get this early, run |
Should have double-checked that, sorry. Updated for the next release. To get this early, run |
Fixed in 2.1.27 |
What are you trying to do?
If I try to submit a HubSpot form via the Formie integration, I only see the url in the results table. It looks like the form page title is not being added to the context when the form is submitted.
What's your proposed solution?
Could you please add the form page title to the HubSpot context as provided in the Forms API??
https://legacydocs.hubspot.com/docs/methods/forms/submit_form_v3_authentication#:~:text=As%20this%20API%20is%20authenticated%2C
Result:
Thanks
Additional context
No response
The text was updated successfully, but these errors were encountered: