Zapier does work still, but the massive jump from $10 a month to $30 is insane.
Make needs to do a better job for their paying customers.
3 Likes
Still no solution! I will move all scenarios to another platform this weekend. any suggestion?
2 Likes
It didn’t occur to me. Thank you so much.
For now it works, we’ll see if it works in the long term or Buffer has limitations.
It is very sad that I’m getting more information from this post than from Make, which insists on blaming Twitter.
2 Likes
Hello, do we have an ETA on this? I am using make to support many customers and they are not happy twitter is down. please advise on ETA.
1 Like
I got an email from support. and it tells us to sign up for a Twitter developer account and use API. it costs $100 per month
Guys
I feel f… I registred paid version of make just for twitter automation.
Now need to pay on top $100/month?
1 Like
I’m assuming Twitter is giving Make issues with getting a new enterprise license due to concerns over the use cases of users. We have a lot of clients getting really upset and I wish Twitter would give them some sort of ETA to deliver to us.
Hi, everyone!
I’m Bruno, one of the team leaders for our Care team.
First of all, we’d like to say that we’re sorry that your recent experience with Make has not been satisfactory and that you that you’ve been having trouble with the Twitter connection.
While we can only imagine how frustrating this has been, we’d like to try and explain our side of things.
TL;DR version:
The core of the matter is that all modules continue to work and you don’t have to pay anything more for now if you follow the steps outlined in our documentation.You can also find a video demonstrating it step-by-step here.
Long Version:
A few days ago, our app was suspended by Twitter without any prior warning, resulting in the failure of all existing connections. Despite our attempts to contact Twitter, we have not received any response regarding the reason for the suspension, so we cannot yet take measures to revert the decision.
Our App is still using API v1.1. While the Twitter team has mentioned the deprecation of some API v1.1 endpoints, there was no mention of sunsetting the API as a whole yet and those deprecated endpoints are not being used by our modules at all.
So far, the release has been rather chaotic with several documentation articles related to the API inexplicably disappearing, but our modules continue to work with v1.1. The only problem we’ve identified so far was the blocking of our OAuth app on Twitter’s end.
As such, you’ll need to register your own app to create a connection to Twitter at the moment, until we can reinstate our OAuth app using v1.1 for now (we’ll continue to use that for now, but are looking at what the future holds).
We’ll continue to work to get our app listed again, but the core of the matter is that all modules continue to work and you don’t have to pay anything more for now if you follow the steps outlined in our documentation. You can also find a video demonstrating it step-by-step here.
When creating your own app, please note you’re directly responsible for adhering to Twitter Automation rules.
I hope this helps bring some clarity to the whole situation!
To maintain the integrity of the community, I am obliged to remove this comment. I want to emphasize that my intention is not to silence your frustration, but rather to ensure that the content posted aligns with the community guidelines. Thanks for understanding.
Dear make.com staff,
I am a software developer. I think Twitter is a terrible place for developers. That’s why I used make.com for the Twitter module only years ago. At that time, the platform was called an integromat.
But instead of buying a developer console account for $100 and connecting it to make.com, I’d rather leave make.com and write my own code. At worst…
If I have to continue with no-code,
I can buy a professional account on Zapier or similar platforms for over $100…
Please find a solution urgently…
Thanks.
1 Like
So, going through the steps listed and getting access through the Twitter Dev Portal, and it seems that we still can’t watch for when new tweets are posted.
Unless I’m doing something incorrect here. Has anyone had any luck in this?
Hi Ali. You don’t need a paid Twitter account.
Most likely, you created an app under a project instead of creating a Standalone app. Please check our documentation and the video again and make sure you’re following those exact steps.
If you’re still having trouble though, please create a support ticket sendingus a video demonstrating the steps you’re taking and we’ll be happy to help you sort things out!
1 Like
Same thing for you Yokie. 
sorry I quoted you instead of replying, but please check the message above. I hope it helps! 
That fixed it. Thank you so much for the help with this whole situation.
2 Likes
Just to be clear, does Make have the intention to be set up with an enterprise license from Twitter and they are not playing ball with Make, or will this likely be the final solution?
2 Likes
Hi Matthew.
We’ve been contacting Twitter since our app got disabled and haven’t been answered so far. We want to first get our app re-enabled and secondly discuss Enterprise options, but I can’t make promises regarding that at the moment.
Please note that these 2 things are completely unrelated: our app uses v1.1 and Enterprise relates to v2.
It’s worth noting that as far as we can tell, most applications including other integration tools are still using v1.1. If they were using v2, I believe you’d need to manually update your connection. Additionally, it’s not currently possible to upload media to Twitter through API v2, or at least that is not publicly documented yet, so likely all requests that allow you to create a Tweet with a picture and so on are still using v1.1
Disclaimer: This last bit includes a bit of speculation of my own, and I could be wrong about it.
1 Like
Okay, understood! But if we’re using our own API credentials from Twitter, it’s still limited now correct?
@Bruno_T, do you mean a register like this?
I applied for this for more than one Twitter account(one of the accounts had 20k organic followers) a few years ago… Here is the result:
“Your Twitter developer account application was not approved.
Thank you for your interest in developer access. We are unable to serve your use case at this time.
Thank you for your interest in building on Twitter.”
Later, you cannot object to this situation or apply again!
Yes, and you can check the limits on Twitter’s end