I’m trying to connect Webflow to n8n, but without success. The credential using OAuth2 doesn’t work, and the connection using the API token only works with Webflow’s legacy API, which doesn’t allow creating trigger nodes. I’ve noticed that the app used for OAuth2 in the cloud version, which is what I’m using, may not be requesting the necessary permissions for changes. Can you help me?
Thank you for your response! I updated to the new version; however, the problem persists. The message “Error fetching options from Webflow Trigger” keeps appearing.
@Jon@ria@aya@mariana-na any update? We haven’t been able to update any of our clients’ Webflow related automations and we’re running out of excuses to be honest… we’re spending EUR 1627.20 a year on this n8n plan and the whole purpose is to bring superpowers to our Webflow projects. We’re at a standstill. Please advise.
I’m sorry this issue has been draggring through a few versions - we’re looking into it and planing a fix for as soon as possible. Since we weren’t being able to recreate this it became hard to debugg. Will update you as soon as we have a fix in place.
Thank you for keeping posting details on this!
This should be sorted out later today, the problem here is our Cloud offering has managed credentials so that you don’t need to worry about setting your own so with self hosted this node is currently all good but on Cloud I didn’t realise at the time we need to do the extra update.
I have created the new app on the Webflow side and will update the cloud team shortly, Once this change is in you will need to restart your n8n instances and create a new Webflow credential with Legacy disabled and you should be good to go.
This should be sorted out later today, the problem here is our Cloud offering has managed credentials so that you don’t need to worry about setting your own so with self hosted this node is currently all good but on Cloud I didn’t realise at the time we need to do the extra update.