Post with Make
Use Make's generic HTTP module against PostLake's publish endpoint. Body and addressing match the Publishing docs, profile, optional platforms filter, then read targets.
Get started free →Free tier. No card · one API for every network · full MCP access
Your automations already run in Make and you want one step to fan out instead of one module per network.
Same setup the docs quickstart uses. Do this once:
my-brand) and connect at least one account. Bluesky is the fastest first channel: no app review. Instagram/TikTok/Facebook need each platform's review before API posting.sk_live_…). It shows once; treat it like a password.Configure once, then reuse on every run. Same request body as the docs, this is just how Make sends it.
https://api.postlake.dev/v1/posts.Authorization = Bearer sk_live_…. Add Idempotency-Key when the scenario can retry.{ "text": "Hello from Make", "profile": "my-brand" }.text (and optional platforms / scheduledAt).state / targets: don't treat HTTP 200 alone as full success.You get one Post with an overall state and a targets[] array. One entry per account. Always check each target; partial success is normal.
{
"id": "post_a1b2c3",
"state": "partial",
"targets": [
{ "platform": "bluesky", "state": "published", "url": "https://bsky.app/…" },
{ "platform": "linkedin", "state": "failed",
"error": { "type": "invalid_request", "message": "…", "retryable": false } }
]
}published: every target succeeded. partial: some published, some failed. failed: none published. processing: still going (async networks like TikTok).Idempotency-Key header on writes so a retry never double-posts.Same rules as the docs. Pick one addressing style:
"profile": "my-brand" posts to every account under that profile (the name on Channels)."platforms": ["bluesky", "linkedin"] narrows that set. It is a filter, not a selector: if you have two Pinterest boards, both match pinterest."accounts": ["acc_…"] for exact channels (copy an id on Channels, or GET /v1/social-accounts).profile? PostLake uses that profile. Multiple profiles and you omit it? You'll get an error that names them.See Publishing: where to post.
scheduledAt as UTC (trailing Z), or a naive local time plus timezone (IANA, e.g. Europe/London). Credits charge when it fires. Scheduling docs · scheduling guide.POST /v1/media, then pass the med_… id in media. Media docs.textOverrides (e.g. shorter text for X). Per-network options: platformOptions (Pinterest boardId, TikTok privacy, …). Live option lists: GET /v1/platforms/{platform}.POST /v1/posts/validate runs the same checks without publishing (free).platforms filters the profile; unconnected networks simply won't appear as targets.scheduledAt without timezone is a 400. Send UTC with a trailing Z, or a local time plus an IANA zone.Prefer an assistant over Make code? Point it at MCP (https://api.postlake.dev/mcp). Prefer the dashboard? Use Quickstart → No code.
HTTP Make a request: POST https://api.postlake.dev/v1/posts with Bearer auth and raw JSON { text, profile }. One module posts to every account on that profile.
You don't need one. The HTTP module is enough because PostLake exposes a single REST publish endpoint.
Add scheduledAt (UTC, or a naive local time plus timezone) to the JSON, or schedule the scenario itself. Credits are charged when the post publishes, not when you queue it.
These guides stay short on purpose. Canonical behaviour lives here:
Also: Media · Errors · MCP · Analytics
All guides · Full docs · llms.txt · Markdown
Stuck? The docs are the source of truth, start at Publishing.
Open the dashboard →