What is your goal?
Being able to reply on a certain tweet
What is the problem & what have you tried?
Buffer doesn’t have Watch Tweets Module
Hi,
Since the X (Twitter) modules were removed from Make, this is no longer possible using native modules.
Buffer can’t be used for this use case because it doesn’t have a way to watch tweets or trigger automations based on a specific tweet or mention.
The only viable option now is to use the X API directly via the HTTP module in Make. That means polling tweets (by user, keyword, or tweet ID), keeping track of processed tweet IDs to avoid duplicates, and then sending another request to post a reply.
This approach requires an X developer account, API credentials, and currently a paid plan.
Hope this helps clarify the situation.
Regards, Tony
2 Likes
If it’s not to much to ask can you show me how such workflow would look like?
Hi,
Think of it like this: you’d just run a scenario on a schedule that checks X for the tweet you care about (by ID, user, or search). When it finds it, you save the tweet ID somewhere so you don’t reply twice, and then fire another HTTP call to post the reply.
There’s no native “watch tweet” anymore, so it’s all done by polling the X API directly. That also means you’ll need an X developer account and a paid plan.
Hope this helps.
Regards, Tony
1 Like
The free X developer account actually let you reply 16-17 times a day.
The thing is that when I m trying to set an HTTP module with GET method and trying
to create a OAuth 2.0 connection I get “Something went wrong You weren’t able to give access to the App. Go back and try logging in again.” error.
Maybe, your X app settings are missing the right redirect URI, your X app permissions are too restrictive, or clear your cache.
Then create a new OAuth connection right after troubleshooting it.
If you still get the error after checking those above, please send a screenshot your X app’s Auth settings page (the Callback URLs and Permissions sections) so we can see exactly what’s misconfigured on your end.
1 Like
Yeah still get the error. I rearranged everything used every key I have maybe that was the problem (client id,client secret,api key,api secret ,accesstoken , access secret) nothing worked. I also tried to change native app and set it to web app no luck there either
You can try switching the type of app. Regenerate your client secret and save again. Delete the old connection and create a new one.
1 Like
Still get that. The only thing I noticed is that in the URL of the 2nd image it contains integromat in it. Don’t know if that useful somewhere…
You can also check out this video: https://www.youtube.com/watch?v=PDgKashP_4Q
1 Like
Nothing works 
I tried everything. Regenerated everything tried different callback urls don’t know what else to do 
I guess X is no longer work with make.com unless they bring the modules back. If anyone have successfully connected to X with HTTP module please share your windom with us!