Hi @mike17,

Welcome to the Community.

We sincerely apologize for the issue, but have you tried to update Webflow to its latest version? Try using the newest version and recreate the Zap. Let us know if the issue still persist after updating to the latest version.

Having the same issues as of this morning. I’ve tried everything, but the multiple forms are not showing up as a trigger event.

Hi @ken.a, 

Same - no luck at all. Still missing several forms with Webflow’s “new” API option. 

I’m facing the same issue with forms not showing up after switching to the new Webflow option as per email instruction from Zapier.

I too am not seeing my form even though the site is published and a submission has been made.  It simply does not appear in the list of forms.

I created a new test site and created a form within it without an issue the test form appears but not in the main site.  

I’ve tried loading more, however it refuses to be shown.

Hi friends,

I did some digging into this, and it seems like this issue has been resolved with the new update with the Webflow app. For any users experiencing this issue, please refresh the forms field and reselect the form you would like to trigger.

Hopefully, this helps.

I can’t even get it to show the NEW form I created in WebFlow.  This is after submitting an entry to the form and following every step to a tee.  It refuses to show up in the list for me.

Beyond frustrating.

Hi @mike17, @Cageless Content, @Bala and @xapache! 

Hope you don’t mind but I’ve split your replies out into this topic as the issue for the author of the previous post has been resolved. The new update Ken refers to in his post here was for an issue where the New Form Submission trigger was failing to trigger which was since resolved.

The issues you’re all running into here appear to relate to another bug that’s been reported, where forms are not showing in the Zap editor. So I’ve ensure you’re all on the list of folks being impacted by that issue which will help to increase it’s priority. I can’t make any promises as to when it will be resolved by but we will definitely can notify you by email as soon as Webflow’s developers implement a fix.

In the meantime, I wonder if you might be able to get around this by manually selecting the form. To do that:

1. On the Form field choose the Custom value option.
2. Then type in the ID number for the form into the Form field.

If you do give that a try and it works please let us know, keen to know whether that does the trick in the interim. 

Hi @SamB,

I have the same problem. I wanted to change my zaps to the new Webflow integration. 
However, I can’t find some of my forms between the forms. And the forms which I do find, are all separated by its page on the website. As I have some of the forms on 20+ pages. I would have to make 100+ different zaps. On the old integration, you could just select the form without the selection of a specific page on the website. I hope you mean that you are currently fixing this problem? So, that you can just select a form without a certain page. 

I’ve tried to do it with the custom value, but that didn’t work for me. 
Hopefully you guys are fixing this problem before January 1st, 2025. So, that we can change the integration but will not have these problems of making 100+ Zaps and also some forms are not even findable. 

Please let me know, thanks!

Daan

Same here as @Daan-onesix , 100+ pages in webflow, with 3 forms and a few zaps, I only have limited forms in the selector (if its by page now, it should have all my pages, I see only 7).

Custom value doesn’t work.

Should be fixed ASAP.

Same problem. Would love an email when it is fixed

We have the same issue

Hi @pav5069, @Liddeo and @FS_B,

I’ve added you both to the list of affected users, and we’ll notify you via email once an update is readily available. Thanks.

@JammerS Did you include me too?

This is getting frustrating. The forms, either new or some of the old forms are now showing in the dropdown. Reload does not work. Recreate the connection to webflow does not do anything. I have no ID for the form to put into the form-field explained above..

Please FIX this!

Hi @Daan-onesix and @smult76,

I have added you both to the open bug report. Our engineers are actively working on this issue and we will keep you updated via email once the bug has been fixed.

I appreciate your patience and understanding.

Hi, can you please add me to the open bug report? Thank you 

Hi @danielle1357,

I have added you to the bug report. We will keep you in the loop via email once the bug has been fixed.

I appreciate your patience and understanding.

Same problem here, I’m having big issues with clients because of this.

What a terrible rollout this has been.

When I enter the ID of e.g. 'Form 1', I see the submissions of 'Form 2' in the test records. Please fix this quickly.

Since many users are eagerly waiting for a fix and this has been going on for a few weeks, I am curious about what will happen with the deadline of January 1, 2025, especially considering the holidays in December. It cannot be the case that many automations will stop working on January 1 due to this suboptimal rollout.

Could you provide an answer to this?

Hi ​@mrDico and ​@wnadvr,

I have added you both to the open bug report. We will keep you updated via email once the bug has been fixed. Additionally, our engineers are closely working with Webflow developers to resolve this issue as soon as possible.

I appreciate your patience and understanding.

Thank you! Could you also answer my second question?

still not working - same bug that’s been reported for a month now. Why is Zapier saying this is fixed when it clearly isn’t?

Please add me to the bug report as well. I just submitted a Support Inquiry regarding this very problem, but this is causing me significant problems with a client. I really need this to function properly so I can finish my automations. 

Hi ​@wnadvr, ​@dreweastmead and ​@murphy2232 
 

Completely understand the urgency and concern around that upcoming deadline for Webflow’s v1 API deprecation. Wish I could provide a date for when this will be resolved by but we’re unable to give any sort of estimate as to when this issue will be fixed by Webflow’s developers. But, as Ken mentioned, our engineers are working closly with the Webflow team to help them get this sorted as soon as possible. 

​@dreweastmead and ​@murphy2232 - I’ve ensured that your both on the list so you’ll definitely receive an email notification once it’s fixed. 

Thank you all for bearing with us on this. We really appreciate your patience while we work with the Webflow team to resolve this issue. I’ll be sure to follow up here with any updates to the status of this issue or additional workarounds I come across in the meantime.