n8n has a built-in X node, and it works. The catch is the setup before it: the node signs in with OAuth 2.0 credentials from your own app on the X developer portal, and X's API is pay-per-use, so that app needs a payment method on file. For a workflow that posts a few times a week, that is a lot of setup.

This post covers the other route: one HTTP Request node that calls a posting service, which posts to X through its own app. Disclosure up front: we build Posteora, the service in the example.

Route 1: n8n's X node with your own app

  1. Sign in at the X developer portal and create a project and an app.
  2. Turn on OAuth 2.0 user authentication, set the callback URL n8n shows you, and copy the client id and secret.
  3. Add a payment method for pay-per-use. X lists $0.015 for a post and $0.200 for a post with a link (we broke the prices down in X API cost per post, explained).
  4. Create the X credential in n8n, connect, and use the node's Create Tweet operation.

  5. Good for: high volume, X only, or a workflow that also reads from X.

  6. You handle: the app, the bill, token refresh, and X's rules for text and media.

Route 2: one HTTP Request node, no developer app

Here a posting service holds the X app. You connect your X account to it once on its website, and n8n sends it plain HTTP.

  1. Create a free Posteora account and connect X under Connections. Bluesky, Mastodon, LinkedIn, TikTok, Pinterest and YouTube connect the same way, one account each.
  2. Copy your API key from the Account page. It is a password: keep it in an n8n credential, not in the node.
  3. Add an HTTP Request node:
  4. Method POST, URL https://posteora.com/api/v1/posts
  5. Authentication: Generic, Header Auth, name Authorization, value Bearer <your key>
  6. Body: JSON
{
  "text": "Shipped the new release notes today.",
  "targets": ["x", "bluesky"],
  "scheduled_for": "2026-11-24T09:00:00-08:00"
}
  1. Run it. The answer is JSON with status_label (queued), the post id and a receipt that says how much of the X allowance is left. Leave out scheduled_for to publish now; that call also needs an Idempotency-Key header, so a retry by n8n never posts twice.

A network that refuses the post (text too long, a duplicate within 48 hours, a daily cap) answers with its own readable message, so an IF node after the request can catch it. For results after the fact, register a webhook and n8n hears post.sent or post.failed. All of it is on the API docs.

  • Cost: the free plan has 10 posts a month across all networks with no card, and no links on X. Pro is $19 a month, or $15 billed annually, with an X allowance of about 20 link posts or 260 plain posts a month. Past that you can connect your own X API key at no extra charge. Full table on pricing.
  • Good for: a few posts a day, the same post on X and other networks, or a workflow where you do not want to run an X app.
  • Limits: one X account per network on Pro, the daily caps listed on the API docs, and no reading from X.

A Posteora community node for n8n is written and is not yet published in the n8n community nodes directory. Until it is, the HTTP Request node above does the same job.

Which one to pick

  • Heavy X volume, or you also read from X: your own developer app and n8n's X node. You pay X directly and keep full control.
  • A few posts a day, more than one network, no app to run: one HTTP Request node to a posting service.
  • You draft in Claude or ChatGPT rather than n8n: skip the workflow and connect the assistant; see n8n, Zapier or MCP: three ways to schedule posts.