Zapier, n8n and Make

Postel has apps for Zapier, n8n and Make. They connect with an API key and use the same endpoints these docs describe.

What the apps do

• Triggers poll GET /v1/events for posts that went out, posts that failed, drafts ready in Review and viral posts in your niche.
• Actions create, schedule and publish posts, write a post in your voice, and write your take on a viral post.
• Connection test. The apps check your key with GET /v1/me and name the connection after its label.
• Network dropdowns come from GET /v1/channels, connected networks first.

To connect, create a key in Postel under Settings → API & MCP and paste it into the app.

Use any HTTP step

You don't need an app. Any tool that can send an HTTP request can use the API, such as Webhooks by Zapier, n8n's HTTP Request node or Make's HTTP module.

Two things make automations safer:

• Send an Idempotency-Key on steps that create posts, built from the run's id, like n8n:<execution id>:<node>. When a step is replayed after a timeout, it returns the first post instead of making a second one. See Idempotency.
• Branch on code in error responses and show error to people. The message already says what to do. See Errors.

Publishing now answers at once and the post goes out within a minute, so a step never waits on the network. Use a post.published or post.failed trigger to act on the result.

The X-Postel-Client header

Postel's apps send X-Postel-Client with their name and version, like zapier/1.2.0, so posts show which tool created them. The header is optional. If you build your own integration, you can send your app's name and version the same way:

X-Postel-Client: my-crm-sync/1.4.0

It never changes how a request behaves.