From the e-mail:
“Starting today, April 3, 2025, we are removing the X (formerly Twitter) app integration from our offering due to X’s API policy requirements and pricing that prevent us from providing a reasonable integration to our customers. Here are a few critical dates to note:”
What’s the exact reason for this and what alternative services will still be able to use the API? Zapier?
I got this email, too. Would love more details. I have lots of X/Twitter scenarios that I will need to rebuild elsewhere now.
X’s API pricing changes ($200/month for Basic, $42K for Premium) make integration unsustainable. Zapier dropped Twitter; alternatives like Buffer and Hootsuite remain. Make.com is exploring I was already fallen in love with the seamless integration, i think cost effective and more feature is important
Ugh. thanks for update on this. Super frustrating that x/twitter is doing this. sounds like Make.com basically had no choice given these pricing changes from X.
I was using publer before I found make. I think I’ll take another look at it now.
Appreciate this info. That’s interesting – and useful to know – that Zapier dropped Twitter as well.
OK, I don’t think the Buffer module will work anymore in Make.
In order to connect, you need a ClientID and Client Secret.
To get these, you need to register an app in Buffer (much like we did in Twitter).
I don’t believe that is correct. The Buffer app in Make is designed to use Make’s Client ID and Secret.
OPTIONALLY you can choose to use your own, but that’s not a required step - see the help page for details.
Oh wow, you’re right, David! Whew, this is great news then!
Any solution or alternative so far ? X still let dev like me to have free plan with limited post count but it’s all i need. Why stopping the X module ? Any help are welcome 
This is probably still possible with a Custom App feature in Make but it will require everyone who wants to use it to make the structure themselves manually and learn the ins and outs of the X API. In theory it could be possible.
I think Make doing this makes a ton of sense. X is forcing new terms with the price of $42,000 per month (this is a starting price, not a flat fee) so Make would need 4,200 customers at the base level just to break even on a SINGLE platform. Imagine if the different platforms did this! I would rather not even use X/Twitter anymore than to have Make.com charge me more for a single platform that is losing userbase. Plus that $42,000/month is a starting price, it is guaranteed to be much much more for the amount of usage we as Make.com community push through the API as a collective.
The only option for them is to convert the module into a paid addon or remove it. Now with this change every service is making adjustments. I saw one that now requires Paid Account for the ability to use a single X account and if you want more X accounts you have to pay more and more.
Twitter got popular because of their openness of the API and the flexibility of it… now X has ruined all of that and is gutting automation to a huge degree which is only going to push people away from the platform.
Sorry but make doesn’t have to pay. The actual module use personnal API key and credential so make is not having anything to pay at all it you or me that need to pay or have a free plan … that make no sence at all !
I recommend upload-post API the integration with Make it’s so simple
Yeah this doesn’t make sense if the user is connecting via their own X account API