Make.com is Dropping X - 3 Ways To Fix Before Scenarios FAIL

Key Concepts

• Make.com X (Twitter) Module Removal: Discontinuation of the native X app integration in Make.com due to API policy changes and pricing.
• Buffer: A social media management platform suggested as an alternative to the X module.
• N8N: A workflow automation platform used as an alternative to Make.com for X integration.
• X API: The application programming interface for X (formerly Twitter).
• OAUTH 2.0 with PKCE: A specific authentication protocol required by the X API.
• HTTP Modules: Native modules in Make.com and N8N that allow direct interaction with APIs.
• Webhooks: Automated HTTP requests triggered by events, used for communication between platforms.
• Data Store: A storage location within Make.com for storing variables and credentials.
• Access Tokens & Refresh Tokens: Security credentials used to authenticate API requests.
• API Endpoints: Specific URLs in an API that perform certain actions.

Buffer as an Alternative

• Reason for Recommendation: Make.com suggests Buffer and Hootsuite as alternatives due to X's API changes.
• Pricing Comparison: Buffer offers a free plan with limited features, while Hootsuite's plans are more expensive.
  • Buffer: Free plan available with 3 channels and scheduling 10 posts per month.
  • Hootsuite: Cheapest plan at $99/month, Team plan at $250/month.
• Setup Process: Connecting Buffer to X is straightforward, involving authorizing the app within X.
• Module Integration in Make.com: Replacing X modules with Buffer modules involves adding a "Create a Status Update" module.
• Media Handling: Buffer requires publicly available URLs for images, simplifying media uploads.
• Posting Limits: Buffer's free plan allows scheduling 10 posts per month, but the daily posting limit is 100 posts per 24 hours as per X's API.
• Use Case: Buffer is suitable for posting tweets, images, GIFs, and videos.

Direct X API Integration via HTTP Modules

• Motivation: Buffer doesn't support all X API endpoints, necessitating direct API integration.
• Challenge: X API requires OAUTH 2.0 with PKCE, which Make.com's native OAUTH module doesn't support.
• Deconstructed OAUTH Flow: Breaking down the OAUTH process into separate HTTP requests.
• Scenario 1: Building the Authentication URL:
  • Requires a client ID from the X developer portal.
  • Uses a webhook from a second scenario to handle the OAUTH callback.
  • Generates a unique state verification token for security.
  • Saves client ID, state verification token, and OAUTH header to a data store.
  • Constructs the authentication URL with parameters like response_type, client_id, redirect_uri, scope, state, code_challenge, and code_challenge_method.
• Scenario 2: Generating the Access Token:
  • Triggered by a webhook call after the user authorizes the app on X.
  • Retrieves stored data from the data store using the state verification token.
  • Verifies the state parameter to prevent unauthorized access token generation.
  • Fetches the access token from the X API using the OAUTH code, client ID, client secret, and redirect URI.
  • Saves the access token and refresh token to the data store.
• Security Concerns: Storing the OAUTH header and refresh token in the Make.com data store is not a security best practice.
• Posting Tweets with Access Token:
  • Fetches the access token from the data store.
  • Constructs the JSON payload for the tweet.
  • Posts the tweet to the /2/tweets endpoint with the bearer access token.
• Handling Expired Access Tokens:
  • Implements an error track to refresh the access token if a 401 unauthorized error is encountered.
  • Uses the refresh token to generate a new access token and refresh token.
  • Saves the new tokens to the data store.
• Posting Images:
  • Generates an image using replicate.com.
  • Downloads the image and uploads it to the media-upload endpoint.
  • Parses the response to get the media ID.
  • Creates the tweet body with the tweet text and media ID.
  • Posts the tweet with the media ID.
• Scopes: The media.upload scope is required for uploading media.

N8N as an Alternative

• Reason for Suggestion: N8N natively supports OAUTH 2.0 with PKCE, simplifying X API integration.
• Setup Process: Creating a new credential in N8N involves pasting the client ID and client secret from the X developer platform.
• Module Availability: N8N provides a native X (formerly Twitter) module with access to various resources and operations.
• Webhooks in N8N: Setting up a webhook trigger in N8N involves configuring authentication (e.g., basic auth) and defining the request method (e.g., POST).
• Credential Management: N8N offers a credential management system for storing secrets securely.
• Integration with Make.com: N8N workflows can be triggered from Make.com scenarios using HTTP modules and webhooks.
• Workflow Example: A Make.com scenario triggers an N8N workflow to post a tweet, and N8N responds back to Make.com with a success message.

Conclusion

The video explores three approaches to address the removal of the X module from Make.com. Buffer offers a simple and cost-effective solution for basic posting needs. Direct API integration via HTTP modules in Make.com is possible but complex and raises security concerns. N8N provides a more secure and straightforward alternative due to its native support for OAUTH 2.0 with PKCE, allowing for full control over the X API and seamless integration with Make.com scenarios. The choice depends on the specific requirements, technical expertise, and security considerations of the user.