Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

We’ve been using the linkedin lead gen form zap to send all event regos to our CRM / database (Airtable) for a few months.

 

We run different fortnightly events. Sadly, it seems LinkedIn made a change to the zap trigger so you now have to specify the event that’s triggered. This is really limiting. I’m not going to build a new zap for every event we run.

 

Does anyone know a workaround for having one zap to capture all LinkedIn regos as was done in the past? Or insights on why this was done and if it’ll be reversed?

 

Thanks in advance, T

Hi Tristan,

Great question! I did some research and while I wasn’t able to find a workaround, I did find a feature request for this exact feature. I’ve added you to the feature request so we can let you know as soon as this is added, as well as let our developers know that folks are requesting this feature. I don’t have an ETA on this, but we’ll certainly notify you (and update this thread) if this happens.  

​I wish I could be more helpful here, but please let me know if you have any other questions!

Thanks Clint, it’s nice to know our voice is out there. I sense this was a power grab from LinkedIn, but it would be nice to know this was merely an oversight on their developpers part.

 

I believe the zap trigger loses more than 95% of it’s value without the ability to not specify an event id.

 

T

Terms & Conditions