LinkedIn posts with n8n and Bolta
Draft social posts from your n8n workflows. For LinkedIn, 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.
Draft a LinkedIn post from this new blog item, in my brand voice, and save it as a draft for my review
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 LinkedIn
Bolta writes the text, saves it as a draft on the account you name, and waits. Bolta lists each LinkedIn organization as its own account, so a company page is a separate choice from your personal profile.
- Text posts to a personal profile or to a company page you have connected.
- Posts visible to everyone by default, or to connections only if you ask for that.
LinkedIn 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 LinkedIn from n8n: LinkedIn articles, newsletters and document carousels. LinkedIn supports them, but this page does not confirm that Bolta publishes them. Comment length limits. The one checked limit on this page is the feed post.
| What to know | LinkedIn's own rule | What Bolta does |
|---|---|---|
| Post length | A feed post is capped at 3,000 characters, counting spaces, line breaks, emoji and the full text of any link you paste. | Bolta does not check LinkedIn text length, so LinkedIn may refuse longer text. The draft has to fit before you say yes. |
| Opening lines | The feed cuts a post after the first few lines behind a see more link. | Bolta keeps your first lines as written. Put the point there. |
| Formatting | Not stated on this page. | Plain text only. Bold, italic and headings become look-alike characters, a list becomes bullets, and a link is written as label (url). #hashtags and @mentions are kept as typed. |
| Who can see it | Not stated on this page. | Everyone, unless you set the post to connections only. |
n8n jobs for LinkedIn, and how to write them
- Check what is waiting for approval and post a note to your team
- Write to 3,000 characters including spaces, line breaks, emoji and any pasted link, because Bolta will not stop a post that is too long.
Example prompts for LinkedIn
Ways to start a LinkedIn draft from n8n. Each one saves a draft and stops.
Draft a LinkedIn post from this new blog item, in my brand voice, and save it as a draft for my review
Use the item text from the trigger to draft one LinkedIn post in the brand voice. Save a draft only.
When a new article is published on our blog, save a LinkedIn draft with the title and link and hold it for approval
When a customer review is added, save a LinkedIn draft that quotes it and wait for a person to approve
Bolta saves a draft, you read the exact text, you say yes
- 01
A step saves a draft
n8n sends the LinkedIn post to Bolta as a draft. Saving does not approve, schedule or publish it.
- 02
You read the exact text in Bolta
On LinkedIn the exact text includes where the line breaks fall, because the feed hides everything after the first few lines, and how any formatting was flattened to plain text.
- 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 LinkedIn
For LinkedIn, n8n reaches Bolta through a Bearer credential in n8n that holds a Bolta API key. The LinkedIn account itself is connected inside Bolta, not in n8n.
n8n keeps the Bolta key as a Bearer credential, and a workflow can save a LinkedIn 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 LinkedIn post it saves, so keep them on.
An illustration from the n8n guide, not real output. You ask: Use the item text from the trigger to draft one LinkedIn post in the brand voice. Save a draft only. The reply goes along these lines: I read the voice and the LinkedIn limits, wrote one post and saved it as a draft. It is not approved or published. Draft saved. Waits for your yes.
An illustration from the n8n guide, not real output. You ask: Pick the right brand from the form answer before drafting. If it is unclear, stop and ask. The reply goes along these lines: The form did not name a brand, so I stopped and asked you to choose one instead of guessing. Paused for your answer.
The MCP Client Tool path lets the AI Agent choose which Bolta tools to call, so it can handle an item that needs a brand lookup first. The cost is that its steps vary from run to run.
- Write in the brand voice. An AI Agent can read the brand voice before writing, so drafts from automation match drafts from people. Without that read it writes generically.
- 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 learns the voice. The agent pulls the brand voice context so the draft sounds like the brand and not like a generic model.
- A person decides. You open Bolta, read the draft and approve it, change it or reject it. Nothing is approved, scheduled or published until a person says yes.
- Setup: Path A: tell the agent to save drafts only. In the AI Agent node, add a System Message that says to save drafts only and never approve, schedule or publish unless a person has said yes. Ask it to name the brand, or pass the workspace_id you give it, when more than one brand is available.
- Setup: Path B: or call the REST API with an HTTP Request node. For the same call every time, add an HTTP Request node with Bearer or Header Auth and your credential. Pick the endpoint from the Bolta API docs. Run a read-only call first to confirm the key works, then run the workflow on one test item and find the draft in Bolta before you switch it on.
- REST API. An HTTP Request node with Bearer or Header Auth calls the Bolta REST API. Each endpoint and its permission is listed in the Bolta API docs.
- A workflow that is switched on with a schedule or webhook trigger runs without you opening anything, as long as your n8n instance is running. We have not checked n8n Cloud limits, so check yours.
Connect n8n to Bolta
Create an API key in Bolta, save it as a Bearer credential in n8n, then run one test item.
LinkedIn questions, answered for n8n
- How long can a LinkedIn post be when it comes from n8n?
- A LinkedIn feed post is capped at 3,000 characters, and the count includes spaces, line breaks, emoji and the full text of any link you paste. Bolta does not check LinkedIn length, so n8n should write inside the limit and show you the final text before you say yes.
- Can n8n post to a LinkedIn company page and not only my profile?
- Bolta lists each LinkedIn organization as its own account, so you can name the page when you ask. The company page has to be connected in Bolta first. If it is not there, ask for a connect link and finish the sign-in in your browser.
- What can it not do?
- A key can only do what the permissions you ticked allow, and a call without a permission returns a 403. Posting to a network needs that account connected in Bolta first. If the connection reaches more than one brand, each call has to name the workspace_id.
- 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.
- Why does the agent ask which brand to use?
- A key can reach more than one brand, and in that case every call has to name the brand. The API calls a brand a workspace, so give the agent the workspace_id in its System Message, or tell it the brand name in the workflow input.
- The agent cannot see any Bolta tools. What is wrong?
- Check Tools to Include on the MCP Client Tool node. If it is set to Selected with nothing chosen, nothing is exposed, so set it to All or pick the tools you want. Also confirm the node is attached to the Tools connector of the AI Agent.
- Does n8n publish LinkedIn posts without my yes?
- No. A n8n step can save a LinkedIn 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.
LinkedIn from other AI agents
The same LinkedIn limits apply whichever agent asks. The connection and the setup are what change.
Try a LinkedIn draft from n8n
Connect n8n, ask for a LinkedIn draft and read the exact text. Nothing goes live until you say yes.