I am updating my Zaps for webflow to the new API and all the sudden instead of having one webform to set up, I have 120 different webforms because they are assigned IDs on each page the form is present.
Not sure if this is new functionality available with the API, or something changed in our webflow. Does anyone have guidance on best practice on setting up a form.
For clarification, we have 1 form that is available on multiple pages. The CTA button does not create a new page for the form but pops the forms within the page.
I don’t use Zapier anymore, but from experience, the “integrations” within automation platforms like Zapier and Make take a long time to update. I’m not even certain who is responsible for updates, e.g. Webflow’s devs or Zapier’s devs, or both.
If you’re wanting to fix this urgently, the way I’d approach it is to replace the official Webflow form submission trigger with a generic webhook trigger, and create a webhook via Webflow’s API.
That way you’ll receive the raw request including the form name, and you can filter your automation ( Zap ) so that it only processes the ones you want, rather than trying to filter it on Form ID which seems to have been fragmented by page or form instance.
You can use the form name if it’s available, or put a hidden field in your forms to identify which form you’re dealing with, and filter accordingly.
Same issue here! We have a couple of form components that have instances all across the site, and Zapier now shows a unique ID for each instance. Definitely frustrating, hope a resolution comes soon.
Hey folks - definitely understand the frustration here, and apologies the new v2 update didn’t work out on initial launch. We’re working closely with Zapier’s team to help resolve some new issues (the one of duplicate forms should be resolved) and can share an update soon here. Thanks for your patience
What exactly did you mean by “the duplicate forms should be resolved”?
When I create a new Zap and search for my form (a newsletter form that is embedded in the footer of every page) it still shows me multiple forms with different IDs. Or at least some… it shows 6 forms, but I have the form on about 30 pages. So even if I created a Zap for each instance of the form, I wouldn’t be able to select every form that exists on the site.
And one more question:
Do you guys plan to postpone the deprecation of V1 if the issues with V2 are not fixed until january 1st?
I have already been referred to Zapier by your support department several times for further assistance regarding this issue. On both the Zapier and Webflow forums, there have already been several posts dedicated to this problem.
We are now five weeks past the announcement that the API needs to be updated. The app in Webflow has not been working for five weeks. In less than a month (taking into account the holidays), the Zaps need to be updated; otherwise, the automations will no longer function. This, of course, has huge consequences.
Yesterday, I asked Zapier what they are going to do about the January 1 deadline, given that the V2 app of Webflow is still not usable in Zapier. They indicated that the January 1 deadline still stands.
Various clients are starting to get quite anxious, and I simply cannot reassure them at this point, as we are unable to do anything and the deadline is getting closer and closer.
It cannot be the case that a deadline is set while we are simply not in a position to do what is being asked of us. I sincerely hope that you understand the seriousness and consequences of this situation and can be flexible with the deadline.
@zachplata hello! Januray 1st is around the corner and the issue is still here. Through support, Zapier is pushing the responsibility to you, and you are pushing it back to them. We need a fix soon, managing hundreds of zaps for a few forms present on multiple pages (we went from having 8 forms to 100+) is madness, please collaborate with Zapier and keep us updated on the progress, thank you!
@rickrns hello! Unfortunately, I can’t see any updates that solve the issue on my side, still having hundreds of forms showing up in Zapier for our CMS and navigation forms (we went from having 8 to 100+). Is there a hidden new “feature” in the zaps that makes this problem go away for you?
Could someone at Webflow please inform us about the status of this. The January 1 deadline is approaching very fast, and the V2 app of Webflow is still not usable in Zapier. Will I have to rewrite all my Zaps if I upgrade to V2 and (if I don’t) will my Zaps stop running on January 1st. ???
I had contact with Webflow and they fixed the issue!
If a form exists on multiple pages on the website and you look at the list of forms in Zapier, it will still show the page name next to the form name (see screenshot below). But don’t worry, it will select all instances of the form, regardless of whether it exists on multiple pages.
Thank you for the previous response of the community. I’m still facing some challenges, and I’d appreciate it if you could provide a bit more clarity about the fix of this issue. I followed the advice, but unfortunately, the issue persists on my end.
Currently, I’m in a situation where I need to create hundreds of flows, which could have been consolidated into just ten with V1. I noticed that the update was marked as resolved, but I believe the problem is still present.
My main concern is the potential ripple effects: if I proceed with duplicating these flows now and the issue is fixed later, it might lead to complications such as having multiple Zaps for a single submission. This could result in more inefficiencies, both in terms of time and workflow management.
For now, I plan to move forward with duplicating the flows since I only have a few hundred to handle. However, I can only imagine the challenges faced by teams managing websites with thousands of pages. I really admire the effort and courage it takes to address such complex issues, and I hope this feedback can contribute to improving the experience for everyone.
Thank you for your support and hard work. Looking forward to hearing your thoughts on this!
@DevFlow75 Are these forms “duplicate forms” or forms within components? From what I can tell, I believe the “fix” addresses the issue if the form is a component added to multiple pages. However, if you have duplicated forms, this might not resolve the issue for you.
As an alternative solution, if the form field names are the same and in the same order across all the forms generating the same formatted e-mail from webflow, you could possibly setup a zap using Email Parser Email Parser by Zapier
Hi. With a more deepened research, it seems to work on some of my forms, but not on others. Maybe there is a problem of implementation on my side around my forms.
So I’ll say that in the end the issue seems to be closed.
Hey folks - my sincere apologies for the lack of follow-up here. Webflow has worked (and continues to work) in close partnership with Zapier to ensure major bugs reported on this thread, as well as those reported on both support teams from Webflow/Zapier were addressed. Some major updates were pushed towards the end of the year which should have resolved a large number of issues, such as:
Consolidating forms that were in components, and instanced on multiple pages
Grabbing all form submissions from all domains on a Site during the test form submission step
Fixing some bugs as it related to form submissions not triggering the Zap as expected
One important note made by @Schuschi_Eyes above is that you may see multiple of the same Form (but different pages). If these forms are in a component and instanced on multiple pages, feel free to configure one, test that form submissions come through as expected on the Test step, and leave it to Zapier to ensure all Forms on the other pages will trigger the Zap.
As most of you and/or clients may have noticed, we moved the Jan 01 date out. The final API v1 deprecation date will be March 31 (see new dates here), which means older configured Zaps will still continue working until that date. However, we strongly encourage you to start migrating to the new Webflow integration in Zapier now and report any issues to Zapier support, and turn off Zaps using the old Webflow integration.
Thank you all in advance for taking the time to update the Zapier integrations
