X account credential issue. Getting the same error message and feel like I’ve tried everything

Questions
1

Describe the problem/error/question

My X create tweet node refuses to post.

Screenshot 2025-11-04 at 18.36.29
Screenshot 2025-11-04 at 18.36.29676×222 14.2 KB

I’ve created new X credentials in n8n and even created a new app in the X developer portal but still doesn’t seem to be working.

What’s maddening is that this whole thing did work at one point. One day the X node just stopped working and now it just says “forbidden - perhaps check your credentials? “ every time.

There doesn’t seem to be any issue with connecting my X account. When I create a new credential and add my secret key and client ID, n8n connects to my X account just fine.

I’ve definately enabled posting on the X developer platform too.

What is the error message (if any)?

“forbidden - perhaps check your credentials? “

Please share your workflow

Share the output returned by the last node

There is no output because it wont execute.

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
1 Like
2

I’ve seen this exact issue before! The “Forbidden” error usually means your X app permissions aren’t set correctly.

Here’s what I think happened - your app worked fine initially, but X might have reset permissions or you changed something. The tricky part is that even if you enable “Read and Write” permissions in X Developer Portal, the OLD API keys won’t get the new permissions.

Try this:

  1. Go to X Developer Portal
  2. Check your app permissions are set to “Read and Write” (not just Read)
  3. After confirming permissions, REGENERATE your API Key and Secret
  4. Use the NEW keys in n8n credentials

The old keys are tied to the old permissions, so just enabling posting won’t fix it - you need fresh keys.

Also make sure you’re using OAuth 2.0 credentials in n8n (not OAuth 1.0a).

X’s docs: OAuth 2.0 Authorization Code Flow with PKCE - X

Let me know if regenerating the keys fixes it!