Last updated: August 2026
Make.com can't post to X anymore. Here are your options.
Make disabled the creation of new X (Twitter) scenarios in April 2025, and reconnecting existing ones fails for many users. The practical fix takes about ten minutes: keep your scenario exactly as it is and swap the broken X module for one HTTP module pointed at a posting API. Your triggers, filters, and routing all survive.
OpenTweet is the posting API on the other end: connect your X account once with a normal login, and Make posts through a single authenticated HTTP request. No X developer account, no OAuth signing in Make, no per-post fees, and scheduling included.
What are your options now?
Fix your scenario in three steps
Connect X to OpenTweet and grab an API key
Sign up, connect your X account with a normal login (no developer portal), and create an API key from the dashboard. This is the only new account you need.
Swap the X module for an HTTP module
In your scenario, delete the broken X module and add HTTP > Make a request in its place. Configure it like this, mapping the text field from your earlier modules as usual:
Method: POST
URL: https://opentweet.io/api/v1/posts
Headers: Authorization: Bearer ot_your_api_key
Body type: JSON
{
"text": "Posted from Make via OpenTweet.",
"publish_now": true
}Run it, or schedule instead of posting now
Execute the scenario and the tweet publishes through the official X API. To queue for later, send a timestamp instead of publish_now:
{
"text": "This one goes out at 3pm UTC.",
"scheduled_date": "2026-08-10T15:00:00Z"
}If your scenario only existed to post to X
Skip Make for that job entirely. OpenTweet's built-in connectors cover RSS-to-X, GitHub releases, and Stripe milestones without any workflow tool, and threads, media, and batches of up to 50 posts are supported through the same API.Frequently asked questions
Why can’t Make.com post to X (Twitter) anymore?
Make disabled the creation of new X (Twitter) scenarios in April 2025 after X changed its API terms and pricing. Some legacy scenarios with existing connections kept running, but new X connections cannot be created through the native module, and users report OAuth errors when reconnecting.
How do I keep posting to X from Make now?
Replace the X module with a plain HTTP module. Point it at a posting API such as OpenTweet: one POST request with a Bearer key and a JSON body containing your tweet text. Your triggers, filters, and the rest of the scenario stay exactly as they are; only the final module changes.
Do I need an X developer account for the HTTP-module approach?
Not with OpenTweet. You connect your X account to OpenTweet once with a normal login and create an API key. If you instead call the X API directly from the HTTP module, you need your own X developer app enrolled in pay-per-use billing (about $0.015 per post and $0.20 per post with a link), plus OAuth 1.0a signing, which Make’s HTTP module does not handle well.
Can I schedule tweets from Make, not just post immediately?
Yes. Send a scheduled_date field with an ISO timestamp instead of publish_now and OpenTweet queues the tweet. That also removes the need for Make’s sleep or scheduling gymnastics: fire the scenario whenever the trigger happens and let the posting API handle timing.
Should I switch from Make to something else entirely?
Not necessarily. If your scenarios do more than posting, keep Make and swap in the HTTP module. If the scenario existed only to post to X, such as RSS-to-X, OpenTweet’s built-in connectors can replace it outright, and MCP is the better path if an AI agent is writing your content.
Keep exploring
Post to X from any workflow tool or agent. No X developer account.
OpenTweet vs the X API
Post, schedule, and automate X without a developer account or the $200/mo minimum.
X DM outreach, human-approved
Find and qualify leads, AI-draft DMs, approve each one, and drip-send from your own account via API or MCP.
Post to X without an API
The clean, account-safe way to post to X from your code or an AI agent.
Twitter MCP Server
Give Claude, Cursor, and OpenClaw the ability to post to X. 43 tools included.
Developer docs
Quickstart, API keys, MCP setup, and the REST reference for posting to X from code or an agent.
Cross-posting reference
One call posts to X, Bluesky and LinkedIn. The platforms field, per-network results, and why a network gets skipped.
Social media API for AI agents
Three ways an agent can post to X, Bluesky and LinkedIn, and the trade-offs of each.
LinkedIn MCP server
Post and schedule to a LinkedIn profile from Claude or Cursor through the official LinkedIn API.
XMCP vs OpenTweet
X's official MCP server bills per API call and cannot schedule. Compare it with the flat-fee hosted MCP.
MCP for AI agents
Connect your AI client to X in under two minutes, no X developer account.
Developer API and keys
REST endpoints, one bearer key, and usage tracking. Build on OpenTweet.
OpenTweet for AI agents
The posting layer for autonomous agents and automations that live on X.
Build an AI Twitter persona
Give your AI agent its own X account. Setup, cadence, and the rules that keep it safe.
Best MCP servers for social media
The 2026 ranked list. How the hosted OpenTweet MCP compares with the official X MCP and others.
Cheapest way to post to X via code
Flat fee vs pay-per-use. Why the $0.20 per-link fee flips the math past ~60 posts a month.
Get your Make scenarios posting again
One HTTP module, one API key, ten minutes. No X developer account, no per-post fees.
7-day free trial. Cancel anytime.