n8n

When you finish this page an n8n workflow creates a post on a connected account through the Zernio node, with no HTTP node to configure. You need an API key, a connected account and n8n Cloud or a self-hosted n8n.

The node covers these resources:

The Posts resource covers 9 of the platforms POST /v1/posts accepts. WhatsApp, Reddit, Discord, Slack, Snapchat, Google Business Profile and Telegram have no entry in the node's platform picker; reach them from n8n with the built-in HTTP Request node against POST /v1/posts (Create post), using the same API key credential.

Step 1: Install the node

cd ~/.n8n/nodes && npm install n8n-nodes-zernio

Step 2: Create a post

1. Add a Zernio node.
2. Set Resource to Posts.
3. Set Operation to the target platform, for example Add Post to Twitter/X.
4. Pick the Profile and the Social Account from the dropdowns.
5. Enter the Content.
6. Set the scheduled time to publish later, or leave it empty to publish now.

Each platform has its own operation and fields:

Map values from earlier nodes with n8n expressions: {{ $json.postText }} from a Google Sheets, RSS or Code node into Content, {{ $json.publishDate }} (ISO 8601) into the scheduled time, {{ $json.imageUrl }} into Media URLs.

Step 3: Schedule a post

Set the scheduled time to a future timestamp and the post publishes then. To compute it, put a Code node before the Zernio node:

const tomorrow = new Date();
tomorrow.setDate(tomorrow.getDate() + 1);
tomorrow.setHours(9, 0, 0, 0);

return [{ json: { scheduledFor: tomorrow.toISOString() } }];

Then map {{ $json.scheduledFor }} into the scheduled time.

Step 4: Upload media

For files under 4 MB, set Resource to Media and Operation to Upload, and pass the file from a previous node (HTTP Request, Google Drive, Read Binary File). For larger files, run the Presign operation first, upload the file to the URL it returns, then use the media URL in the post. Size limits and per-platform requirements are in the media uploads guide.

Step 5: Receive events

Add a Zernio node with Resource set to Webhooks, enter your n8n webhook URL and select the events. Receive them with a Webhook trigger node.

The payloads are documented under webhooks. A post.failed event feeding a Slack or email node is the usual failure alert.

Workflow examples

Daily posting from a content calendar: Schedule Trigger at 9:00 every day, Google Sheets reads the next row, Zernio creates the post from the row's content, platform and media.

RSS to social: Schedule Trigger every hour, RSS Feed Read on your blog feed, IF checks for new items, Zernio posts them to X and LinkedIn.

AI pipeline: Schedule Trigger daily, HTTP Request fetches topics, OpenAI writes a version per platform, Zernio posts each one. Prebuilt templates for these are at zernio.com/n8n-templates.

If it fails

A 429 from the Zernio node means your team hit its request limit (rate limits). On the node, open Settings and set Retry on Fail with Max Tries 3 and Wait Between Tries (ms) 2000, and space high-volume runs with the Schedule Trigger interval or Wait nodes between batches. For every other failure, an Error Workflow (a workflow with an Error Trigger node, selected under Settings in the main workflow) receives the error and can notify you.

Related

• Zernio node on n8n
• Workflow templates
• Source code and the npm package
• API keys
• API reference