I recently received a message from Zapier stating that all of my Zaps connected to Webflow need to be updated by January 1st. Initially, there was an issue getting the new Webflow version authorized, which has been fixed. However, now when I try to update my Zaps connected to Forms, none of my forms are showing up in the list to choose from. Instead, it’s displaying generic form names that I’ve used in the past. I hope that Webflow can resolve this issue before January 1st.
3 Likes
I’m getting this issue as well. The previous integration was using the Form Names to separate out form data in Zapier, however the new version is using some unique identifier which seems to be different instances or versions of the forms (possibly even if they have been deleted). Hopefully the ID does not change if you edit the forms as this will be big problem. Some of my clients have multiple instances of similar looking forms which I used to have one Zap for, but now I have to create multiple zaps.
I can add a little clarification to this issue, which my agency is also experiencing and which is creating difficulties with migrating a number of clients for whom we’re using Zapier with Webflow forms.
It looks like v2 is a bit more “powerful” in one sense than API v1, in that it allows—or requires, more accurately—targeting of a specific instance of a form. If I have the “same” form on multiple pages, then API v2 see that as multiple forms (all with their own unique ID). Even if the form is within a component, multiple instances of a component ultimately means multiple forms. Same goes if I have multiple domains involved… each domain on which a site gets published involves separate form instances.
While I could see the potential utility of this granularity in some use cases, without a way to simply target all forms with the same name using a single Zapier trigger, this could be incredibly—nay, prohibitively—cumbersome. In Zapier I have to have a separate zap for every trigger. If I have a tiny “subscribe” form in my website’s footer, then I may very well have dozens or more of necessary triggers/zaps, which also means additonal cost for a higher Zapier subscription tier. I hope I’m wrong here and that there’s some way to work around this, but I’m thinking this is gonna require a little work on the part of Zapier and/or Webflow to get this worked out.
3 Likes
That’s my thinking as well, although I would have hoped using components would have the same ID which would alleviate some of the issues. A possible stop gap solution might be using Email Parser by Zapier to capture the e-mails and parsing the contents, however I’m not sure how well that handles Textarea form fields which could have newlines in them, otherwise it’ll be time to replace Webflow forms altogether. However, I’ll cross that bridge when it gets closer to depreciation of the V1 API if no solution has been implemented by Webflow or Zapier.
1 Like
Hi Mark,
I’m having the exact same issue, did you manage to resolve this? Is there a way to give forms the same ID number? Because I use a form as a component on every page, this new system is unmanageable…
2 Likes
Thats exactly what I think. The new way of identifying forms it totally fine IF there is also a way to target multiple forms with the same name.
I’m crossing my fingers and hope that Webflow changes this before january 1st.
1 Like
Yes, this appears to be correct, and is incredibly frustrating. It means I’d have to create hundreds of new Zaps, which is ridiculous.
1 Like
FYI I’ve opened a ticket with both Zapier Support and Webflow support with screenshots describing the issue and the problem it represents.
2 Likes
Ok, got a response from Webflow and they are working with Zapier to try and get the old behaviour back. Timeline is uncertain at this stage, so I suggest holding off upgrading to the new integration until that work is completed.
6 Likes
Thats some good news! Lets hope that they can fix it before the deprecation of V1.
Is there any update on this? I’m running into issues with v1 now too 
Update: A new update was released yesterday. Finally, it’s working again!
Hello, I’m just getting around to working on this for my business. I also got the “As a result, you’ll need to take action before then to keep your Webflow Zaps running.” message. Is the only solution to this really to go through every zap using the webflow api and update the app manually? I’ve tried this with just one of my simpler zaps and it’s a logistical nightmare. Changing the app blows out everything including the account connection, all the configuration data, and none of my test data is even showing up anymore. This is a clustermuck.
I’m essentially being asked to rebuild everything I’ve spent years building in zapier. Is this really the solution webflow and zapier have given us? Are all of you also having to go through every webflow zap you’ve created and rebuild/retest everything step by step? Or am I missing something simple?
Zapier customer support’s recommendation is to “duplicate your zap so you can keep track of the steps and re-institute them on your current zap.” This is the cheesiest, hackiest, most workaround monkey business solution I’ve ever seen. I know some of you have 100s of zaps using webflow. Are all of you jumping through these hoops? The amount of man hours it would take to do all this rework boggles my mind.
*EDIT: Also, the previous webflow api 1.11.1 had no problem parsing form submissions from webflow that pass through memberstack. Does the new api break that functionality? Because I am not getting any test data to come through on zapier when trying to update the webflow app on my zaps. Does anyone else use memberstack on their webflow forms? Did you also experience this breakdown in functionality?