Skip to main content
Your content rarely starts in PostQueen. It starts in a sheet a client fills in, in the post you publish on Friday, in a scenario you built two years ago. Five routes put her inside the tool you already run.
Content from AI, an RSS feed or a spreadsheet reaches PostQueen through Create Post and is scheduled to every channel at once

​
Pick your route

n8n

A community node with seven ready-made operations, from scheduling to video generation

Zapier

Webhooks by Zapier in both directions, until the native app ships

Make

The HTTP module for scenarios, plus a custom webhook coming back

Webhooks

An HTTP call to your endpoint the moment a post goes live

RSS AutoPost

She watches a feed hourly and drafts the newest item for you

​
What all five share

One API key. In app.postqueen.ai, open Settings › Developers › Public API and click Reveal. Send it as Authorization: YOUR_API_KEY, with no Bearer prefix. The n8n credential sends it for you once saved.
Everything here speaks to the Public API that also sits behind the CLI and MCP, so the result never depends on the route.
The create-post endpoint allows 30 requests per hour. A chatty trigger reaches that faster than you would expect, so filter or delay a busy source.

​
Self-hosting

Your own domain changes the address and nothing else. Webhooks and AutoPost live in your instance’s own settings, and with billing switched off the plan checks are skipped, so both tabs are there. AutoPost calls OpenAI for captions and pictures, so set OPENAI_API_KEY before turning those on, or leave them off and run the feed with no AI key at all.