---
title: "n8n integration with Bolta"
description: "Connect an n8n workflow to Bolta with an API key. Add the MCP Client Tool node to an AI Agent so it can draft posts in your brand voice, or use an HTTP Request node to call the Bolta REST API with fixed steps. Nothing goes out until a person approves it."
canonical_url: "https://bolta.ai/integrations/n8n"
markdown_url: "https://bolta.ai/integrations/n8n.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# n8n integration with Bolta

Source: https://bolta.ai/integrations/n8n
Last updated: 2026-11-21

Connect an n8n workflow to Bolta with an API key. Add the MCP Client Tool node to an AI Agent so it can draft posts in your brand voice, or use an HTTP Request node to call the Bolta REST API with fixed steps. Nothing goes out until a person approves it.

## Summary

Draft social posts from your n8n workflows

## Who this is for

- Developers
- Automation teams
- AI-assisted marketing teams

## Core capabilities

- Turn a new RSS item or blog post into a draft for LinkedIn or X
- Send a form answer or customer win to Bolta as a draft for review
- Let an AI Agent draft a week of posts in your brand voice
- Pull recent post results into a sheet or report on a schedule
- Check what is waiting for approval and post a note to your team

## Limitations and boundaries

- Integration availability depends on current APIs, authentication, scopes, and account permissions.
- Generated content can be incorrect and should be reviewed before publication.
- Availability depends on the current Bolta plan, connected network, account permissions, and integration coverage.
- Current prices and plan limits must be verified on the Bolta pricing page.

## Create a Bolta API key

In Bolta, open Settings, API Keys and create a key for the brand this workflow should post for. For drafts and reading, tick Read Workspace, Read Accounts, Read Posts and Write Posts. The key starts with bolta\_sk\_ and is shown once, so copy it now.

## 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.

## 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.

## 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.

## 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.

## Agent path or fixed path in n8n

The two routes behave differently inside a workflow, and the difference shows up when something odd arrives. 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. 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.

## Keep the key in a credential

Create the Bearer credential once and reuse it in every Bolta node. Tick only Read Workspace, Read Accounts, Read Posts and Write Posts for drafting. Use one key per brand when the workflows are for different clients. Revoke and replace the key in Bolta if it appears in a shared export.

## Test on one item first

1. Run a read-only call: List workspaces to confirm the key works and to find your brand's workspace\_id. 2. Execute on one test item: Click Execute workflow once and open Bolta to find the draft. 3. Switch it on: Turn the workflow on only after the draft looks right.

## Does Bolta publish without my approval?

No. A workflow can save drafts on its own, but nothing is approved, scheduled or published until a person says yes. Approving stays with you in Bolta, and Safe Mode and client sign-off still apply.

## 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.

## 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.

## How do I keep the API key safe?

Treat it like a password. Keep it in an n8n credential, not in a Set node or in the workflow text. If it leaks, revoke it in Bolta and make a new one.

## What does the API key start with and where do I make it?

Bolta keys start with bolta\_sk\_. You create one in Bolta under Settings, API Keys, and it is shown once, so copy it straight into an n8n credential. If you lose it, revoke it and make another.

## 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.

## What does the node answer if the key is wrong?

The MCP node reports Invalid or expired API key, and an HTTP Request node returns a 401. Check the credential sends Authorization with the value Bearer bolta\_sk\_ followed by your key, with one space after the word Bearer. Sending the same key again gives the same answer, so replace the key.

## 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.

## Can a workflow approve or schedule posts by itself?

It can save drafts without anyone watching. Approving and scheduling stay with a person, and the System Message we suggest tells the agent to stop at a draft. Treat that message as a guard rail and rely on the Bolta approval rules for the real limit.

## 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.

## Relevant links

- [Related page: /integrations](https://bolta.ai/integrations)
- [Bolta pricing](https://bolta.ai/pricing)

## Supporting sources

- [n8n official website](https://n8n.io/)
