Hi there @dstarr,

Welcome to the Community!

It looks like you have reached out to our Support Team regarding this one and this turned out to be a feature request to trigger by form component instead of the form instance on the page in Webflow.

Hopefully, this helps.

 I agree @dstarr this is not what I was expecting when coming to update my zaps.

@ken.a Is there a reason this would be considered a feature request vs. a bug/breaking change that requires an immediate fix in the new version? This not only affects how forms are being used in Zapier, but also requires multiple Zaps which comes at a development time cost. Please advise, there should be 1 Zap for 1 Form. Webflow doesn’t separate these forms by page, so Zapier should not either. 

I 100% agree @Fyooz Financial  - I’d also consider this a bug not a feature request. It’s been an absolute headache to build an interim solution. 

This being called a feature and not a bug is wild. I find it unfathomable that this could be an intended outcome. This needs to be fixed ASAP as it leaves us with hundreds of sites with essentially broken forms. Also, being forced to use a depreciated API in order to workaround is just unsafe. 

This is an incredibly frustrating update

Hi friends, 

I completely understand the frustration here and I apologize for any convenience this has caused you and I completely agree that this update is not ideal since this would make a simple Zap more difficult. In the meantime, I have added you all to the feature request and you’ll get a notification once this new feature has been reverted back to the previous behavior.

In the meantime we have a workaround regarding this one here:

Workaround

• Use a catch hook for the trigger.

• In the site settings, go to the apps and integrations page, and add a webhook.    

• Select form submission for the trigger type and paste the URL from the catch hook trigger

•   

• Use a filter in the Zap to filter on the Payload Name field, which is the form name.

I appreciate your patience and understanding.

What do you mean “Copied from the trigger”? Where do I copy this url from? Webflow? Zapier? The form? the Zap? 

Thanks, 

Zapier, pls help. This is a catastrophe. Think of all the ‘get-in-touch’ forms at the bottom of every single page on a site. Maintaining updates will be impossible/

I don’t know if this is helpful, but I copy / pasted the form and renamed it and now Zapier sees it. 

Also, it seems dropdown selection fields are a no go. I made one for “State” (for US States), and it just doesn’t work. It won’t submit. Webflow says “please make the required selection for “State”. Even if you choose one. 

I even made it not required and it just bugged out. 

So, maybe don’t use selection fields and make a duplicate of your field and Zapier may see it. 

I realize this doesn’t solve the issue in the thread. But in case someone is having the same issues as me I thought I’d mention it. 

Hi there,

You will copy the Webhook URL from the Webhook by Zapier trigger and paste it on Webflow’s Web URL field. In the meantime, I have added @Primengine-Jakub and @slapbox to the feature request. We will keep you updated via email once the feature has been implemented.

I appreciate your patience and understanding.

Hi, I agree with others, this is a very frustrating bug! Please fix it. 
I have many customers with forms in component and now zapier can’t read from these.

Meanwhile, I create a zap with webhook, but I have many different forms with different fields in my sites.
How can I manage all forms inside the same zap?
I can filter on the Payload Name, but the fields change in the different form.
Zapier ask to me to select only one after the webhook test.

Thanks

Hi @Andrea Brunetti 

Sorry to hear you’re affected by this as well! I’ve added you to the feature request which will help to increase it’s priority and allow us to send you an email notification as soon as it’s been solved. 

To handle multiple different forms within a single Zap you’d want to use Paths instead of a Filter. With paths you can set up different paths for each form and carry out different actions, which different fields selected - be sure to select different test records when setting up each path to ensure that the correct form fields are mapped for each path. You can learn more about paths here: Add branching logic to Zaps with paths. 

That said, if the number of forms exceeds the number of paths that can be added in a Zap then you may want to try the approach outlined in the following guide that explains how to trigger multiple Zaps from a single webhook:

Hope that helps!