I have an issue with Twitter API V2.
First of all the documentation is a bit outdated, I think Twitter has made some new changes in their developer portal
Also I still have many problems using a simple node of twitter
After credential setup, I am not able to test even with a simple tweet creation.
My error message is
You currently have Essential access which includes access to Twitter API v2 endpoints only. If you need access to this endpoint, you’ll need to apply for Elevated access via the Developer Portal. You can learn more here: https://developer.twitter.com/en/docs/twitter-api/getting-started/about-twitter-api#v2-access-leve
NodeApiError: Forbidden - perhaps check your credentials?
at Object.twitterApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Twitter/GenericFunctions.js:26:15)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Twitter/Twitter.node.js:153:40)
at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:652:28)
Could this be a bug due to some twitter API changes ?
Hey @Jon !
Aouch I see, ok it makes sense
Any plan to support v2 soon ? Elevated access jumps straight to 40$/months, which is a bit too much for my use case.
Any other alternative you can suggest to bypass this node in order to post tweets. The mode itself come in the middle of a larger workflow, any clever bypassing alternative will be more than welcome
We do plan to update the node but we also want to introduce PKCE support at the same time which is a fairly large change and may involve swapping out the oauth package we use which will need a lot of testing.
As a workaround you could try using the HTTP Request node to send to the v2 api but I have not tried this yet.