X (Tweeter) connector is having a problem to connect to my x account

Describe the problem/error/question

when hitting connect my account and i try to connect:

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

{
“errorMessage”: “Unable to sign without access token”,
“errorDetails”: {
“rawErrorMessage”: [
“Unable to sign without access token”
]
},
“n8nDetails”: {
“nodeName”: “Post to X”,
“nodeType”: “n8n-nodes-base.twitter”,
“nodeVersion”: 2,
“resource”: “tweet”,
“operation”: “create”,
“time”: “3/27/2025, 10:59:52 PM”,
“n8nVersion”: “1.83.2 (Cloud)”,
“binaryDataMode”: “filesystem”,
“stackTrace”: [
“NodeApiError: Unable to sign without access token”,
" at ExecuteContext.twitterApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Twitter/V2/GenericFunctions.js:41:15)“,
" at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Twitter/V2/TwitterV2.node.js:172:40)”,
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:681:27)“,
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:913:51”,
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:1246:20"
]
}
}

Information on your n8n setup

Using the latest cloud version on default settings

Hello @hou_roc Welcome to the community :tada:

I suggest regenerating all of these

Then try connecting again. It should work.

Let me know if you still have any problems.

I have put my client id and client secret into the x connector, is “connect my account” necessary as well?
cause from the SS I have put I am having a problem with this part.

also why is the error is about access toekn?
am i not authenticating using oauth2 ? not access and scret?

also, check app permissions like this:

I have done that as well, but still not working.

I have the feeling that’s it could be the twitter ( I have basic plan )
Tried doing the same using multiple simpler connectors, and getting 503 from twitter.
Can anyone else test with their own app?

I think you’re using an outdated workflow here. Actually, there is a ready-to-use X/Twitter node you can use directly.

Also, the API works with the basic plan too.

Please take a look here for a sample workflow Post Media to X/Twitter via API (NEW)

1 Like

Tried your flow and getting Unable to sign without access token here too:

Node type

n8n-nodes-base.twitter

Node version

2 (Latest)

n8n version

1.83.2 (Cloud)

Time

3/28/2025, 1:21:53 AM

Stack trace

NodeApiError: Unable to sign without access token at ExecuteContext.twitterApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Twitter/V2/GenericFunctions.js:41:15) at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Twitter/V2/TwitterV2.node.js:172:40) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:681:27) at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:913:51 at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:1246:20

Well, I’m sure you just need to go step by step.

First:

Second: Regenerate all of these:

Finally: Copy the new generated secrets to n8n and connect.

1 Like

Thank you, looks like I needed to wait a bit until the added callback URL change in dev dashboard take effect.

1 Like

I have been having the same issues. I made sure that i have all the right authentication setting in the X developer portal, Read and write and Direct message Read Posts and profile information, read and post Direct messages. I have re generated all my keys and tokens. I believe that there is an issue with x or n8n. Something has changed. I will post my code below with out the keys and tokens.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.