Hi @Dadourlou, I haven’t used Twitter’s OAuth2 yet, but could authenticate with OAuth1 without too much trouble. This allowed me to use Twitter’s API v2 as these endpoints support OAuth1 as well:
So if your goal is to simply be able to use the HTTP Request node for API v2 requests you might want to try creating “OAuth1 API” credentials in n8n with these values:
The values for Consumer Key and Consumer Secret would be provided by Twitter of course.
After connecting, v2 API requests like this one work as expected for me:
Example Workflow
As for OAuth2, this might require a closer look and will take some time unless someone else has done this already. But maybe the above already help?