@Jon - Maybe I’m not following this correctly – But if the endpoint is updated to v2, won’t that also mean that credentials will need to be updated to use Webflow Oauth2 API? And that then means creating a Webflow app? I’m not certain I’m following all the requirements for the new nodes, so I may be wrong here. Thanks! (I’m hoping I’m wrong here.)
HI @Jon just wanted to ask if you were already able to check out on this Issue or i I can assist with analyzing or solving the problem. thank you very much
I’m in the process of upgrading a huuuge n8n workflow to the Webflow API v2 and just ran into this issue. So I’m very much interested in this fix.
So far I’ve solved it by adding a function node that collects all ItemIDs from the previous Webflow create node, and then using a html-node sending a separate API request for publishing said ids (documentation).
That works, sort of.
My main issue that I need to tackle are when deleting items, because that seems to break creating any new items – unless you publish the site manually (or via the API). Which is not ideal because you risk publishing stuff, that are not yet ready (depending on how structured/good your webflow users are when editing – most are not that good).
The built in Webflow node, does not have this publish function anyway, so I guess I will try to go the custom route. Good thing about this, is that I learn a bunch.