n8n

n8n talks to Pozy through its built-in nodes: HTTP Request for actions and Webhook for triggers. This works on n8n Cloud and self-hosted n8n, with no community node to install.

You need a Pozy API key (Developers → API keys in the dashboard) and at least one connected account.

#Create the credential

If your n8n version has no Bearer Auth type, use Header Auth with the name Authorization and the value Bearer pz_live_....

#Create a post

Add an HTTP Request node:

Body, with values mapped from earlier nodes:

{
  "content": "{{ $json.text }}",
  "platforms": [
    { "platform": "linkedin", "accountId": "6650f1c2a8b4e3d2c1b0a333" }
  ],
  "mediaItems": [
    { "type": "image", "url": "{{ $json.imageUrl }}" }
  ],
  "publishNow": true
}

Drop mediaItems for a text-only post. The response contains post._id and, per platform, status and platformPostUrl once it is live.

#Schedule for later

Replace publishNow with a time and a timezone. Compute the time in a Code node before the request:

const when = new Date();
when.setDate(when.getDate() + 1);
const day = when.toISOString().slice(0, 10);

return [{ json: { ...$json, scheduledFor: `${day}T09:00:00` } }];

{
  "content": {{ JSON.stringify($json.text) }},
  "platforms": [{ "platform": "linkedin", "accountId": "6650f1c2a8b4e3d2c1b0a333" }],
  "scheduledFor": "{{ $json.scheduledFor }}",
  "timezone": "Europe/Madrid"
}

A time without an offset is read in timezone, so this posts at 9:00 in Madrid tomorrow. See Scheduling and timezones.

#Post a file

Posts take media as URLs. For a file that only exists inside n8n (from Google Drive, an email attachment or a generated image):

1. HTTP Request: POST https://api.pozy.ai/v1/media/presign with body { "filename": "photo.jpg", "contentType": "image/jpeg" }. Keep uploadUrl and publicUrl from the response.
2. HTTP Request: PUT to {{ $json.uploadUrl }}, Authentication None, Body Content Type n8n Binary File, with header Content-Type: image/jpeg.
3. Use publicUrl in mediaItems of the create-post request.

The upload URL goes straight to storage, so it must not carry your Pozy key. See Media uploads.

#Start a workflow from a Pozy event

{
  "name": "n8n alerts",
  "url": "https://your-n8n.example.com/webhook/pozy-events",
  "events": ["post.failed", "account.disconnected"]
}

const crypto = require("crypto");
const secret = "whsec_...";                          // the endpoint secret
const raw = await this.helpers.getBinaryDataBuffer(0, "data");
const headers = $input.first().json.headers;

const expected = crypto.createHmac("sha256", secret).update(raw).digest("hex");
const given = headers["x-pozy-signature"] ?? "";
if (given.length !== expected.length || !crypto.timingSafeEqual(Buffer.from(given), Buffer.from(expected))) {
  throw new Error("Bad signature");
}

const event = JSON.parse(raw.toString("utf8"));
return [{ json: { eventId: headers["x-pozy-event-id"], ...event } }];

On self-hosted n8n, the Code node can only load crypto when the instance allows it: set NODE_FUNCTION_ALLOW_BUILTIN=crypto. Keep the secret in an environment variable or n8n credential rather than in the node where you can.

Pozy retries a delivery that does not get a 2xx within 5 seconds, so the same event can arrive twice. If a duplicate would hurt (an email, a Slack alert), store eventId and skip ids you have seen.

#Workflow ideas

• Content calendar. Schedule Trigger every morning, Google Sheets reads today's rows, HTTP Request creates one post per row with Idempotency-Key set to the row id.
• RSS to social. RSS Feed Read on your blog, IF for new items, HTTP Request creates a LinkedIn post and a shorter X post with customContent per platform.
• Failure alerts. Webhook on post.failed, then Slack or email with post.platforms[].error.
• Weekly report. Schedule Trigger on Mondays, GET /v1/analytics/dashboard?fromDate=...&toDate=..., then an email with the totals and top posts.

#Troubleshooting