How to Post to X (Twitter)
from Make.com
Make removed its native X integration in 2025. This guide shows how to get tweeting working again in your scenarios using the OpenTweet app for Make, with no X API key and no developer app.
7-day free trial • No X developer app • Setup in under 10 minutes
Why your Make X scenario stopped working
Make decommissioned the built-in X (Twitter) app in 2025 because of X API pricing and policy. The timeline:
- Apr 3, 2025:New X scenarios blocked. You could no longer add the X module.
- May 30, 2025:Existing X scenarios stopped running and now return an error on every execution.
The fix is to swap the dead X module for an OpenTweet module. Your trigger stays the same; only the posting step changes.
Your old X scenario, rebuilt
Find the scenario you lost on the left and the OpenTweet module that replaces it on the right.
| Old Make X scenario | Rebuild with OpenTweet |
|---|---|
| RSS feed to X (new blog post tweets) | RSS trigger to OpenTweet Create a Tweet |
| Webhook or app event to X | Webhook trigger to OpenTweet Create a Tweet |
| Scheduled tweet from a spreadsheet | Sheets or Airtable to OpenTweet Schedule a Draft, or Batch Schedule Posts |
| New sale or milestone to X | Stripe, Shopify, or Gumroad event to OpenTweet Create a Tweet |
| Thread posted from steps | OpenTweet Create a Thread with your tweets in order |
Step-by-step setup
Install the OpenTweet app for Make
Open the invitation link below. It adds the OpenTweet app to your Make organization, so its modules show up in the scenario editor right away.
Install OpenTweet for MakeGet your OpenTweet API key
Sign in at opentweet.io and connect your X account. Open the API section in the sidebar and click Generate API Key. Copy it now; the key starts with ot_ and is shown only once.
The 7-day free trial includes API access so you can test the full flow.
Rebuild your scenario
Open the scenario whose X module broke. Delete the dead X module and add an OpenTweet module in its place, most often Create a Tweet. Create a connection, paste your API key, and map the text field from your trigger.
Keep your existing trigger as is. The RSS, webhook, Sheets, or store step that fed the old X module feeds OpenTweet exactly the same way.
Run and verify
Run the scenario once. If you posted immediately, the tweet appears on your X account. If you scheduled it or left it as a draft, it shows up in your OpenTweet dashboard. Once it looks right, turn the scenario back on.
Tip: start with drafts
Have the scenario create drafts first and review them in OpenTweet. Once the output looks right, switch the module to publish or schedule for a fully automated flow.
Frequently Asked Questions
Why did my Make X (Twitter) scenario stop working?
Make decommissioned its native X app in 2025. New X scenarios were blocked on April 3, 2025, and existing scenarios stopped running on May 30, 2025, due to X API pricing and policy. Affected scenarios now fail on every run.
How do I post to X from Make now?
Install the OpenTweet app for Make, generate an OpenTweet API key, and replace the old X module with an OpenTweet module. OpenTweet posts to your connected X account, so Make never touches the X API directly.
Do I need an X developer app or API key?
No. You connect X to OpenTweet once. Make authenticates to OpenTweet with your OpenTweet API key. There is no X developer app, OAuth flow, or token refresh to manage.
Can I still automate RSS to X in Make?
Yes. Keep your RSS trigger and connect it to the OpenTweet Create a Tweet module. The same applies to webhooks, Google Sheets, CRMs, and store events.
Can I schedule posts instead of sending them immediately?
Yes. Add a schedule time to post later, use Batch Schedule Posts for many at once, or leave it as a draft to review first. Scheduling and publishing require an active OpenTweet subscription.
Get your Make scenarios posting to X again
Install the OpenTweet app, paste one API key, and swap in the module. Done in under 10 minutes.
Install OpenTweet for Make