Add a webhook
1
Open the Webhooks tab
In app.postqueen.ai, open Settings and choose the Webhooks tab. The tab is deep-linkable, so
/settings?tab=webhooks takes you straight there.2
Click Add a webhook
The heading shows how many webhooks you already have out of your allowance, for example
Webhooks (1/10).3
Give it a name and a URL
Name is yours to recognize later. URL is where the POST goes. It must be a public HTTPS address.
4
Choose which channels it covers
Integrations offers All integrations or Specific integrations. Pick All integrations and the webhook fires for every channel you have connected. Pick Specific integrations and a channel picker appears, so a webhook can watch only your YouTube channel, or only the two LinkedIn accounts a client cares about.
5
Send a test, then save
Send Test posts a sample payload to the URL right away and tells you whether the endpoint accepted it, so you can wire up the receiving side before a real post depends on it. Save stores the webhook.
The Webhooks tab only appears when your plan includes webhooks, and creating one past your allowance is refused with a message asking you to upgrade. On a self-hosted instance with no billing configured, plan checks are skipped entirely, so the tab is there and the count is not enforced.
When it fires
The post lands on X, and a fraction of a second later your endpoint hears about it.- One delivery per channel. A post scheduled to three channels publishes as three separate runs, so a webhook set to All integrations hears three times, once per channel, as each one goes out.
- Only the channels you selected. A webhook scoped to specific integrations is skipped for posts on any other channel.
- Only for real publishes. Drafts do not reach the publishing step, and a post that fails on the network after its retries stops short of it too, so neither one triggers a webhook.
What arrives
She sends aPOST with Content-Type: application/json. The body is a JSON array of post objects, so parse it as a list rather than as a single object.
URL requirements
The URL has to be HTTPS and has to resolve to a public address. She rejects anything that is not publicly routable:localhost and loopback, link-local, and the private ranges. That covers 10.x.x.x, 192.168.x.x, 172.16.x.x through 172.31.x.x and 169.254.x.x, whether you give her the IP or a hostname that resolves to it. The same check runs on Send Test.
Developing against a local listener? Put a public HTTPS tunnel in front of it and give her the tunnel URL.
Use it as a trigger
Most no-code automation platforms have a “wait for an HTTP call” starting block. Point a PostQueen webhook at one and every published post becomes the first step of a workflow.1
Create the catching step
In Zapier, start a Zap with Webhooks by Zapier, then Catch Hook. In Make, add a Custom webhook module. In n8n, drop a Webhook node on the canvas and set it to
POST.2
Copy the URL it gives you
Each of the three hands you a unique HTTPS URL. That is the value you paste into the webhook’s URL field in PostQueen.
3
Hit Send Test
With the catching step listening, press Send Test in PostQueen. The platform captures the sample body and learns the field structure, so
releaseURL, content and integration.name become pickable fields in the steps that follow.4
Build the rest of the workflow
Post the link to Slack, append a row to a sheet, or update a CRM record. The payload is an array, so use the platform’s iterate or line-item step if you want one step per entry.
Next steps
Zapier
Catch the hook, then send new posts back to PostQueen.
Make
Custom webhook in, HTTP module out, all in one scenario.
n8n
Webhook node in, PostQueen community node out.
RSS AutoPost
The other direction: a feed that fills your calendar on its own.
Public API
Schedule, list and delete posts from your own code.