Skip to main content

Use PostBoost with n8n

Use PostBoost in n8n: give an AI Agent PostBoost's MCP tools, or call the REST API from any workflow with the HTTP Request node.

note

PostBoost's MCP server uses an API token today. OAuth sign-in is in progress; when it ships, this page will show it first and keep the token setup as an advanced option.

Before you start​

  • A PostBoost account. The Free plan works: API, webhooks and MCP are on every plan.
  • An API token: in the dashboard go to Settings → Access Tokens → Create Token and copy it (it is shown once).
  • At least one connected social account, so there is something to post to.

The examples use YOUR_API_TOKEN. Never commit a real token; where the client supports it, read it from an environment variable such as POSTBOOST_API_TOKEN.

There are two ways to use PostBoost in n8n. A native PostBoost node is planned; until then, both of these work today.

Option 1: AI Agent with the MCP Client Tool​

Use this when an AI Agent node should decide what to post.

  1. In your workflow, add an AI Agent node with a chat model.
  2. Under the agent's Tool connector, add an MCP Client Tool node.
  3. Set the endpoint to https://postboost.co/mcp/postboost. If your n8n version shows a Server Transport option, choose HTTP Streamable. PostBoost does not offer an SSE endpoint, so older n8n versions that only support SSE cannot connect.
  4. Set Authentication to Bearer Auth and create a credential with your API token.
  5. Leave Tools to Include on All, or pick only the tools the agent needs (for example listing accounts and creating posts).

Option 2: HTTP Request node (no AI)​

Use this for fixed workflows such as "RSS item → scheduled post".

  1. Create a Header Auth credential: name Authorization, value Bearer YOUR_API_TOKEN.
  2. Add an HTTP Request node: method POST, URL https://postboost.co/app/api/<workspaceUuid>/posts, authentication Generic Credential Type → Header Auth, body JSON as in the Quick Start.
  3. Your workspace UUID is in the dashboard URL (Quick Start, step 4); get account IDs with GET https://postboost.co/app/api/<workspaceUuid>/accounts.

Verify​

For option 1, open the chat panel and ask the agent to list your PostBoost accounts. For option 2, run the node once and check the post appears in your PostBoost calendar.

Try it​

Ask the agent things like:

  1. "List my PostBoost social accounts."
  2. "Schedule a LinkedIn and X post for tomorrow at 9:00 saying our 1.8 release is live, with a link to https://postboost.co/docs/changelog."
  3. "Show me posts that failed in the last 7 days and tell me why each one failed."

The agent calls PostBoost tools (list accounts, create post, list posts) and shows you each call before running it, depending on your client's approval settings.

Troubleshooting​

ProblemWhat to check
401 UnauthenticatedThe header must be exactly Authorization: Bearer <token>. Create a new token if the old one was deleted.
403 on a toolAdmin-only tools (workspaces, users, subscriptions) need a token from an admin user.
Tool list is emptyThe server did not connect. Check the URL is https://postboost.co/mcp/postboost (no trailing path), then restart or reload the client.
Network or timeout errorsThe endpoint uses Streamable HTTP. Make sure your client version supports remote HTTP MCP servers and that a proxy is not blocking postboost.co.