Twitter has restricted the shared n8n.cloud application used here because it has been abused by a user. We’ll most likely change towards letting users create their own Twitter applications (similar to self-hosted n8n instances) in the next week to fix this. You might want to follow the main thread about this for more updates:
Oof - that is very unfortunate. Especially as I had a still functioning Twitter integration working whose workflow accidentally got deleted two days ago. There’s no way to reinstate that instance with its oauth integration somehow, right?
You can reach out via the cloud help center for us to check whether we can recover an earlier database backup, but I don’t think this would restore Twitter functionality unfortunately.
Before Christmas, I could still authenticate with Twitter and search Tweets on n8n.cloud, but this no longer seems to be the case. I haven’t upgraded my n8n.cloud version since or changed anything else, so I reckon Twitter might have tightened the screws even further here.
I’d therefore suggest creating your own application in the Twitter developer portal and using the HTTP Request node for the time being in order to interact with the Twitter API. I’ve quickly tested this on n8n.cloud and it appears to work fine: