I want to create a Webflow form submissions to Telegram bot integration. However, when I add a Webflow trigger (form submission), it just doesn’t work. I did everything in the n8n docs down to the T regarding Webflow credentials, but I cannot load a website(s).
What is the error message (if any)?
I’ve also tried installing the app in Webflow directly, but it didn’t work either.
Hi @Georgy, I think this issue is caused by the fact that we’re still using the legacy API which is being fixed soon. Once we update the API, this should be fixed.
When do you expect to launch the update? I wanted to create a solution for one of my clients, but now I’m kinda forced to go Zapier/Make route, though I would much preferred to use my beloved n8n.
I am in the middle of updating the Webflow node to use the newer API at the moment we only support the legacy / v1 api. I want to have this finished for the release this week but it is possible it may slip to next week depending on how much I can get done today.
Hi @Jon - I see that the Webflow team will stop issuing legacy v1 API tokens in about two weeks (Aug 15, 2024), which I believe will entirely break the Webflow node for all new n8n users (and limit everyone else to using pre-existing Webflow v1 credentials.) Wanted to re-up this thread given the approaching deadline.
This is going through review now, For this first change it is mostly an exact copy of the v1 Webflow node. I also need to think about the trigger node still as well.
@Jon I updated to v1.54.4, but Webflow still isn’t working. I ran into a number of different issues that I wanted to share:
New V2 Webflow API tokens are not validating from n8n
I created a V2 Webflow API Token with some read-only permissions, but when I tried to set up a new credential in n8n (type: “Webflow API”) and pasted in the API Key into the “Access Token” and click Save, I see error message: Couldn’t connect with these settings. (Bad Request). Note: I tested this API Key on the command line and it works fine.
Existing Webflow credentials are not populating in Webflow nodes
I created a new workflow and added a Webflow trigger to it, and noticed that my existing credentials (both v1 and v2) didn’t pre-populate the “Credentials to connect with” pulldown menu. My only option was to create a new credential.
Inline Webflow credential creation uses Oauth2, not Access Tokens
When I clicked through “Create new credential” from a new Webflow trigger node, the new credential was of type “Webflow OAuth2 API” (I had expected “Webflow API”.) Is the updated Webflow node now only compatible with OAuth2 API keys? (The documentation still includes API access tokens.)
n8n documentation should point to V2 Webflow docs
I tried to follow the n8n instructions to set up an OAuth 2.0 app, but found that all links from Webflow credentials | n8n Docs pointed to V1 Webflow docs. This should probably be updated from OAuth 2.0 to Create an App
I didn’t test the update yet, but, dang, it sounds really upsetting that it doesn’t work. Hopefully n8n devs will resolve the issue soon, Webflow and n8n is a great combo!
The update Webflow node currently only uses the OAuth2 authentication option and doesn’t support using access tokens.
A future update may add support for these again, once setting up the oauth app in Webflow though the node will work but it looks like I did miss the docs update to add the information about the oauth.
I wouldn’t expect v1 tokens to be usable with the v2 Webflow api so when we do add tokens you would still need to create a new credential as it doesn’t look like api tokens can be used between api versions.
This is helpful. It wasn’t clear to me that “Webflow API” is necessarily only for v1 tokens while “Webflow Oauth2 API” was v2. I’ll try again using the Oauth2 API.
