Hey everyone, I have generated an API token for my Webflow site, then added this as a credential in n8n. I’m getting a bad request error… even though the key is correct and site published.
To validate the gaslighting in n8n (lol) I created a http request with the header having my api token in, which successfully returned data about our webflow instance.
Does anyone know why my credential isn’t saving. I saw the Auth connection to webflow had legacy on it originally… so avoided using that. That also wasn’t connecting properly.
Maybe they change something on their end or n8n should update this credential setting.
Any way you still can use generic auth → header auth
Paste the Authorization to name
Key to value.
So you can use as normal credential.
1 Like
Thanks darrell_tw that would definitely work. However, I have figured it out. Webflow now only uses the Oauth2 API to connect… which defaults to have a toggle automatically go to legacy. This then doesn’t work and also doesn’t give you the required permissions.
So if legacy is de-selected (unusual that it defaults to this) it all then works in the node.
1 Like
