Skip to content
postpeg
Start trial

Integrations

Every integration calls the same REST API with an API key, so the requests, statuses and errors in these docs apply unchanged. The guides below set each tool up step by step.

n8n, Make and Zapier

Native apps for all three are built and coming soon. Until they’re published, use each platform’s own HTTP step: n8n’s HTTP Request node, Make’s HTTP → Make a request, or Webhooks by Zapier → Custom Request. Each guide has the exact fields for listing accounts and creating a post.

The request every guide builds:

curl https://api.postpeg.com/v1/posts \
  -H "Authorization: Bearer $POSTPEG_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: blog-builds-2026-10" \
  -d '{
    "account_ids": [
      "acc_mfz1x0k27d4q8vbn3c5s0a1p9e",
      "acc_mfz1y4r9h2c6t0wqk8e3m7ld5f"
    ],
    "content": "New on the blog: how we cut build times in half https://example.com/blog/builds"
  }'

AI agents (MCP)

The hosted MCP server at https://mcp.postpeg.com/mcp gives assistants such as Claude, Cursor and VS Code tools to check, publish and schedule posts, read analytics and answer comments. Send your key as Authorization: Bearer pp_live_…. In Claude Code:

Terminal
claude mcp add --transport http postpeg https://mcp.postpeg.com/mcp \
  --header "Authorization: Bearer pp_live_your_key"

The MCP guide has the config for every client and the full tool list.

Rules for every integration

  • Keep the key in the tool’s credential store, not pasted into each step, and use a separate key per tool so you can revoke one alone.
  • Send an Idempotency-Key on POST /v1/posts, comment replies and messages, built from something unique to the item (an RSS guid, a row number). Workflow tools retry steps; the same key never publishes twice.
  • Build JSON bodies safely. Text mapped straight into a JSON body breaks on the first double quote or line break. Each guide shows its tool’s way to escape it.
  • Don’t re-post failures from the workflow. postpeg retries networks that have a bad minute on its own. Watch GET /v1/posts?status=failed and alert a person instead.
  • Walk lists with cursor set to the previous next_cursor until it is null, and cap the number of pages.
  • Mind the rate limits: 120 requests a minute per key, at most 30 of them writes. On 429, wait Retry-After seconds and retry. See Rate limits.

A longer walkthrough with three example workflows is on the blog: Automate social posting with n8n, Make or Zapier.