I’ve had 3 n8n workflows successfully running for the past few months now, through multiple upgrades of n8n but suddenly in the last week I’ve had issues with the Twitter node.
If I include any link in the tweet, even if I don’t use data from another node and just hand write in the URL, the Twitter node will fail citing ERROR: Authorization failed - please check your credentials.
I’ve destroyed my twitter credentials, rebuilt them, recycled all the keys from developer.twitter.com, and reconnected the credentials to the twitter app and there is no change.
I’d say the Twitter API has been updated and requires additional params for link inclusion in a tweet.
Has anyone else had this issue?
Have you found a work around?
Can we get a priority on the Twitter node being reviewed against the Twitter API?
Can you try setting N8N_USE_DEPRECATED_REQUEST_LIB=true this tells n8n to use the older library and in some cases it has worked around the issue until someone has had a chance to check the node.
Thanks so much for looking into this so thoroughly already @hellotimking and @Jon. I’ve filed an internal bug report for this (from testing further just adding a colon : seems to be enough to break the Twitter node) and we’ll of course make sure to add a note to the changelog once this problem has been fixed.
Please accept my sincere apologies for the inconvenience this causes.
I am on version 0.150.0 and encounter the same issue. In fact, I receive a 403 error with and without a link in the body of the tweet. I double-checked my API key credentials and made sure its permissions are set correctly.
I’m very sorry to hear you’re having issues with sending Tweets through n8n. The behaviour might not be related to the problem reported in this thread though. Using Twitter with n8n version 0.150.0 also works fine in principle (this masterpiece of a Tweet was sent out to test this just the other day ).
Would you be able to share a workflow using which your problem can be reproduced and also confirm if you have any environment variables set? Maybe post this is in a new topic to make sure your question doesn’t get overlooked.