Skip to main content
n8n is an open-source workflow automation tool. The official community node package, @social-media-scheduler/n8n-nodes-social-media-scheduler, lets an n8n workflow create and schedule posts, manage drafts, upload media, read your connected accounts, and react to publishing events.

The two nodes

The package ships two nodes. Both use the same Social Media Studio API credential.

Operations

Posts and drafts can go to Twitter/X, Instagram, LinkedIn (personal and Page), Facebook, TikTok, YouTube, Threads, Pinterest, Dribbble, Bluesky, Mastodon, WordPress, Dev.to, Discord, and Slack. The available post types and options depend on the destination account.

Trigger events

The Trigger node manages its own webhook subscription. It registers a subscription when you activate the workflow and removes it when you deactivate the workflow. It checks the HMAC-SHA256 signature of each delivery and answers HTTP 401 to a missing or wrong signature. See Webhook payloads for the body of each event.
Social media studio must be able to reach your n8n webhook URL. A self-hosted n8n instance on localhost needs a public URL (for example a tunnel) before the Trigger node can receive events.

Authentication

Both nodes use one API key credential.
1

Create an API key

In the Social media studio dashboard, go to Settings → API Keys and create a key. See Authentication for details.
2

Add the credential in n8n

In n8n, create a new Social Media Studio API credential and paste your key. n8n sends the key in the X-API-Key header and tests it when you save the credential.
Keep the default Base URL (https://api.so-me.studio) unless you run your own Social media studio backend.

Installation

1

Open Community Nodes

In n8n, go to Settings → Community Nodes → Install.
2

Install the package

Enter @social-media-scheduler/n8n-nodes-social-media-scheduler and confirm. The Social Media Studio and Social Media Studio Trigger nodes appear in the nodes panel.
For a self-hosted n8n instance, you can also install it directly:
n8n requires Node.js 20 or later to run community nodes.
This is not a verified community node, so it is available on self-hosted n8n only. n8n Cloud does not offer unverified community nodes.

Example: publish a post with an image

1

Upload the image

Add a Social Media Studio node with Media → Upload to Library. Set Binary Property to the binary field that holds the image. The node uploads and verifies the file and returns its file ID.
2

Pick the account

Add a second Social Media Studio node with Post → Create. Set Platform and Post Type, then select the destination in Account Name or ID.
3

Attach the image and schedule

Put the file ID from step 1 in Media Library File IDs, write the Text, and set Schedule For. Leave Schedule For empty to publish now.
Run Media → Validate before you schedule a post. It checks each file against the rules of each destination and tells you which files a platform will refuse.

Threads and first comments

Post → Create, Update, and Schedule, and Draft → Create, Update, and Convert to Post, have Thread Parts and First Comment fields. The Text field is the first part of the thread, and the thread parts follow in order. Threads work on Twitter/X, Threads, Bluesky, and Mastodon.

TikTok

Before you post to TikTok, run Social Account → Get TikTok Creator Info and choose one of the privacy levels that it returns. TikTok refuses a post without an allowed privacy level.

n8n templates

Five ready-to-import workflows. Each uses only the published node plus n8n’s built-in nodes; the yellow sticky note on each canvas lists what to change. Download a file, then in n8n open Workflows → Create workflow → ⋯ → Import from File. Open each node that shows a warning and select your credential. The RSS and analytics templates also need an n8n Header Auth credential (Name X-API-Key, Value: your API key) for the HTTP Request node. Setup notes for every template are in the templates README. The same files are kept in the Social media studio monorepo under apps/n8n-node/templates/.

Other automation tools

No native Zapier or Make app exists yet. Both can call the same REST API and receive the same webhooks: see Zapier and Make.