There is no Postey app in Zapier's app directory yet, so searching for Postey inside a Zap finds nothing. Postey's own settings list Zapier under Integrations as coming soon. This page covers what works today.
Connect over MCP
Postey runs a remote MCP server. Any automation tool with an MCP client step, such as the MCP Client Tool node in n8n or the MCP Client in Make, can connect to it with a URL and one header:
- Server URL:
https://mcp.postey.ai/mcp - Header:
X-API-Key: mk_...(your MCP key)
Create the MCP key in your Postey settings under AI & Agents → Advanced. MCP keys work on the free plan. Every key is listed in the same place and can be revoked there. Treat it like a password: anyone holding it can act on your Postey account.
What the workflow can do
It gets the same tools an AI agent gets: list your connected accounts, create and update drafts with a separate caption for each network, and publish. Scheduling needs a paid plan. The full tool list and the free-plan limits are on the MCP page, and plans are compared on Pricing.
Publishing from an unattended workflow
Postey marks publish, schedule, delete and reply as actions that need confirmation, and chat clients such as Claude Code stop and ask before running them. An automation runs with nobody watching, so there may be no one to ask. If a person should check every post first, have the workflow create drafts only and publish them from Postey yourself.
Calling the REST API from Zapier
On paid plans you can also create a REST API key in your Postey settings and call the REST API from a webhook step, for example Webhooks by Zapier. Send the key in the X-API-Key header. The endpoints are documented under Posts in the sidebar, starting with Getting Started.