n8n ​

Publish, schedule, and manage posts on 18 platforms from n8n workflows with the official community node: n8n-nodes-socifyr.

Install ​

1. In n8n: Settings → Community Nodes → Install
2. Enter n8n-nodes-socifyr
3. Reload when prompted

n8n 1.x. The node is free and open source (packages/n8n-nodes-socifyr in the Socifyr repo).

Credentials ​

Create a Socifyr API credential:

Recommended: one key per workflow, with guardrails. In the dashboard, open the shield icon on any key and set a daily post limit, an X spend cap, and/or require approval. The node inherits them automatically — a runaway workflow hits a clear 403 from Socifyr instead of spamming your accounts (or burning X budget). See Agent guardrails.

Operations ​

Content → Create

Content → Fetch: Get Content · List Content (status/type/platform filters) · Check Status (requestId)

Content → Manage: Publish Draft · Publish Now · Submit for Approval · Approve Post · Reject Post · Retry Failed · Delete Content

Useful options live under Additional Fields: scheduledAt/timezone (schedule instead of publish), saveDraft, contentFormat, platformOptions (JSON), firstComment, idempotencyKey, and async (returns a requestId immediately — pair with Check Status).

Connections, not platform names ​

Every operation takes connection slugs like instagram-mybrand or x-myhandle — the stable identifiers from Connected Accounts. Multiple values: add them as separate items in the multi-value field.

Media files ​

The node posts media by library ID or public URL. To upload a file generated upstream in n8n: add an HTTP Request node doing POST {baseUrl}/media/upload (multipart, same auth headers), take the returned media ID, and pass it into the Socifyr node's Media field.

Outputs ​

Socifyr's { success, data } envelope is unwrapped — downstream nodes see data directly, so expressions like these work as-is:

{{ $json.uploadId }}
{{ $json.requestId }}
{{ $json.usage }}

A list operation outputs one item per post.

Error handling ​

API failures throw the node with the Socifyr message (e.g. 403: API key "n8n-agent" reached its daily post limit (50/day)...). Wire a Catch branch on the node to alert or retry.

Recipe: RSS → drafted → approved → published ​

1. RSS Read → 2. Socifyr: Create Text Post → 3. Slack/Email notify with the uploadId. Turn on the key's require approval guardrail and step 2 already lands the post in pending approval — nothing publishes until a teammate approves it in the dashboard.

Related ​

• Make integration · Webhooks for publish events · Agent guardrails