Problem using WebFlow OAuth2

[Jon]

Hey there,

This should now be resolved, if you are on Cloud you will need to restart your instance and make a new credential for Webflow making sure to disable the legacy option.

If after doing this you are still seeing an issue let me know.

[PauloAFA]

Still same problem

I can’t click on search to “select sites or workspaces to authorize”. It is blocked.

[Jon]

Is there an option at the top of the page?

[Andy_Masson]

Hey, I am also experiencing the same issue here. I cannot select any of my Workspaces in in the auth window.

Keen t get an update on this as I really need to test this out soon.

[PauloAFA]

There isn’t. Just a menu without interesting options.

[Jon]

Let me look again and see if I am missing something

[PauloAFA]

Updates? @Jon

[PauloAFA]

Two months to solve a simple problem. This is sad.

[adslab360]

I have solved it by self-hosting n8n, deploying app here Login - Webflow and using id and token from there for oauth

[Jon]

Morning,

We are currently waiting on Webflow to verify the application, It is a step I missed when I updated the node as I wasn’t expecting it to be an issue but the process had changed. This shouldn’t be an issue for too much longer.

[BRMLasers]

Hello @Jon,

Could you please post a progression update on how much longer it will take? We have an instance of n8n running, but we haven’t fully migrated from Zapier jet. We still need the WebFlow and the facebook integrations to be working, but those are blocking us from the n8n platform for now.

[Jon]

Hey @BRMLasers,

I chased the Webflow team today on this, they had an issue during their testing which should be resolved so hopefully this will be good to go. If this isn’t sorted in a couple of days we may have to consider removing the managed auth option and let users add their own app instead.

[BRMLasers]

Thanks for the quick feedback!

I didn’t want to sound negative, but the platform is awesome, and I want to use it. Thanks for the extra chase to Webflow.

I can now confirm that the account connection works as expected!
Thanks @Jon!

[Jon]

I was just about to post that, I heard back last night that it is good to go

[onetake.ai]

is this actually working for anyone? Meaning, did anyone manage to actually create a Workflow that connects to WebFlow and does something useful?

Since the “fix”, I can finally connect using OAuth and check a Workspace/Site on the authorization modal. I can see a green “Account connected” label. Great.

But whenever I try using the Webflow node,

• The Site Name or ID fields reads Error fetching options from Webflow with an info-bubble: Issues: There was a problem loading the parameter options from server: "Bad request - please check your parameters"
• The Collections Name field does the same.

If I don’t use Oauth and instead rely on a token by going to the Webflow settings and creating a deprecated v1 token, I can see the Sites and Collections, but I cannot create items either because there are no Fields visible and creating a field returns an error message that Fields are not iterable.

So in the end, it’s been a long time now, and it’s still impossible for me to create a blog post in Webflow from n8n. it’s all the more frustrating because it worked for like 24 hours, weeks ago, and now we’ve just gone one step closer but no cigar.

The docs haven’t been updated either, so I have no idea how to fix this.

Hence my question ; has anyone been able to make a Webflow node work in N8N in the last 3 months? (not just connection, but actually performing an action). If so, how did you do it?

[PauloAFA]

It worked! Thank you very much, jon

[Jon]

Are you self hosting or using Cloud? For self hosted users this has been fine and for cloud users this should now be working but you will need to make sure Legacy is disabled it will then connect and you should be good to go.

[onetake.ai]

Hi Jon, thanks for your reply. I’m using Cloud and I’ve tried all the combinations (with and without Legacy).

With Legacy disabled, it “connects”. But then the node is not able to load CMS information: whenever I try using the Webflow node,

• The Site Name or ID fields reads Error fetching options from Webflow with an info-bubble: Issues: There was a problem loading the parameter options from server: "Bad request - please check your parameters"
• The Collections Name field does the same.

See attached screenshots:

[onetake.ai]

Are you managing to use the Webflow node (not just connect the credentials), @PauloAFA ?
If so, would you mind sharing the use case that worked for you?

[PauloAFA]

@Jon there is another problem

Get many items node isn’t displaying items when return all is on. Could you fix it? Thanks!