Zapier X Integration Status April 2026

The Zapier and X (formerly Twitter) integration has had a turbulent history. Removed in August 2023 after X changed its API policies and pricing, restored in February 2026 with a bring-your-own-key (BYOK) model, briefly deprecated again in early March 2026, and then restored once more. As of April 2026, the integration is live and functional, but it works differently than it did before the original removal.

This post covers the current status, what is available, how to set it up, what it costs, and what alternatives exist if the BYOK requirement does not work for your use case.

Timeline of Changes

| Date | Event | Impact | |---|---|---| | August 31, 2023 | Zapier removes X integration entirely | All X triggers and actions stop working | | 2023 - 2025 | No native X integration on Zapier | Users rely on workarounds (Buffer, Hootsuite, direct API) | | February 6, 2026 | X launches pay-per-use API pricing | New default for developers, replaces free tier | | February 16, 2026 | Zapier restores X integration with BYOK model | Users can connect X again using their own developer app | | March 4, 2026 | Brief deprecation notice due to X API policy dispute | Some Zaps temporarily disrupted | | April 2026 | Integration live and stable with BYOK requirement | Current state, covered in this post |

Current Status: Working with BYOK

The X integration on Zapier is operational in April 2026. The critical difference from the pre-2023 version: you must bring your own X Developer App credentials. Zapier no longer maintains a shared OAuth application for X.

This means you need:

1. An X Developer Account (apply at developer.x.com)
2. A project and app created in the X Developer Portal
3. OAuth 2.0 Client ID and Client Secret from your app
4. An active X API plan (pay-per-use or legacy tier)

Once you have those credentials, you enter them in Zapier when connecting the X app to your account.

How the BYOK Connection Flow Works

Available Triggers and Actions

Here is what Zapier currently supports for X as of April 2026.

Triggers (start a Zap when something happens on X)

| Trigger | Description | API Tier Required | |---|---|---| | New Mention | Fires when someone mentions your account | Pay-per-use or Basic+ | | New Post from Query | Fires when a new post matches a search query | Pay-per-use or Basic+ | | New Post from User | Fires when a specific user publishes a post | Pay-per-use or Basic+ |

Actions (do something on X from a Zap)

| Action | Description | API Tier Required | |---|---|---| | Create Post | Publish a new post to X | Pay-per-use or Basic+ | | Follow User | Follow a specified account | Pay-per-use or Basic+ | | Like Post | Like a specific post | Pay-per-use or Basic+ | | Repost | Repost (retweet) a post | Pay-per-use or Basic+ | | API Request (Beta) | Make a custom request to any X API v2 endpoint | Pay-per-use or Basic+ |

The API Request action is the most flexible. If Zapier does not have a built-in action for what you need (for example, creating a list, uploading media separately, or managing bookmarks), you can construct a raw API call.

X API Pricing in April 2026

The BYOK model means you pay X directly for API usage. Here is the pricing landscape.

| Tier | Monthly Cost | Post Reads | Post Writes | Notes | |---|---|---|---|---| | Pay-per-use | Variable (credit-based) | Up to 2M/month | Included in credits | Default for new developers, $10 starter voucher | | Basic (legacy) | $100/month | 10,000 posts | 1,667 posts | Still available for existing subscribers | | Pro (legacy) | $5,000/month | 1,000,000 posts | 300,000 posts | Still available for existing subscribers | | Enterprise | $42,000+/month | Custom | Custom | Required above 2M reads/month |

If you are only using Zapier to post a few times per day and monitor mentions, the pay-per-use tier is the most cost-effective option. The $10 starter voucher that X provides to new developer accounts covers a reasonable amount of usage for low-volume automation.

Step-by-Step Setup Guide

1. Create an X Developer App

Go to developer.x.com, sign in with your X account, and create a new project. Inside the project, create an app. Under the app settings, enable OAuth 2.0 and set the redirect URL to https://nla.zapier.com/oauth/callback/. Copy your Client ID and Client Secret.

2. Connect X in Zapier

In any Zap, add an X (Twitter) step. When prompted to connect your account, paste your Client ID and Client Secret. Zapier will redirect you to X to authorize the connection. After authorizing, the connection is saved to your Zapier account.

3. Configure Your Zap

Set up your trigger or action as normal. Test the step to confirm the connection works. If the test fails with a 401 error, double-check that your Client Secret is correct and that your X Developer App has the right permissions enabled (read, write, or both depending on your use case).

4. Monitor API Usage

Check your X Developer Portal dashboard regularly. Zapier triggers poll on an interval, and each poll counts as an API request. If you are on pay-per-use, keep an eye on credit consumption.

Common Issues and Fixes

| Problem | Likely Cause | Fix | |---|---|---| | 401 Unauthorized | Wrong Client Secret or expired token | Reconnect the X account in Zapier with fresh credentials | | 403 Forbidden | App permissions too restrictive | In X Developer Portal, enable read+write under app permissions | | Rate limit errors (429) | Too many Zaps polling simultaneously | Reduce polling frequency or consolidate triggers | | Zap turns off unexpectedly | X API returned repeated errors | Check X Developer Portal for app status, reauthorize if needed | | Posts not appearing | X API eventual consistency delay | Wait 1 to 2 minutes; X search index has a slight lag |

Alternatives if BYOK Does Not Work for You

Not everyone wants to manage their own X Developer App. Here are alternatives that handle the API relationship for you.

Buffer integrates with Zapier and handles X posting through its own API connection. You connect Buffer to Zapier, then Buffer posts to X on your behalf. No developer app needed. The free tier supports up to 3 channels with 10 scheduled posts per channel.

Hootsuite works similarly. Connect Hootsuite to Zapier, and Hootsuite manages the X API connection. The entry-level plan starts at $99/month for 10 social accounts.

Make (formerly Integrobot) decommissioned its own X integration in early 2026, so it is not a viable alternative for direct X automation.

Direct API integration is an option if you are comfortable writing code. The X API v2 with OAuth 2.0 PKCE is well documented, and you can build custom automation without any intermediary platform. This is the most flexible but also the most maintenance-heavy approach.

Desktop AI agents like Fazm can automate X interactions through the actual interface rather than the API, which means no developer app, no API costs, and no risk of API policy changes breaking your workflow. The tradeoff is that UI-based automation is slower per action than API calls.

What to Expect Going Forward

The Zapier X integration has been unstable since 2023, and the BYOK model shifts the risk to users. If X changes its API terms again, your Zaps will break until you adjust your developer app settings. Zapier has less leverage to maintain the integration because they are no longer the API consumer; you are.

That said, the pay-per-use pricing model X introduced in February 2026 is more accessible than the old $100/month Basic tier for low-volume users. The $10 starter credit is enough to test whether a Zapier-plus-X workflow meets your needs before committing to ongoing costs.

For business-critical automation that depends on X, consider running your workflows through two paths: an API-based approach for speed and a UI-based fallback through a tool like Fazm for resilience. If one path breaks, the other keeps working.