Update: I deleted the old node and created a new one, and the new one is “Version 2” which is now able to fetch data from Webflow and send new blog posts.
“Get many” also works.
Thanks for the fix, it seems all good now!
This discussion was opened almost 4 months ago and the definitive solution has still not been provided.
Jon, I can use the Webflow node, however, if I activate the Return All option, no output is returned.
There are several users needing help with serious problems involving Webflow and n8n.
It’s very sad that we don’t have proper support here.
@PauloAFA all authentication issues with the Webflow node have been resolved, when the node was changed I was not aware of the managed credential in our cloud environment. Once I was aware of this I started the verification with Webflow which took longer than expected however that has been resolved for a couple of weeks now.
It looks like I missed the return all issue you reported but I will look into that today / tomorrow, to confirm are you using the v2 node or the v1 node?
Hey @nocode
For the v2 api we only support OAuth, could you create an oauth credential for Webflow and let me know if that works.
I will update the old credential to add a note to mention this.
@PauloAFA the PR is in and can be found below, I have also added a test so that in the future if we make any changes to the node we won’t break this again.
One reviewed this will be merged and available in a future release, Likely 1.71.0 next Wednesday.
v2 node
v1 node
New version n8n@1.71.0 got released which includes the GitHub PR 11934.
Morning,
With release 1.71.0 2 issues have been resolved with the Webflow node.
- The issue reported above with the Return All not working correctly has now been resolved
- The ability to publish / unpublish wasn’t working correctly as the option was being sent as a query string rather than a URL parameter