Sign up
Integration · Workflow automation

Put your socials on autopilot.

Wire post mate into n8n and let workflows do the work. Start a flow the moment a post publishes or fails, and schedule posts, write captions, pull analytics and upload media across all 13 networks — from one node. Runs on n8n Cloud or self-hosted.

Build a workflowSee recipes
6 trigger events11 actionsHMAC-signed
Blog → everywhereActive
TriggerNew blog postRSS Feed
post mateGenerate captionAI · per network
post mateSchedule post5 networks
OutputNotify channelSlack
Runs anywhere n8n runs
n8n CloudSelf-hostedn8n Desktopnpx n8n
How it connects

Data flows both ways.

post mate plugs into n8n through two open primitives you already have: signed webhooks fire out to start a workflow, and the REST API lets a workflow reach back in to act.

post mate → n8nTriggers (webhooks)

post mate fires an HMAC-signed webhook the moment something happens — a post publishes, a post fails, an account connects. The post mate Trigger (or n8n's Webhook node) catches it and starts your flow. No polling, sub-second latency.

post.publishedpost.failedaccount.connected
n8n → post mateActions (REST API)

Anywhere in a workflow, the post mate node calls our stable /v1 REST API with your Bearer key — schedule a post, reschedule, cancel, generate a caption, read analytics or upload media. Same auth, same guardrails as the dashboard.

POST /v1/postsGET /v1/analyticsPOST /v1/media
The post mate node

Eleven actions, grouped by resource.

Drop the post mate node into any workflow, pick a resource and an operation, map your fields, and run. Each action maps to a stable REST endpoint, so nothing breaks under you.

post-mate · v1
Post5 ops
  • Schedule / CreatePOST /v1/posts
  • GetGET /v1/posts/:id
  • Get Many (queue)GET /v1/posts
  • Update / ReschedulePATCH /v1/posts/:id
  • CancelDELETE /v1/posts/:id
Caption3 ops
  • Generate captionAI · per network
  • Suggest hashtagsAI
  • TranslateAI · keep voice
Account1 op
  • Get ManyGET /v1/accounts
Analytics & Media2 ops
  • Get analyticsGET /v1/analytics
  • Upload mediaPOST /v1/media
The post mate trigger

Start a flow on any event.

Pick the events you care about and the trigger fires your workflow the instant they happen — no polling. Every request is HMAC-SHA256 signed and timestamped, so n8n can verify it really came from post mate.

webhook payload
{
  "type": "post.published",
  "data": {
    "post_id": "post_01HSXF…",
    "platform": "instagram",
    "external_url": "https://instagr.am/p/…"
  }
}
post.published

A post successfully publishes to a network — one event per network.

post.failed

A post fails to publish after retries — with the platform error.

post.scheduled

A post moves into the scheduled state.

post.cancelled

A scheduled post is cancelled.

account.connected

A new social account is connected to the workspace.

account.disconnected

A social account is disconnected.

Workflow recipes

Wire it up in an afternoon.

A few flows teams build on day one. Every node here is either post mate or a standard n8n node — no glue code.

Blog → everywhere

New RSS item kicks off an AI caption, then schedules across five networks.

RSS
Caption
Schedule

Failure → ticket

A failed post opens an issue and pings the on-call channel instantly.

post.failed
Create issue
Slack

Daily metrics → Sheets

Every morning, pull yesterday's analytics into a spreadsheet.

Schedule
Analytics
Sheets

Approve in Slack → publish

A Slack approval triggers the scheduled post to go out the door.

Slack
Schedule
Setup

Connected in three steps.

01

Mint an API key

In post mate, open Settings → API and create a full-scope key (pm_live_…). Shown once — copy it.

02

Add credentials in n8n

Create a post mate credential with that key (and your base URL if self-hosting). Reuse it across every node.

03

Drop a trigger or node

Add the post mate Trigger to start on events, or the post mate node to act — then map fields and hit Execute.

Two ways to build

Two ways to connect.

Pick whichever fits your setup. Both connect to the same API — the community node just removes the manual wiring.

HTTP Request + Webhook nodesWorks today
Use n8n's built-in nodes: a Webhook node as the trigger (paste its URL into a post mate webhook), and an HTTP Request node for actions, with a Header Auth credential.
HTTP Request node
  Method: POST
  URL: https://post-mate.com/v1/posts
  Auth: Header → Authorization
        Bearer pm_live_•••
  Body: { caption, platforms, scheduled_at }
post mate community nodeWorks today
Install n8n-nodes-post-mate from the community registry — one-click operations and a self-registering trigger, no manual webhook wiring.
Settings → Community Nodes → Install
  npm:  n8n-nodes-post-mate

+ post mate            (actions)
+ post mate Trigger    (events)

Self-hosting n8n?Point credentials at your own base URL and you're set. The same API key works for n8n Cloud, Desktop and self-hosted — and it's the exact key that powers our MCP and REST integrations.

What we're building next

The native node, in stages.

The REST-and-webhook path works now. Here's what turns it into a first-class, one-click n8n experience.

On the roadmap
Soon

Verified community node

Publish n8n-nodes-post-mate to npm and get it verified, so it installs on n8n Cloud with one click.

Soon

Self-registering trigger

A POST /v1/webhooks endpoint so the trigger node creates and tears down its own webhook — no manual setup in Settings.

Soon

AI sub-nodes in /v1

Expose caption, hashtag and translate generation under the Bearer-auth /v1 surface so they're first-class node operations.

Soon

Approval-gate node

A node that pauses a flow until a post is approved in the dashboard or Slack, then resumes — human-in-the-loop publishing.

Soon

Analytics polling trigger

A trigger that fires when a post crosses a metric threshold (e.g. 1k views) so flows can react to performance.

Soon

Workflow templates

Ship the recipes above as importable n8n templates and a public template-library listing.

n8n integration FAQ.

Do I need to write any code?

No. With n8n's HTTP Request and Webhook nodes you build the whole flow visually — paste your API key as a header credential and a webhook URL into post mate. The dedicated post mate community node (coming) removes even that wiring.

Does it work with self-hosted n8n?

Yes. The integration is just our REST API plus outbound webhooks, so it works identically on n8n Cloud, n8n Desktop and any self-hosted instance. Point the credential's base URL at your setup and you're done.

How are the triggers secured?

Every webhook from post mate is HMAC-SHA256 signed with a secret you set, and carries a timestamp. Verify the signature in n8n (or let the trigger node do it) and reject anything older than five minutes to block replays.

What can a workflow do to my posts?

Whatever your API key's plan allows: schedule, reschedule, cancel, read the queue and analytics, generate captions and upload media — across all 13 networks. The same publishing guardrails and quotas as the dashboard apply.

Which plan do I need?

The REST API and webhooks are part of the API add-on (included on Pro). One key powers n8n, MCP and direct REST calls; you can rotate or revoke it any time from Settings.

Is there a rate limit?

Yes — sensible per-key limits keep a runaway workflow from flooding your feeds. Webhook deliveries retry with exponential backoff (up to five attempts) and every send is visible in your 30-day delivery log.

Is the post mate node available now?

The REST-and-webhook path is live today and does everything. The packaged community node and the self-registering trigger are on our roadmap — see the section above.

Stop doing it by hand.
Let the workflow run.

Mint an API key, drop a webhook in n8n, and your content pipeline runs itself — publish, caption, measure, repeat.

Get an API keyBrowse recipes