Hi @n8n_rookie, as for using a more recent version of n8n perhaps you can use npx n8n@latest instead? This should start the most recent version of n8n:
As for the actual problem, there might be two things at play here. One is that Twitter doesn’t easily grant access to their API v1 anymore (which is the version used by n8n). Until n8n adds support for Twitter’s API v2 you could consider using the generic HTTP Request node to interact with this API. In the past, this approach worked for me and supports man (but not all) API endpoints.
The second problem is that Twitter has started blocking some external applications:
This might affect some clients registered by n8n users as well unfortunately.