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

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

Post to social media with *n8n*.

n8n talks to PostLake with the built-in HTTP Request node. Same body as the docs curl. No community node to maintain when a platform API changes.

**In short:** One HTTP Request node → POST /v1/posts. Any trigger becomes a multi-network publish; branch on targets[] in the response.

## When this guide is for you

Ops or growth already live in n8n and you want scheduled or AI-assisted posts without a separate node per network.

## 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 an **HTTP Request** node: method **POST**, URL `https://api.postlake.dev/v1/posts`.
1. Authentication → header `Authorization` = `Bearer sk_live_…`. Optionally add `Idempotency-Key` (e.g. from the trigger id).
1. Body → JSON: `{ "text": "{{$json.message}}", "profile": "my-brand" }`. Add `platforms` only if you want to filter networks on that profile.
1. After the node. Use an IF/Switch on `state` or on each `targets` item. Partial success is a successful HTTP 200 with mixed target states.
1. Wire any trigger (Schedule, Webhook, RSS, AI). Map text from earlier nodes into the body.

## 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

- A 200 with `state: "partial"` is not "everything worked". Inspect targets before marking the workflow done.

- For later publish, put `scheduledAt` in the body as UTC (trailing Z) or a naive local time plus `timezone`.

- Connect accounts under the profile in the dashboard first; the node cannot OAuth platforms for you.

Prefer an assistant over n8n 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 from n8n?

HTTP Request node: POST https://api.postlake.dev/v1/posts with Authorization: Bearer and JSON { text, profile }. PostLake fans out to connected accounts. No per-network community node.

### Do I need a special n8n node per network?

No. One HTTP call covers every connected account on the profile (optionally filtered with platforms).

### Can I schedule posts from n8n?

Yes, add scheduledAt (UTC, or a naive local time plus timezone) in the JSON body, or fire the workflow with n8n's Schedule trigger for "run now" posts. Credits charge when PostLake publishes.

## 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 Make](https://postlake.dev/guides/make.md)
- [Post with Zapier](https://postlake.dev/guides/zapier.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/n8n.md · https://postlake.dev/llms.txt