Twitter node now surfaces actual API error messages
The X (Twitter) node now displays real error messages from Twitter's API instead of a hardcoded reference to plans that no longer exist.
Users of n8n's X (Twitter) node were encountering an error message telling them they needed "Basic or Pro" API plans. The problem: Twitter eliminated those subscription tiers in favor of a pay-as-you-go model, leaving users confused when their valid API access triggered a misleading error.
This fix replaces the hardcoded message with Twitter's actual API error details. When Twitter's API responds with an access level issue, that specific message now reaches the user. A neutral fallback message covers edge cases where Twitter doesn't provide details.
The change matters because it removes friction for users troubleshooting API access. Instead of debugging a message about non-existent plans, they now get actionable information about what their subscription actually requires.
View Original GitHub Description
Summary
The X (Twitter) node was throwing a hardcoded error message referencing deprecated plan names ("Basic or Pro") when the Twitter API returned an insufficient access level error. Twitter has since moved to a pay-as-you-go model, making the old message misleading.
This change surfaces the detail field from Twitter's own API error response instead, with a neutral fallback message if detail is absent.
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/NODE-4726
fixes #26398
Review / Merge checklist
- PR title and summary are descriptive. (conventions)
- Docs updated or follow-up ticket created. (no docs needed — error message only)
- Tests included. (no existing tests for this error path; no logic change)
- PR Labeled with
release/backport(if the PR is an urgent fix that needs to be backported)