Skip to main content
Where: Settings, Webhooks
Availability: Postiz Cloud, Standard plan and above, with the number of webhooks rising by plan. Self-hosted installs are unrestricted.
A webhook is an HTTP callback Postiz fires when a post publishes. Use it to mirror content into Slack, log posts into a spreadsheet, trigger a Zapier or n8n workflow, or update your own system.

​
Adding one

1

Name it

For your own reference in the list.
2

Give it a URL

Where Postiz should POST.
3

Choose the scope

All integrations, or a specific set of channels. Scoping by channel is how you route a client’s posts to that client’s system.
4

Send Test

Fires a test call immediately, so you can confirm the endpoint is reachable and see the payload shape before anything real depends on it.
5

Save

The header shows how many webhooks you have against your allowance.

​
Building the receiver

Always Send Test first and capture the body: that is the contract, and it is more reliable than any description here. Two habits worth having:
  • Return 2xx quickly, then do the work asynchronously. A slow endpoint is indistinguishable from a broken one.
  • Be idempotent. Treat a repeated delivery as a no-op rather than posting twice.

​
When a webhook stops firing

Postiz calls from its servers, so localhost and private network addresses will not work. Use a tunnel while developing.
Check your own logs first, then use Send Test to reproduce.
A webhook scoped to specific integrations stays silent for everything else. Re-check the scope.
Downgrading below the webhook allowance can take webhooks out of service. See Downgrades.
Webhooks tell you when Postiz acted. To make Postiz act, use the Public API, the CLI, or MCP.