Trouble Pushing a LinkedIn Lead to a GoTo Webinar Registration

  • 13 July 2023
  • 5 replies

I want to run a lead ad campaign on LinkedIn (In app) that pushes the registration to GoTo Webinar. I was easily able to set up a LinkedIn Event Registration integration with GoTo Webinar. A lead form is different from an event RSVP in several ways, but the most significant is that with a lead form there is no disclaimer to confirm, where the user has to agree to receive emails. For an event RSVP it’s required, making it easy to map the field. On the GoTo Webinar side this is a required field. I’ve tried using X, Y, and 1 characters in the field directly in Zapier, I tried adding a hidden field to the LinkedIn lead form and using X, Y, and 1 as values to substitute for the checkmark, all with no success. It keeps erroring out. It doesn’t specify which field is the problem, but I think my hunch that it is the disclaimer field is correct when I compare it to my other zap that works just fine. What can I put in the disclaimer field that will translate to GoTo Webinar? 

400 Error: Registration request is missing one or more required fields or contains fields longer than maximum input

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

5 replies

Userlevel 7
Badge +14

Hi @B2B Humans 

Good question.

To help us have enough context, please post detailed screenshots with how your Zap steps are configured along with the encountered error, thanks.

Here’s confirmation Zapier pulls a successful lead from LinkedIn


Here is the Disclaimer field (Required) - but there is no field from LinkedIn to map this to


Here is the error:


Userlevel 7
Badge +14

@B2B Humans 

Try entering a static value.

Airtable fields can have these values:

  1. Dynamic variable
  2. Static value
  3. Combo of dynamic variable and static value.

I did, I tried inputting “X”, “Y”, “1”, and this morning “true” and nothing will through 🤷‍♀️

Userlevel 7
Badge +14

@B2B Humans 

Error might be due to a different field.


Check the standardized dropdown values.

The expected value is the smaller gray font value for each option.