PostEaseHow to connect PostEase to Zapier or Make
Every publish can POST a signed payload to a Zapier Catch Hook or a Make custom webhook, carrying the caption, the account and a link to the live post. No app listing needed, and you can send a test event to map the fields.
Published Sep 11, 2026
There is no listed app, and you do not need one
Neither directory carries a PostEase app yet. You do not need one: both Zapier and Make accept a plain webhook from anywhere, which is what this uses, and it takes about two minutes.
1. Zapier
Create a Zap. For the trigger, choose “Webhooks by Zapier”, then “Catch Hook”. Zapier gives you a URL. Paste it into Settings, then Developer, then Save webhook. Come back to Zapier, ask it to test the trigger, and press “Send a test event” in PostEase so it has a payload to read the fields from. Then add whatever action you want — a Slack message, a row in a sheet, a Notion page.
2. Make
Create a scenario and add the “Webhooks” module, then “Custom webhook”. Add a webhook and copy its address. Paste it into Settings, then Developer, then Save webhook. In Make, press “Redetermine data structure”, then “Send a test event” in PostEase, and Make will map the fields for you.
3. What arrives
One POST per published post, per channel. A post going to four channels sends four, because each channel publishes independently and can fail on its own. The body is JSON with these fields: event (always post.published), postId, connectedChannelId, platform, platformPostId, publishedAt, caption, channelName, and url. caption is null when the post had none, and url is null on platforms with no public permalink we can build.
4. Checking it came from us
Every request carries X-PostEase-Signature: sha256=… — an HMAC-SHA256 of the exact request body, keyed with the signing secret shown beside your webhook URL. Recompute it on your end and compare. Zapier and Make do not check signatures for you, so if the automation does something consequential, verify it in a code step. The header is on test events too, so a receiver that checks signatures accepts them the same way.
5. When a delivery fails
A failed delivery never affects publishing — the post still goes out. The Developer page shows the last delivery's status and the reason it failed. There are no automatic retries, so a receiver that was down for an hour has missed those events; the posts themselves are all on the Performance page.
Wire it into whatever you already run.
Included with the plan, not a separate integration bill.
More guides
Connecting PostEase to the rest of your stack
The outbound webhook, Zapier and Make, importing a calendar from another scheduler, and the browser extension are one integration surface, not four separate things to discover on your own.
Adding alt text to the images you schedule
One field in the composer, sent to X, LinkedIn, Pinterest, and Bluesky with the image. What it is for, what the 500-character cap comes from, and why video is left out.
How to set your workspace timezone
Every time you see or type in PostEase is in one zone chosen for the workspace, not your browser’s. Posts already scheduled keep their exact time when you change it.
How to disconnect a channel
Remove a connected account from a workspace: what happens to the posts scheduled to it, and where PostEase can revoke its own access versus where you remove it yourself.