X (Twitter) posts with n8n and Bolta
Draft social posts from your n8n workflows. For X, Bolta saves a draft, you read the exact text, and nothing goes live until you say yes.
Checked 2026-11-21
Create an API key in Bolta, save it as a Bearer credential in n8n, then run one test item.
Write three X posts about the feature in this release note and save them as drafts only
Illustration of the reply: Bolta returns a draft showing the connected account and the scheduled time, with Approve, Edit and Reject actions.
What Bolta does on X
Bolta reads the limit for each connected X account, so a Premium account and a free account get different ceilings. Text that is too long does not get trimmed on X: the post fails, so the draft has to fit first.
- Single posts and threads. In a thread, Bolta posts every part after the first as a reply to the one before.
- Images. A post needs text: an image with no text is not supported on X.
X limits and format rules
Network rules last checked 2026-07-28. Bolta's posting rules for your workspace win if they differ from this page.
Not promised for X from n8n: Polls and Spaces announcements. Neither is confirmed for Bolta. How many hashtags work best. Bolta checks none, and this page makes no claim about it.
| What to know | X's own rule | What Bolta does |
|---|---|---|
| Post length | Accounts without a paid subscription are limited to 280 characters. X Premium subscribers can publish up to 25,000. | Bolta reads the limit per account. Longer text makes the post fail, so shorten it first. The 25,000 limit is a ceiling for Premium accounts, and X can still refuse a long post. |
| Links and media | A pasted link counts as 23 characters however long it is. Photos, videos and GIFs count as zero characters. | Bolta does not check how many hashtags you use or their format. They are kept as typed. |
| Threads | Posts can be chained into a thread, and each post carries its own separate character limit. | Each X thread part after the first is posted as a reply to the one before it. |
| Who can reply | Replies can be limited to everyone, accounts you follow, verified accounts, or only the accounts you mention. It is chosen before you post. | The default is that anyone can reply unless you limit it. |
| Video | Not stated on this page. | Video on X is checked on X's side for duration, format and posting eligibility, so a successful upload does not guarantee publication. Ask for the posting rules before you attach one. |
n8n jobs for X, and how to write them
- Send a form answer or customer win to Bolta as a draft for review
- Write to 280 unless the account has X Premium. Check the count, because a post over the limit fails instead of being cut.
Example prompts for X
Ways to start an X draft from n8n. Each one saves a draft and stops.
Write three X posts about the feature in this release note and save them as drafts only
Draft three X posts about this release note and save each one as a draft.
When a release is published on GitHub, save an X draft with the release name and link and hold it for approval
When a blog post goes live, save a short X thread of its three main points and wait for approval
Bolta saves a draft, you read the exact text, you say yes
- 01
A step saves a draft
n8n sends the X post to Bolta as a draft. Saving does not approve, schedule or publish it.
- 02
You read the exact text in Bolta
On X the exact text includes the character count with links counted at 23, and, for a thread, every part in order.
- 03
You say yes in Bolta
Only your yes approves and schedules it. Safe Mode, client sign-off and brand approval rules still apply.
Using n8n for X
For X, n8n reaches Bolta through a Bearer credential in n8n that holds a Bolta API key. The X account itself is connected inside Bolta, not in n8n.
n8n keeps the Bolta key as a Bearer credential, and a workflow can save an X draft from a trigger such as a new blog item. A workflow can save drafts, but it cannot approve them.
This connection uses a Bolta API key, which acts as you. Safe Mode and client sign-off still apply to every X post it saves, so keep them on.
An illustration from the n8n guide, not real output. You ask: Draft three X posts about this release note and save each one as a draft. The reply goes along these lines: I saved three drafts on the X account, each under the post limit. None are approved or published. Three drafts. Waits for your yes.
An illustration from the n8n guide, not real output. You ask: List the brands this key can reach and the accounts connected to each. Change nothing. The reply goes along these lines: I found your brands and their connected accounts and left everything untouched. Tell me which brand to use. Read only. Nothing created.
The HTTP Request path makes one known call, so every run looks the same and is easy to debug. It cannot adapt on its own when the input changes.
- Draft posts from any workflow event. A new RSS item, form answer or customer win can become a draft on a connected account. The draft lands in Bolta, not on the network.
- Report on what is waiting. A scheduled workflow can pull the approval queue and post a note to your team in chat or email, so drafts do not sit unseen.
- It reads the posting rules. Before writing, the agent can check the limits that apply to the account it is drafting for, so a long text does not fail later.
- It learns the voice. The agent pulls the brand voice context so the draft sounds like the brand and not like a generic model.
- Setup: Save the key in n8n as a credential. In n8n, open Credentials and create a Bearer credential. Paste your bolta_sk_ key as the token and name it something clear. If you use a Generic header instead, the name is Authorization and the value is Bearer followed by your key.
- Setup: Path A: add the MCP Client Tool to an AI Agent. Click the plus under the Tools connector of your AI Agent node and add MCP Client Tool. Set the endpoint to https://mcp.bolta.ai/mcp, choose HTTP Streamable if the node offers a transport, set authentication to Bearer and pick your credential. HTTP Streamable arrived in n8n 1.104, so update n8n if you only see SSE.
- MCP with an API key. Add the MCP Client Tool to an AI Agent, use https://mcp.bolta.ai/mcp, set authentication to Bearer and pick a credential holding your bolta_sk_ key. Needs n8n 1.104 or newer for HTTP Streamable.
- Each run can save drafts to Bolta on its own, and that is where it stops.
Connect n8n to Bolta
Create an API key in Bolta, save it as a Bearer credential in n8n, then run one test item.
X questions, answered for n8n
- What happens if n8n writes an X post that is too long?
- The post fails. Bolta does not trim X text, so n8n has to shorten it first. The limit is 280 characters for accounts without a paid subscription, and X Premium accounts can post up to 25,000, though X can still refuse a long post.
- Can n8n write an X thread?
- Yes. Ask for several parts, and Bolta posts each part after the first as a reply to the one before it, so they read as one thread. Each part carries its own limit. You read all of the parts in Bolta and say yes before any of them goes out.
- Should I use the MCP Client Tool or the HTTP Request node?
- Use the MCP Client Tool if you want an AI Agent to decide which Bolta tools to use. Use the HTTP Request node if you want the same fixed call every time. The MCP path needs n8n 1.104 or newer. If your node has no HTTP Streamable choice, use the HTTP Request node.
- Is this tested on every n8n version?
- No. Menu and field names change between n8n versions, so look for the closest label if one does not match. The AI Agent path also needs a chat model you set up in n8n yourself, which is separate from Bolta.
- Which permissions should the key have?
- For drafting and reading, tick Read Workspace, Read Accounts, Read Posts and Write Posts. Leave the rest off. A call that needs a permission the key lacks returns a 403, and the fix is to edit the key or make a new one.
- Can one workflow serve several clients?
- Yes, if the key reaches several brands and each call names its workspace_id. A tidier option is one key per brand, saved as separate n8n credentials, so a mistake in one workflow cannot touch another brand.
- Does n8n publish X posts without my yes?
- No. A n8n step can save a X draft, not approve it. It waits in Bolta for a person to say yes.
More from n8n
n8n can work with the other networks Bolta publishes to. Each page has its own limits and review notes.
X from other AI agents
The same X limits apply whichever agent asks. The connection and the setup are what change.
Try an X draft from n8n
Connect n8n, ask for an X draft and read the exact text. Nothing goes live until you say yes.