Build Make scenarios that schedule social posts with posterly

The shape of a Make integration

posterly is not in the Make app directory yet, but Make's generic HTTP module speaks fluent REST, and that is all the posterly API needs. You get the full surface: create, schedule, update, and delete posts, upload media, and list connected accounts. Incoming events arrive through Make's Custom Webhook module.

Grab an API key

In the posterly dashboard, open Settings and find the API section to create a key. API access starts at $3/month on individual plans, with Agency API at $29/month. You will use the key as a Bearer token in every HTTP module.

Create posts from a scenario

Add an HTTP module with "Make a request", method POST, URL https://www.poster.ly/api/v1/posts. Add a header named Authorization with the value Bearer YOUR_API_KEY, set the body type to JSON, and fill in caption, account_id (fetch your connected account ids once with GET /api/v1/accounts), and optionally scheduled_at as an ISO timestamp for scheduled publishing. Each request posts to one account; add an HTTP module per account, or use an Iterator, to publish the same caption everywhere.

Map data from other apps

The point of Make is the mapping panel, and it works beautifully here: drag the product name from a Shopify watch module into your caption, pull the image URL from Airtable, or feed an OpenAI module's output straight into caption. posterly fetches any media URLs you pass and validates them against each target platform's rules.

Trigger scenarios on publish events

Create a Custom Webhook in Make and copy its URL. Register it by sending POST https://www.poster.ly/api/v1/webhooks with that URL and the events you want, typically post.published and post.failed. posterly will then start your scenario in real time whenever a post goes live or errors, with the full post payload attached.

Handle failures gracefully

Subscribe to post.failed and route it to wherever your team lives: a Slack or Teams message with the error text, a row in an "attention needed" sheet, or an email. Publish failures are rare, expired platform tokens are the usual culprit, but catching them automatically beats discovering a gap in your feed a week later.

Check the signature

Each webhook delivery carries an HMAC SHA-256 signature in the X-posterly-Signature header, computed with your webhook secret. Make webhook URLs are unguessable, which covers most cases, but you can verify the digest in a scenario step when the downstream action is sensitive.

On the roadmap

A native Make app is planned. The HTTP module approach is the supported path today, and because it uses the same public API as posterly's MCP server and CLI, scenarios you build now will keep working unchanged.