Schedule social media posts with n8n

How to connect Postozo to n8n

You need a Postozo account with at least 1 connected channel. n8n talks to the Postozo public API at https://app.postozo.com/public/v1 using an API key with the HTTP Request node.

1. In Postozo, open Settings, Developers and copy your API key. It starts with pz_live_. Treat it like a password.
2. Add an HTTP Request node. Set Method to GET and URL to https://app.postozo.com/public/v1/integrations.
3. Under Authentication, choose a generic credential of type Bearer Auth and paste your key (n8n adds "Bearer" for you). A Header Auth credential with name Authorization and value Bearer YOUR_API_KEY works too.
4. Run the node and copy the id of each channel you want to post to.
5. Add a second HTTP Request node with Method POST and URL https://app.postozo.com/public/v1/posts, the same credential, and a JSON body:

{
  "type": "schedule",
  "date": "2026-10-01T09:30:00+05:30",
  "content": "Your post text",
  "channels": ["CHANNEL_ID"]
}

Use "type": "draft" to save only, "now" to post right away, or "review" to send it to a client for approval. Use expressions to fill the text and date from earlier nodes.

n8n also has MCP client nodes. Their docs describe an SSE endpoint, and Postozo uses Streamable HTTP, so we document the HTTP Request node, which we know works.

Check it works

Run the GET https://app.postozo.com/public/v1/is-connected request. It returns {"connected": true} when the key works.

Endpoints you will use most

All paths start with https://app.postozo.com/public/v1. Send Authorization: Bearer YOUR_API_KEY on every request. The API accepts the same paths and bodies as the Postiz public API, so Postiz examples work after you change the address and key. It allows 90 post creations per hour per workspace.

Ideas for n8n

• A new row in a sheet becomes a scheduled post on the date in the row.
• A new blog or RSS item becomes a draft for each channel, ready for review.
• A form answer from a client becomes a post sent to them for approval.
• A failed post triggers a message to your team, using a Postozo webhook.

Safety and control

• Use "draft" or "review" as the type when a person should check the post first.
• A post is never sent twice. If Postozo cannot confirm a post went live, it marks it "could not confirm" instead of retrying on its own.
• Keep the API key in the tool's credential store, not in plain text fields shared with others.
• Create a new key in Postozo under Settings, Developers if a key leaks. The old one stops working.

Sources

Setup steps checked on 29 September 2026 against: docs.n8n.io/integrations/builtin/credentials/httprequest/, docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.toolmcp/. n8n is a trademark of its owner. Postozo is not affiliated with it. Menus change; if a step looks different, follow the linked docs.