I’ve double-checked my setup and have ensured that the redirect URL and credentials match those provided in the Make.com connection settings. However, the error persists.
I’m currently using the free API from Twitter (X), and I’m wondering if this could be the issue. Is it possible that the free tier limits OAuth functionality or access to third-party integrations like Make.com?
I’ve also reviewed other forum posts on similar topics, but there didn’t seem to be any definitive solution.
Has anyone encountered this before? Any tips or workarounds would be greatly appreciated!
Hi aBaxs, welcome to the community. This has something to do with the redirect uri and setup in the developer portal and not with the tier of twitter. I can confirm this because the account i have connected and run on make.com is a free one.
tl;dr: If it doesn’t work initially, check your settings on both sides using the official Make instructions, and just keep trying to save / submit the module settings over and over. Leave it alone for 30, and hour, and come back.
——
I bashed at this exact issue for hours; I tried Client keys, API keys, etc.; for some reason, the YT video link shows him connecting with API Key / API Secret instead of Client Key / Client Secret. That said, by following the instructions here (Make’s official walkthrough) did work. It just took many, many tries and reentries of Client Keys, as the module settings seemed to blank out anytime I tried to test it.
Ultimately, it was just setting it up over and over until, upon hitting OK in the module settings popup window, the auth flow in Make kicks off because it can finally talk to X. My assumption is this is on the X side, not the make side, due to the error message. It seemed to fail when contacting X with module data on save every single time. (Including some screenshots showing what forms the errors took). Also worth noting that, once the auth flow did properly kick off in Make to X, upon logging in to X, I had to refresh the page for X and the “waiting for auth” white Make site so they could “speak” again once authorized in X. Annoying, but easy. You’ll know it worked if your page for X looks like the black page image included with this post.
If it finally works, you should see a popup on your screen asking to auth, then a popup window for Make, and one as well for signing into your X account.
Adding my voice to the chorus saying that I have followed the instructions from the walkthrough over and over and over and each time I get the same error message as everyone else.
You may be right that this is on the X side, not the make side, but threads from last year report similar issue, and that people were not having the same problems when using other no-code tools, e.g. zapier. I haven’t used zapier so I don’t know. But I have to confess it is less than impressive to search through this make.com community board and see customers complaining for YEARS about this issue.
