Please add me to the bug report.
Thank you @SamB . @wnadvr - I sort of know some people who work at Webflow, and they also understand the urgency. I believe — though I am not certain — that if this is not fixed by 1/1, then they will not force the move to the updated API. They’ll just delay it until this is all resolved.
Thank you @SamB . @wnadvr - I sort of know some people who work at Webflow, and they also understand the urgency. I believe — though I am not certain — that if this is not fixed by 1/1, then they will not force the move to the updated API. They’ll just delay it until this is all resolved.
That would be great and would take away a lot of worries for me and my clients. Can someone from Zapier check/confirm this with Webflow?
Thank you @SamB . @wnadvr - I sort of know some people who work at Webflow, and they also understand the urgency. I believe — though I am not certain — that if this is not fixed by 1/1, then they will not force the move to the updated API. They’ll just delay it until this is all resolved.
That would be great and would take away a lot of worries for me and my clients. Can someone from Zapier check/confirm this with Webflow?
Hey folks! 
@Dormer - I’m so sorry you’re being affected by this as well. I can confirm that you’ve been added you the bug report, so we’ll be in touch via email as soon as it’s resolved. 
Thank you @SamB . @wnadvr - I sort of know some people who work at Webflow, and they also understand the urgency. I believe — though I am not certain — that if this is not fixed by 1/1, then they will not force the move to the updated API. They’ll just delay it until this is all resolved.
That would be great and would take away a lot of worries for me and my clients. Can someone from Zapier check/confirm this with Webflow?
@dreweastmead and @wnadvr - I’ve checked on this and the move to the new API is still set to go ahead in January, but if anything changes on that we’ll let you know. So, as it stands any Zaps using the older version of Webflow’s API will cease to work from January 1st, 2025 when v1 of Webflow’s API will be sunset.
Truly grateful for everyone’s ongoing patience here 🧡 We’ll be sure to share any updates with you all here as soon as we have them.
Hey folks!
@Dormer - I’m so sorry you’re being affected by this as well. I can confirm that you’ve been added you the bug report, so we’ll be in touch via email as soon as it’s resolved.
Thank you @SamB . @wnadvr - I sort of know some people who work at Webflow, and they also understand the urgency. I believe — though I am not certain — that if this is not fixed by 1/1, then they will not force the move to the updated API. They’ll just delay it until this is all resolved.
That would be great and would take away a lot of worries for me and my clients. Can someone from Zapier check/confirm this with Webflow?
@dreweastmead and @wnadvr - I’ve checked on this and the move to the new API is still set to go ahead in January, but if anything changes on that we’ll let you know. So, as it stands any Zaps using the older version of Webflow’s API will cease to work from January 1st, 2025 when v1 of Webflow’s API will be sunset.
Truly grateful for everyone’s ongoing patience here 🧡 We’ll be sure to share any updates with you all here as soon as we have them.
We received the notification 5 weeks ago that we need to update the Zaps to V2. As of today, the Webflow V2 app in Zapier still doesn't work.
We have less than a month left (taking into account the holidays and vacations) to update the Zaps, without any concrete prospect of a functioning Webflow app. Then at least postpone the deadline.
Completely understand how frustrating this must be, @wnadvr! Really wish there was more we could do to delay the sunset of Webflow’s v1 API, but ultimately that’s a decision that would need to be made on Webflow’s end. Our engineers are collaborating closely with Webflow’s team to help them address the issues with their app integration ahead of the deprecation date, but we can’t provide a timeline for when everything will be resolved. I’d encourage you to share your concerns with Webflow’s support team as well—while they’re already aware of these issues, hearing directly from their customers could help prioritize a faster resolution. 
Hi everyone,
I’ve just heard that the Webflow team have resolved the bug, and things should now be back to normal! 
Thank you all so much for your patience and understanding throughout this—I know it hasn’t been an easy wait. Before closing out this thread, it’d be great if someone could test an affected Zap to confirm it’s all working as expected. 
Eager to hear from you on this!
That’s great news @wnadvr! We’re glad to hear that the issue is now resolved!
If you have any other questions, please don’t hesitate to reach out to the Community. We’re always happy to help! 
