# How to Post to Social Media with Zapier (2026) · PostLake

> Markdown version of https://postlake.dev/guides/zapier . The canonical page for humans.
> PostLake is the social media API for AI agents: https://postlake.dev/llms.txt

Post to social media with *Zapier*.

Webhooks by Zapier can call the same publish API as curl. Prefer a proper JSON body (profile + text) over comma-separated platform strings so addressing matches the docs.

**In short:** Webhooks by Zapier POST → /v1/posts with JSON { text, profile }. One action fans out; inspect the returned targets.

## When this guide is for you

The rest of your stack is in Zapier and you need multi-network publish without a custom Zapier app.

## Before you start

Same setup the [docs quickstart](https://docs.postlake.dev/quickstart.md) uses. Do this once:

- Sign up at [app.postlake.dev](https://app.postlake.dev) and verify your email (unlocks free credits).
- On **Channels**, create a **profile** (e.g. `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.
- Account menu → **API Keys** → create a key (`sk_live_…`). It shows once; treat it like a password.


## Step by step

1. Add **Webhooks by Zapier** → **Custom Request** (or POST) to `https://api.postlake.dev/v1/posts`.
1. Headers: `Authorization` = `Bearer sk_live_…`, `Content-Type` = `application/json`, optional `Idempotency-Key`.
1. Data / raw body as JSON: `{"text":"{{trigger text}}","profile":"my-brand"}`. To filter networks, add `"platforms":["bluesky","linkedin"]` as a JSON array, not a comma-separated string.
1. Map trigger fields into `text`. Test the step and open the response to confirm each `targets[]` entry.
1. For later publish, include `scheduledAt` as UTC (trailing `Z`) or a naive local time plus `timezone`.

## Read the response (don't skip this)

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).

- **You're only charged for targets that actually publish.** Failed targets cost nothing.

- Send an `Idempotency-Key` header on writes so a retry never double-posts.

- Full detail: [Publishing](https://docs.postlake.dev/publishing) · [Errors & retries](https://docs.postlake.dev/errors)

## Where the post goes

Same rules as the docs. Pick one addressing style:

- **By profile**: `"profile": "my-brand"` posts to every account under that profile (the name on Channels).

- **Filter networks**: `"platforms": ["bluesky", "linkedin"]` narrows that set. It is a **filter, not a selector**: if you have two Pinterest boards, both match `pinterest`.

- **By account id**: `"accounts": ["acc_…"]` for exact channels (copy an id on Channels, or `GET /v1/social-accounts`).

- One profile and you omit `profile`? PostLake uses that profile. Multiple profiles and you omit it? You'll get an error that names them.

See [Publishing: where to post](https://docs.postlake.dev/publishing).

## Do more (same API)

- **Schedule**: add `scheduledAt` as UTC (trailing `Z`), or a naive local time plus `timezone` (IANA, e.g. `Europe/London`). Credits charge when it fires. [Scheduling docs](https://docs.postlake.dev/scheduling) · [scheduling guide](/guides/schedule-posts-api).

- **Media**: `POST /v1/media`, then pass the `med_…` id in `media`. [Media docs](https://docs.postlake.dev/media).

- **Per-network caption**: `textOverrides` (e.g. shorter text for X). **Per-network options**: `platformOptions` (Pinterest `boardId`, TikTok privacy, …). Live option lists: `GET /v1/platforms/{platform}`.

- **Validate first**: `POST /v1/posts/validate` runs the same checks without publishing (free).

## Pitfalls specific to this path

- Comma-separated `platforms` strings are wrong. The API expects a JSON array of platform ids.

- HTTP success can still be `partial`; add a Filter or Code step if you need all targets published.

- Connect the profile's accounts in PostLake first; Zapier only calls the API.

Prefer an assistant over Zapier code? Point it at [MCP](https://docs.postlake.dev/mcp) (`https://api.postlake.dev/mcp`). Prefer the dashboard? Use [Quickstart → No code](https://docs.postlake.dev/quickstart).

## Common questions

### How do I post to social media with Zapier?

Webhooks by Zapier POST to https://api.postlake.dev/v1/posts with Authorization: Bearer and JSON { text, profile }. PostLake publishes to connected accounts on that profile.

### Do I need a PostLake Zapier integration?

No. Webhooks by Zapier is enough. One REST endpoint covers every network you have connected.

### Can I schedule through Zapier?

Yes, include scheduledAt (UTC, or a naive local time plus timezone) in the webhook JSON. Credits charge when it fires. See docs → Scheduling.

## Go deeper in the docs

These guides stay short on purpose. Canonical behaviour lives here:

    [Docs ### Quickstart Account, first channel, first post, MCP or API.](https://docs.postlake.dev/quickstart)
    [Docs ### Publishing Request body, addressing. Partial success, lifecycle.](https://docs.postlake.dev/publishing)
    [Docs ### Scheduling UTC or local time plus timezone, edit/cancel, fire-time credits.](https://docs.postlake.dev/scheduling)
    [Docs ### Platforms Limits, media rules, live platformOptions.](https://docs.postlake.dev/platforms)

Also: [Media](https://docs.postlake.dev/media) · [Errors](https://docs.postlake.dev/errors) · [MCP](https://docs.postlake.dev/mcp) · [Analytics](https://docs.postlake.dev/analytics)

## Related guides

- [Post with n8n](https://postlake.dev/guides/n8n.md)
- [Post with Make](https://postlake.dev/guides/make.md)
- [Schedule posts via API](https://postlake.dev/guides/schedule-posts-api.md)
- [Build an AI social agent](https://postlake.dev/guides/ai-social-media-agent.md)

[All guides](https://postlake.dev/guides/index.md) · [Full docs](https://docs.postlake.dev/) · [llms.txt](https://postlake.dev/llms.txt)

Plain markdown for agents: https://postlake.dev/guides/zapier.md · https://postlake.dev/llms.txt