Hi @AliceM, thanks for joining the Community!

I’ve been looking into this on our end and found a bug report where the Create Form Submission (HubSpot) action is appearing as successful in the Zap History but, if you click onto Data Out it will show a “This action returns no data” message. 

Can you take a look at the Data Out for the HubSpot action, on a recent run of the affected Zap, and confirm whether you’re seeing that same message? 

If you are we’ll get you added to the list of affected users on that bug report. If you’re not seeing that message, are you seeing any error messages appearing for the attempted submissions on the form in HubSpot? If you are can you share a screenshot of those here so we can take a closer look? Please remove/hide any private information like names, emails etc. from any screenshots first though.

Looking forward to hearing from you! 

Hello @SamB thank you for your reply!

Actually, we use the action “Create or Update Contact in HubSpot”, instead of the action “Create Form Submission”.

That said, I had a look at the “Data Out” for this action and compared a successful case vs. an unsuccessful one. I can see that the former has a long list of data sent out to Hubspot indeed, including value form-submissions, while the latter reports that the field form-submissions has no value - however, they both completed the same form. 

Thank you for taking the time to answer!

Best, 
Alice

Hi again @SamB :) 

I tried to change action. 

Instead of “Create or Update Contact in HubSpot”, I selected “Create Form Submission”, however this is the error message I get

Any ideas how I can fix it? 

Thank you, 
Alice

Hi there @AliceM,

I’m jumping in to see if I can help!

Before we dive deeper into the issue, would you mind sharing a screenshot of the "Action" section in the "Create Form Submission" step? There could be a specific field that needs a certain value.

Thanks! 

Hello @ken.a thank you for your reply, here comes a screenshot of the Action section: 

Hello @ken.a and @SamB any suggestions on this issue? Thank you :) 

Hi @AliceM,

Thanks for the screenshot!

I looked at the screenshot, and I'm having trouble identifying the cause of the error you're receiving. However, I want to double-check if the mapped data matches the options in the drop-down field on the screenshot. The reason I'm asking is that drop-down fields require specific data to be selected for the Zap to work properly. Can you please confirm if the mapped data matches the options in the drop-down field on the screenshot?

(view larger)

Please keep us posted! 

Hi @ken.a , do you mean showing you this? If yes, values seem to be correctly set. 

Hi @AliceM,

I apologize, but I have exhausted my resources on this issue. I recommend opening a ticket with our Support team so that they can take a closer look at the Zap, dig deeper into the internal logs, and determine the root cause of the issue.

You can reach our Support team at this link: https://zapier.com/app/get-help

In addition, you can share the link to this Community post with them to provide them with the troubleshooting steps we have already taken.

Thank you for your understanding.

Hello there, 

I just wanted to share that I eventually figured out the problem.

The Hubspot form I was trying to submit using Zapier contains different mandatory fields: most of them are Contact-based properties, however one field corresponds to a Company-based property (in my case, value's name is 'name'). 

It seems that Zapier only matches Contact-based properties, i.e. properties related to object "Contact" (FYI, HubSpot accounts include four standard objects: Contacts (0-1), Companies (0-2), Deals (0-3), and Tickets (0-5) - you can check the API documentation here). For that reason, I got that error saying "fields.0-2/name is missing". 

To solve the problem, I just changed the type of property in my Hubspot form (Contact-based instead of Company-based) and created an automation for copying that property from Contact to Company.

I hope this helps whoever may experience the same issue :)

Wow, @AliceM! Way to dig in and find out the reason for the error!

Also really appreciate you sharing the solution with the community - it’s super helpful and know it’s going to help others who may across this.

Thanks again and happy zapping!