New Webflow/Zapier API Update Blues

Design help Webflow integrations
1

I got an email saying everything I’ve built in weblow over the last five years would cease to work unless I updated all my zaps with the new and improved Webflow/Zapier API.

(I’m actually curious how those of you with 100s of webflow zaps got through this without jumping out a window). I tried updating one of my simpler zaps and was immediately met with an inability to successfully test the zap. I also noticed that changing the zap app blows out all the account connection information as well as any configurations that the zap previously had. Which effectively means I will have to rebuild every zap I have that uses webflow.

Getting past the extreme taxfulness of having to basically rebuild every zap I have that uses Webflow, I’m immediately met with the problem that zapier, the finicky kludge-fest that it is, will no longer sense my form test data when the app on the zap is updated to the new webflow version.

I’m using memberstack with my forms so that I can have profiles for my users (because webflow hasn’t seen fit to make this functionality native yet, if ever). I’m working on a hypothesis that the new webflow/zapier api has made it so that if you’re using memberstack, zapier won’t sense the form submission.

Has anyone else encountered this break down in functionality? If so, what workaround did you use?

Thanks.

2

Hey @Luke_Prater,

In case you are using Profile Forms powered by Memberstack attributes, Memberstack will handle this form submission and won’t use up the Webflow form submission limit in any way. This means that you don’t need to rely on listening to Webflow form submissions in your Zap, you could listen to Memberstack event (like member created / updated etc.)

While Webflow API updation, does mean that we need to update the Webflow modules in all Zaps, this won’t affect profile form submission triggers if you have already been handling it via Memberstack (instead of native Webflow form submission).

So even before this API update, Zapier wouldn’t have sensed the Memberstack profile form submission if the trigger was to listen for new Webflow form submission events, you could get the form submission data if you listen to Memberstack events as stated above.

Hope this gives some context to your use-case.