Hi there ​@Daniel van Pel,

Welcome to the Community!

Before we dig deeper into this, would you mind sharing a detailed screenshot of how your Zap is configured? Also, please share a screenshot of the Webflow step that shows all of its fields.

Please don't include personal information in the screenshot, or be sure blur out any personal information.

Thanks!

Thanks for the reaction, I’ll show you the way i had to set it up to get it to work. I split the form into 2 separate zaps and that helps.

I can show you how we used to do this with v1 api version. Here it simply triggered the zap no matter where the form was placed on the site. This is one of our other sites that i still have to move to the v2 api.

My main concern is with forms like the subscribe to newsletter which are present on all pages of our site. So meaning i will have to create hundreds of zaps to make it work.

Just let me know if I should be setting things up differently. if so, could you tell me how please ;)

Hi ​@Daniel van Pel,

Welcome to the Community. 

You can handle multiple forms with a single Zap even after switching to the v2 API, provided the forms share the same structure. Set the trigger to the form submission event, use a 'Filter by Zapier' step to differentiate forms by ID or name, and configure the action accordingly. If forms have different structures, you may need separate Zaps for each type, but only for some individual forms.

I hope this helps. If you have any other questions or need further clarification, feel free to ask.

Hi ​@JammerS,

This works, but I’m curious to understand why. Intuitively, it feels counterintuitive that adding a filter (which applies a condition to decide whether to continue) would let more items through than not having the filter at all.

The filter is applied after the Webflow step. Could you help clarify why this behavior occurs?

The filter is simply doing a check to see wether the form name is “Nieuwsbrief”

Thanks in advance!

Hi there, ​@Daniel van Pel!

Hmm, it appears the previous fields that New Form Submission trigger had available were renamed. So I’d recommend clicking the Remove extra fields button to get those old fields removed as these ‘extra’ fields can sometimes cause issues.
 

This works, but I’m curious to understand why. Intuitively, it feels counterintuitive that adding a filter (which applies a condition to decide whether to continue) would let more items through than not having the filter at all.

The filter is applied after the Webflow step. Could you help clarify why this behavior occurs?

Adding a filter shouldn’t result in more items through than not having a filter at all. If it’s letting through more items than it should then it could be that there’s an issue with the set up of the filter. You mentioned that set up to check to see whether the form name is “Nieuwsbrief”—is it supposed to continue if the form doesn’t have that name, or if it does? If you can share a quick screenshot of the current set up of the filter that will help me to better see what might be causing it to allow the wrong items through. 

In your initial message you mentioned an issue you’re having around not being able to trigger on forms across multiple pages any more:

I’m encountering an issue with form submissions when connecting forms to Zapier. Specifically, I’m receiving submissions from all collection pages as expected, but when the same form is placed on a static page, it no longer triggers the Zap.

The older version of the trigger used to be able to trigger on the form instance but was since changed to allow form instances on individual pages to be selected. There’s a feature request open to have the old functionality restored so that it’s possible to trigger from the form component that’s across multiple pages, which was discussed previously over here:

I’ve gone ahead and added your vote to that feature request. While I can’t guarantee if or when this will be added, we’ll be sure to notify you via email once becomes available. That said, there was a workaround mentioned on that other Community topic that you might want to try. I’ll reshare it here in case it’s useful:

If you run into any issues on that or have any further questions in the meantime do let us know!

The removing of the extra fields seems to do the trick, that makes it functional even without the filter afterwards. That really cleans things up as the filter steps are not necessary anymore. This also includes the components. I read in some other articles (can’t find them quickly now though) that the issue was already fixed. It just didn’t seem to work for me.

The filter was indeed checking if it exactly matched. I’ve included a screenshot below. Maybe it helps you guys to understand why using the filter was creating more data than without.

That’s such great news, ​@Daniel van Pel! I’m so glad to hear removing those extra fields helped to get it working correctly. 

Thanks for sending over that screenshot of the filter set up—it’s much appreciated! The filter looks like it’s been correctly set up to only let form submissions through for forms with a display name of Nieuwsbrief. I wonder if it was triggering for another form called Nieuwsbrief instead of only the form called (Contact) Neiuwsbrief, due to the extra fields that were there previously:

If so, then that could well explain why it incorrectly triggered for those form submissions and let them pass the filter. With the trigger working correctly now, as you say, you won’t need that filter step so you shouldn’t experience this issue going forward.

That said, do let us know if anything changes on that front or you run into any further issues. In the meantime, happy Zapping!

Before removing those Extra Fields it would only trigger on specifically the (Contact) Nieuwsbrief meaning the Nieuwsbrief form on the Contact page. After adding the filter and specifically checking on the name “Nieuwsbrief” I was getting all submissions of the forms on the website with name “Nieuwsbrief” including the one on the Contact page. Which seems odd since adding a filter after the trigger causes more form submissions to trigger in the trigger before the filter.

But removing Extra Fields seems to have fixed all problems and made it possible without the filter, after removing the filter everything works how you would expect. thanks for the help!!

If you have any more questions, or can help you to investigate further, im happy to help

That’s very strange, ​@Daniel van Pel. Adding the filter as an action step shouldn’t have had any affect on when a Zap will trigger as the filter wouldn’t run until after the Zap triggers. I’m unable to dig into any of the system logs for your Zaps to confirm what caused that to happen so you might want to reach out to our support team to have this investigated it further. 

Please do keep us updated on how it goes with the Support team—curious to know what the cause was!