How to connect PostEase to Zapier or Make

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. Webhooks are on the Pro plan.

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 (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. The same address also receives link_page.signup and link_page.message when someone signs up or writes to you on your link-in-bio page, so filter on event if an automation is only about posts.

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.

Questions