Schedule social media posts with Zapier

How to connect Postozo to Zapier

You need a Postozo account with at least 1 connected channel. Zapier talks to the Postozo public API at https://app.postozo.com/public/v1 using an API key with Webhooks by Zapier or MCP Client by Zapier.

Option 1: Webhooks by Zapier. In Postozo, open Settings, Developers and copy your API key. It starts with pz_live_. Treat it like a password.

1. Add an action step, choose Webhooks by Zapier and the Custom Request event.
2. Set Method to POST and URL to https://app.postozo.com/public/v1/posts.
3. Under Headers, add Authorization with the value Bearer YOUR_API_KEY, and Content-Type with application/json.
4. In Data, paste the JSON body and map fields from earlier steps:

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

Get channel ids first with a GET request to https://app.postozo.com/public/v1/integrations. Webhooks by Zapier is on the Professional, Team and Enterprise plans.

Option 2: MCP Client by Zapier (beta). On the Apps page click Add connection, search MCP Client, and fill in: Server URL https://app.postozo.com/mcp, Transport Streamable HTTP, and your API key as the Bearer Token. Then use the Run Tool action with a tool such as schedule_post. Zapier's page does not say which plans include it.

Check it works

Test the step. A working request returns a list with postId, group and status for each channel.

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 Zapier

• 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: help.zapier.com/hc/en-us/articles/8496326446989-Send-webhooks-in-Zaps, help.zapier.com/hc/en-us/articles/38777069364109-Connect-remote-MCP-servers-to-Zapier-using-MCP-Client. Zapier is a trademark of its owner. Postozo is not affiliated with it. Menus change; if a step looks different, follow the linked docs.