Post from Make
Connect PostWharf to Make and publish or schedule to every network you run. An HTTP module pointed at one endpoint. Delivery receipts come back as webhooks. Ten of the fourteen networks publish today; Reddit, Discord, Snapchat and WordPress are available on request.
How it connects
An HTTP module pointed at one endpoint. Delivery receipts come back as webhooks.
POST https://api.postwharf.com/v1/posts Authorization: Bearer YOUR_WORKSPACE_KEY
A typical automation
Trigger on a finished render, publish the clip to every vertical channel.
Getting the result back
Register a webhook and PostWharf posts every delivery outcome to you — published, retrying, failed, or removed after publishing. Each is signed with HMAC-SHA256 so you can verify it came from us. Webhook reference.
Where this actually happens
A single HTTP module on the scenario canvas, usually right after the step that produces the thing you are announcing.
Resist the router
The canvas invites a router with a module per destination, and it is the wrong shape here. One call carrying every channel id costs fewer operations and leaves you one post to check instead of five scattered across the run history. When something does fail, a single post with five deliveries tells you which destination refused it and why; five separate modules tell you only that one of them went red.