How to Handle the Discontinued X App in Make.com

The X (formerly Twitter) app has been discontinued in make.com due to changes in the X API and policy. This how-to guide explains what that means for your existing scenarios, what stopped working, and the practical steps you can take to adjust your automations safely.

Why the X (Twitter) App Was Removed from Make.com

The X app was removed because X (formerly Twitter) introduced new API and policy rules that prevent the former integration from working as it did before. As a result, the app is no longer available in the make.com scenario editor for new configurations.

Key points about the removal:

• The X app is no longer listed when you search for it in the app list.
• You cannot add new X modules to fresh or existing scenarios.
• Existing modules already present in a scenario remain visible but have limited behavior.

You can review the original announcement on the official help center at this make.com X integration update page.

What Still Works with Existing X Modules in Make.com

If you already had scenarios containing the X app before its removal, some elements remain visible in your make.com dashboard. However, their functionality is restricted and may be disabled at any time.

Currently:

• You can still see the X modules inside existing scenarios.
• The module configurations you created in the past remain displayed.
• No new authentication or re-connection for X can be configured.

This visibility is mainly to help you understand which scenarios are affected, so that you can manually update, remove, or redesign your workflows.

What No Longer Works in Make.com

Several actions connected to the X app are no longer available or reliable inside make.com. You need to be aware of these limitations so that your automations do not fail silently.

New X App Connections in Make.com

You cannot create new X (formerly Twitter) connections in make.com. Any attempt to add or reauthorize an X connection will fail because the integration is discontinued.

• No new OAuth connections to X can be established.
• Modules that depended on a fresh login cannot be used.

Adding X Modules to New or Existing Scenarios

The X app cannot be added to:

• New scenarios you create today.
• Existing scenarios that never had an X module before.

When editing a scenario, the X app does not appear in the app list, so it is impossible to insert new X-related steps in your make.com workflows.

Scheduling New X-Based Automations

Because you cannot create or extend X-related scenarios, new scheduled automations targeting X are effectively blocked. Any business logic that relied on scheduling tweets, reposts, or searches through the X app must be redesigned with an alternative approach.

How to Identify Affected Scenarios in Make.com

To avoid broken automations, you should locate all scenarios that still contain X modules in your make.com account and mark them for review.

Step-by-step process

1. Open your make.com dashboard and go to the Scenarios section.
2. Use the search bar or manual review to find scenarios that mention X or Twitter in their names or descriptions.
3. Open each scenario and look for modules labeled as X (formerly Twitter).
4. Create a list of all scenarios that still use these modules.

Once you have your list, you can decide which workflows can be deleted, paused, or redesigned with different channels or tools.

How to Safely Update or Remove X Modules in Make.com

Because the X integration is discontinued, the safest approach is to remove or replace it in your make.com scenarios. Follow these steps carefully to avoid losing essential logic or data mappings.

1. Duplicate the Scenario Before Editing

Before changing anything, create a copy of the scenario:

1. In make.com, open the scenario detail page.
2. Use the duplicate function to create a backup copy.
3. Rename the copy, for example “Scenario Name – no X update”.

This ensures you always have the original configuration archived for reference.

2. Document the Existing X Logic

Next, capture the current behavior of the X modules:

• Take screenshots of each X module and its settings.
• Note what triggers the scenario and what data it sends to X.
• Record filters, mappers, and routers that depend on X fields.

Keep these notes, as they will be useful when redesigning your automation in make.com or another platform.

3. Remove or Bypass the X Modules

After documentation, you can update the duplicate scenario:

1. Select each X module in the scenario builder.
2. Delete the module or disconnect it from the scenario flow.
3. Reconnect other modules so that the scenario can still run without X, if possible.

Consider adding temporary placeholders, such as a data store or email notification, to keep track of events that previously went to X.

4. Test the Updated Scenario in Make.com

Once X modules are removed or bypassed:

• Run the scenario in manual mode with sample data.
• Check logs to confirm that there are no errors related to missing X fields.
• Enable the scenario only after multiple successful test runs.

This cautious approach reduces disruption to your existing automations in make.com.

Alternative Approaches for Former X Integrations

Depending on your use case, you may choose different strategies to replace the old X integration in make.com.

Use Other Social or Communication Apps

If your goal was social posting or notifications, consider:

• Posting to other social platforms supported by make.com.
• Sending updates to Slack, email, or chat tools instead of X.
• Saving data to a spreadsheet or database for later manual posting.

Use a Custom API or Middleware

For advanced teams, a custom API or middleware service can be used to rebuild parts of the former integration. However, you must always comply with the latest X platform rules. The discontinued official app in make.com cannot be re-enabled from within your account.

Best Practices for Future Integrations in Make.com

Policy changes from external platforms can impact any automation. To stay safe in make.com:

• Review critical scenarios regularly for app deprecations.
• Subscribe to product updates or newsletters so that you learn about changes early.
• Maintain documentation of your key workflows, including which external APIs they rely on.

If a channel is mission-critical, design backups or alternate notification paths to minimize downtime.

Get Expert Help with Make.com Migration

If you need help redesigning your former X workflows or optimizing other automations in make.com, consider working with experienced consultants. A specialist can audit your scenarios, propose alternatives, and implement scalable, policy-compliant solutions.

You can explore professional automation and integration services at Consultevo, which offers consulting for complex make.com environments and migration planning.

Summary: Key Takeaways for Make.com Users

• The X (formerly Twitter) app integration has been discontinued in make.com due to X API and policy changes.
• You can no longer create new X connections or add new X modules to scenarios.
• Existing X modules remain visible only so you can review and update your automations.
• The recommended approach is to duplicate, document, and then remove or replace X modules.
• Plan alternate channels or custom solutions to handle tasks formerly executed through X.

By following these steps, you can keep your automations stable, compliant, and effective inside make.com, even after the X integration has been removed.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help