Hello!
I have been facing an issue with contact form submissions.
To get hubspot data, I am using Airbyte technology, and on their documentation they mentioned the new hubspot version v3 has no Contact Form Submissions anymore:
HubSpot Connector | Airbyte Documentation.
They suggest to use Form Submission instead, however the schema is not the same.
Do you know if there is any other option where we could get back the Contact Form Submission?
I see this post here: https://community.hubspot.com/t5/APIs-Integrations/How-to-Retrieve-Contact-Form-Submissions-v3-API/m-p/1118941#M80724
But the solution only says about form submissions.
However I need the relation between the contact (conversarion ID) and the form submission details, not only the form-id
Do you have an idea how can I achive it?
Thank you!
Hi @DPlatform and welcome, it’s a pleasure to have you here! 
Thanks for reaching out to the HubSpot Community!
Here are some resources that might be of interest:
- CRM API | Associations v4
- POST /crm/v3/objects/feedback_submissions/search
- CRM API | Contacts
Now, let’s consult our Top Experts: Hi @sylvain_tirreau, @Anton and @SteveHTM do you have suggestions to help @DPlatform, please?
Have a wonderful day and thanks so much!
Bérangère
Hi @DPlatform
Hey, that seems to be a problem in the recent update. However, there is a workaround which is using this “/crm/v3/forms/{formId}/submissions”" API to get the email of the contact who has submitted the form. You will get the form ID from the new submission form API. Then you can link both in the backend anyway you want.
I hope this will help you out. Please mark it as Solution Accepted and upvote to help another Community member.
Thanks!
Hi @DPlatform , this change is confusing, especially when you were relying on the old “contact form submissions” shape.
What Airbyte is reflecting is basically HubSpot’s move away from the legacy Contact-Form-Submissions object into the newer forms + submissions model. There isn’t a hidden v3 endpoint that brings that old object back, so you have to reconstruct the relationship yourself: pull submissions via the Forms endpoint, then join them to contacts using an identifier like email or hs_object_id on your side.
In practice that means: get form submissions with /crm/v3/forms/{formId}/submissions, read the submitted email (or another unique field), then link that to the contact you’re already syncing via the Contacts API. From there you can store a lightweight “contact_form_submissions” table in your warehouse that mimics the old schema and keeps the conversation/form link you need.
If your broader goal is to centralize all submissions and contact data from multiple tools (Airbyte, HubSpot, other forms) into one clean model, Stacksync keeps HubSpot and your source database in two-way sync so every new form event lands already tied to its contact, without extra stitching each time.