> Content index: https://reachmore.co/blogs/llms.txt > Canonical page: https://reachmore.co/blogs/n8n-twitter --- title: n8n Twitter (X) Node: Operations, Costs and Limits description: The n8n Twitter node has 8 operations and no trigger. Here's what each does on X's pay-per-use API, what 100 runs cost, and where the API stops you. keywords: n8n twitter, n8n x node, n8n twitter automation, twitter automation workflow, x api pay per use published: 2026-09-27 updated: 2026-09-27 url: https://reachmore.co/blogs/n8n-twitter word_count: 2048 --- # n8n Twitter Node: What X's API Still Lets It Do > The n8n Twitter node has 8 operations and no trigger. Here's what each does on X's pay-per-use API, what 100 runs cost, and where the API stops you. Canonical: https://reachmore.co/blogs/n8n-twitter Published: 2026-09-27 ## Related Pages - [Twitter Automation: 9 Workflows X's API Actually Allows](https://reachmore.co/blogs/twitter-automation-workflows) - [X API Free Tier: What Replaced It in 2026](https://reachmore.co/blogs/x-api-free-tier) - [How to Post Links on X in 2026 Without Killing Reach](https://reachmore.co/blogs/how-to-post-links-on-x-2026) - [Twitter API Rate Limits: What Actually Breaks in 2026](https://reachmore.co/blogs/twitter-api-rate-limits) - [Twitter API Python: What Still Works in 2026](https://reachmore.co/blogs/twitter-api-python) - [Twitter MCP Server: Run Your X Account From Claude](https://reachmore.co/blogs/twitter-mcp-server) - [Social Media Scheduler API: What Breaks at Scale](https://reachmore.co/blogs/social-media-scheduler-api) ![A black and white flowchart with text boxes and arrows on a wall](https://images.unsplash.com/photo-1571666521805-f5e8423aba9d?crop=entropy&cs=tinysrgb&fit=max&fm=jpg&ixid=M3w4OTM1MDJ8MHwxfHNlYXJjaHwyfHx3b3JrZmxvdyUyMGF1dG9tYXRpb24lMjBub2RlcyUyMGRpYWdyYW0lMjBzY3JlZW58ZW58MHwwfHx8MTc5MDQ4MDI0Nnww&ixlib=rb-4.1.0&q=80&w=1080) *Photo by [Hanna Morris](https://unsplash.com/@hcmorr?utm_source=quillly&utm_medium=referral) on [Unsplash](https://unsplash.com?utm_source=quillly&utm_medium=referral)* You wire up the n8n Twitter node, point it at a Google Sheet of posts, and the first run works. Then you try to reply to a big account's post and X refuses. Then you look for a "new mention" trigger and there isn't one. Then the first invoice from X arrives. **The short answer:** n8n's X (formerly Twitter) node gives you eight operations — create, delete, like, retweet and search tweets, send a DM, add a user to a list, and look up a user. It has no trigger node, it runs on your own X developer app, and every call it makes is billed by X under the pay-per-use model that replaced the old tiers in February 2026. That's enough to build useful things. It's also a lot less than most n8n twitter automation tutorials imply. This guide reads the node from its [source code on GitHub](https://github.com/n8n-io/n8n/tree/master/packages/nodes-base/nodes/Twitter), prices each operation against X's own table, and marks the line where the API stops you — whichever tool you use. ## What does the n8n Twitter node actually do? The current node (version 2) exposes four resources and eight operations. This list is taken straight from the node's description files, not from a marketing page: | Resource | Operation | What it calls on X | | --- | --- | --- | | Tweet | Create | Posts a tweet; optional quote or reply-to ID | | Tweet | Delete | Deletes one of your tweets | | Tweet | Like | Likes a tweet as you | | Tweet | Retweet | Retweets a tweet as you | | Tweet | Search | Recent search — tweets from the last seven days | | Direct Message | Create | Sends a DM to a user | | List | Add Member | Adds a user to one of your lists | | User | Get | Looks up a user by username, ID, or "me" | A few details matter more than they look: - **Search only covers seven days.** It's X's recent-search endpoint. No full-archive search from this node. - **Media is thin.** The Create operation accepts a media ID, but there's no upload operation, so you upload through an HTTP Request node first. The node's own UI warns that location and attachments are limited by the v2 API. - **Authentication is OAuth 2.0 with PKCE** against your own developer app. You bring the app, the keys and the billing account. ![n8n documentation page for the X (formerly Twitter) node, listing its tweet, direct message, list and user operations](https://quillly.com/serve/v1/019c4288-991a-773f-8671-f957d77800e3/images/857fd9fe2892d762440d46b177e61e5f17999b8a.webp) *The official [n8n X node documentation](https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.twitter/). Captured September 2026.* ## Is there an n8n Twitter trigger? No. n8n ships an X action node only. To react to mentions, you poll: a Schedule Trigger, an HTTP Request that reads your mentions, and a dedupe step. There's no X trigger node in n8n's codebase — only the action node. If you want a workflow to start "when someone mentions me," you build the trigger yourself: a Schedule Trigger that fires every few minutes, then an HTTP Request node calling X's mentions endpoint with your credential, then a filter that drops mentions you've already seen. ![Flowchart of a polling pattern in n8n: a schedule trigger fires, an HTTP request reads new mentions from the X API, a dedupe step removes mentions already handled, an IF node checks whether any are new, and only new mentions continue to a draft and a reply step](https://quillly.com/serve/v1/019c4288-991a-773f-8671-f957d77800e3/images/b12a2f6374fa72c2d542cc717820cc4a637897ef.webp) Two costs hide in that diagram. Every mention the poll returns is a post read that X bills. And the dedupe step is on you: if you store `since_id` badly, a crashed run can re-read the same mentions and reply twice. Double replies are the quiet way home-built automation embarrasses an account. This is the most common reason people outgrow a DIY setup. For more patterns that fit inside the rules, see [the X automation workflows the API actually allows](https://reachmore.co/blogs/twitter-automation-workflows). ## Why n8n can't reply to strangers on X The Create operation has an "in reply to" field, and it's tempting to wire a search step into it. The call will fail on most posts, and n8n has nothing to do with it. Since X's February 2026 changes, the API only accepts a reply when the post's author **summoned** you — they @-mentioned or quoted your account. A reply to an arbitrary stranger's post has no API path at any spend level. That's covered in depth in our breakdown of [what replaced the X API free tier](https://reachmore.co/blogs/x-api-free-tier). So the classic "search keyword → reply with AI" n8n template is dead on arrival through the official API. The only way to make it "work" is to drive the X website with a headless browser, which is exactly what X's automation rules exist to catch, and the enforcement lands on your account rather than the template's author. What still works through the node: - Replying to people who mentioned or quoted you - Posting, quoting and deleting your own tweets - Likes and retweets, at a price (see below) - DMs — but X's inbox settings and spam rules make cold DMs a bad idea regardless of the tool ![Two comparison cards showing what an n8n X workflow can do through the official API, such as scheduled posts, replies to mentions and searches, versus what it cannot, such as replying to strangers, follow automation and triggers on new mentions](https://quillly.com/serve/v1/019c4288-991a-773f-8671-f957d77800e3/images/aa602aae0bbb4a2c2cc235b2f3d706ef4ab41d8b.webp) ## What an n8n X workflow costs to run Self-hosted n8n is free, but the API isn't. X bills your developer app per request. Under [X API pay per use pricing](https://docs.x.com/x-api/getting-started/pricing), these are the rates that matter for the node's operations: | Action | X's price | 100 of them | | --- | --- | --- | | Post a tweet (no link) | $0.015 | $1.50 | | Post a tweet containing a link | $0.20 | $20.00 | | Reply to a mention (summoned) | $0.010 | $1.00 | | Like or retweet | $0.015 | $1.50 | | Send a DM | $0.015 | $1.50 | | Read a post (search, mentions) | $0.005 each | $0.50 | ![Bar chart of X API pay-per-use cost for 100 actions: 100 plain posts cost 1.50 dollars, 100 posts with a link cost 20 dollars, 100 summoned replies cost 1 dollar, 100 likes cost 1.50 dollars and reading 100 posts costs 50 cents](https://quillly.com/serve/v1/019c4288-991a-773f-8671-f957d77800e3/images/933026b85ca1d6811ce0b90f0d79f39b1c75b494.webp) The link row is the one that breaks budgets. An RSS-to-X workflow that posts every new blog article with its URL costs over thirteen times what the same post costs without one. Moving the link into a follow-up reply takes the reach penalty off the main post, but it doesn't save money — the reply still contains a URL. Our guide to [posting links on X](https://reachmore.co/blogs/how-to-post-links-on-x-2026) covers the trade. The polling pattern adds up too. A mention poll every five minutes is 288 runs a day. Each mention it returns is a billed read, so a busy account pays for its own inbox. Rate limits apply on top of billing; [what breaks under X's rate limits](https://reachmore.co/blogs/twitter-api-rate-limits) walks through them. > Want the workflow without the plumbing? [Try ReachMore's automations](https://reachmore.co) — a visual builder for X where every node shows its price before it runs. ## How to set up the n8n X node, step by step If you're going ahead with n8n, here's the short path that avoids the common first-day errors. 1. **Create an X developer app** and attach a pay-per-use billing account. Without billing, write calls fail. 2. **Set the callback URL** in the app's OAuth 2.0 settings to the OAuth redirect URL n8n shows in the credential screen. 3. **Add an "X OAuth2 API" credential** in n8n with the app's client ID and secret, then connect. n8n requests the scopes the node needs by default. 4. **Test with User → Get → "me"** before anything that writes. It proves the credential without posting. 5. **Build writes behind a manual trigger first.** Swap in a Schedule Trigger only once a dry run looks right. 6. **Put a cap in the workflow.** A Limit or IF node that stops after N posts per run protects you from a sheet with 400 rows and a bill to match. ![Vertical flowchart of a safe first n8n X workflow: a manual trigger, a Google Sheets read, a limit node capping rows, an IF node that routes posts containing a URL to a review branch, and an X Create node that posts the rest](https://quillly.com/serve/v1/019c4288-991a-773f-8671-f957d77800e3/images/5c95afa343d396db3eb07e9ac70c596ccf76cbcf.webp) Marking the row as posted in the same run is the step people skip. Without it, a retry re-posts everything, and X bills every duplicate. If you'd rather write this in code than in a canvas, the same calls are available from a script — see [the X API from Python in 2026](https://reachmore.co/blogs/twitter-api-python). ## n8n vs a purpose-built X tool n8n is a general automation platform. It's excellent when X is one step in a bigger pipeline — a CRM update, a Slack alert, a database write. It's more work when X is the whole job. | | n8n + X node | ReachMore | | --- | --- | --- | | Who holds the X app and bill | You | ReachMore | | Mention trigger | Build it (poll + dedupe) | Built in | | Approval before a reply sends | Build it (Wait + form) | Built-in queue | | Price shown before a run | No | Every node shows its cost | | Crash recovery | Depends on your design | Runs checkpoint after every step | | Cost per plain post | $0.015, paid to X | 15 credits | | Other apps in the flow | 400+ integrations | Webhook and HTTP steps | The honest trade: calling X directly from n8n is cheaper per action, because you pay X's price with nothing on top. [ReachMore](https://reachmore.co) prices each action in credits pegged to X's own cost, and takes its margin on the credit's sale price rather than by inflating the count. Automation runs that do paid work carry a flat 5-credit run fee when they succeed; orchestration steps like branches, waits and templates are free. What you get for that is the parts you'd otherwise build: a mention source, dedupe, a human approval queue, per-step prices, and runs that resume after a crash without re-spending credits. If you already run n8n for everything else, keep it. If X is the job, the plumbing is the cost. You can also drive ReachMore from an AI client through its [native MCP server](https://reachmore.co/blogs/twitter-mcp-server), which covers much of what people reach for n8n's AI agent nodes to do. ## Four n8n X workflows that are worth building Each twitter automation workflow below stays inside the API and pays for itself: - **Content queue to X.** Sheet or Notion → Limit → X Create → mark posted. Plain posts only, links reviewed by hand. - **Mention digest.** Schedule → mentions read → summarise → send yourself one Slack message a day. You reply by hand, in X. - **Brand search alert.** Schedule → Search (last 7 days) for your product name → dedupe → alert. Read-only, so a bug can't post as you. - **Cross-system logging.** When your own tweet is posted, write its ID and text to your database for later analysis. Notice what's missing: anything that replies to strangers, follows people, or sends cold DMs. Those aren't n8n gaps. They're API and policy lines, and our [social media scheduler API guide](https://reachmore.co/blogs/social-media-scheduler-api) explains why every tool hits them at scale. ## Frequently Asked Questions ### Does n8n have a Twitter trigger? No. n8n ships only an X action node, with no trigger. To start a workflow on a new mention, use a Schedule Trigger plus an HTTP Request node that reads your mentions, and store the last seen ID so each run only handles new ones. Every mention returned is a billed read. ### Is the n8n Twitter node free to use? The node is free and self-hosted n8n is free, but X isn't. Since February 2026 X bills every request on pay-per-use: about $0.015 per plain post, $0.20 per post containing a link, and $0.005 per post read. You pay X directly through your own developer app. ### Can n8n reply to any tweet automatically? No. X's API accepts a reply only when the author mentioned or quoted you. Replies to strangers' posts have no API path at any price. Templates that promise automated replies to keyword searches either fail or rely on browser automation, which breaks X's rules and puts your account at risk. ### Can n8n post images to X? Partly. The Create operation accepts a media ID but the node has no upload operation, so you upload the file with an HTTP Request node against X's media endpoint first, then pass the returned ID. It works, but it's the fiddliest part of most X workflows in n8n. ### Why is my n8n X workflow getting expensive? Usually links or polling. Any post with a URL costs $0.20 instead of $0.015, and a mention poll every few minutes pays for every post it reads. Cap rows per run, route link posts to review, poll less often, and store the last seen ID so retries don't re-read or re-post. ## Key takeaways - The n8n Twitter node has eight operations across tweets, DMs, lists and users — and no trigger. - It runs on your own X developer app, and every call is billed by X under pay-per-use. - Links are the budget killer: $0.20 per post with a URL versus $0.015 without. - No tool can reply to strangers through the API. Summoned replies only. - n8n is the right choice when X is one step in a larger pipeline. When X is the whole job, you're rebuilding triggers, dedupe and approvals by hand. > **X automations with the plumbing already built** > Mention sources, dedupe, a human approval queue and runs that resume after a crash, with every node's price shown before it runs. Credit wallet, one-time top-ups, credits never expire, charged only when an action succeeds. > → [Open ReachMore](https://reachmore.co)