About the integration

The Social media studio community node for n8n is published on npm as @social-media-scheduler/n8n-nodes-social-media-scheduler. It adds an action node that creates, schedules, updates and retries posts, manages drafts, uploads and validates media and lists your connected accounts, plus a trigger node that starts a workflow when a post is created, scheduled, published or fails, or when a draft becomes a post.

What you can automate with n8n

n8n is where many teams already wire their tools together. With the node installed, publishing to your social accounts becomes one more step in a workflow instead of a separate tab, whether the content comes from a feed, a spreadsheet, a form or an AI model.

  • Create, schedule, update, retry and delete posts on every publishing destination you have connected
  • Save posts as drafts for review, then convert a draft into a scheduled post
  • Upload images and videos, and check each file against the destination's media rules before posting
  • Add thread parts, a first comment or TikTok privacy options to a post
  • Start workflows when a post is created, scheduled, published or fails, when a draft is converted, or when a quota limit is reached

How to set it up

Install the package on a self-hosted n8n instance, then add one credential with an API key from your workspace. Both nodes share that credential.

  1. 1In n8n, open Settings → Community Nodes, choose Install and enter @social-media-scheduler/n8n-nodes-social-media-scheduler. Only an owner or admin of the n8n instance can install nodes.
  2. 2In Social media studio, open Settings → API and create an API key. Only workspace owners can create keys.
  3. 3In n8n, create a Social media studio API credential and paste the key. The node sends it as the X-API-Key header.
  4. 4Add the Social media studio node for actions, or the Social media studio Trigger node to start a workflow when an event fires.

Example n8n workflows

  • Blog post to scheduled social posts

    An RSS trigger picks up a new article, an OpenAI node writes a short caption, and two Post → Create steps schedule it on LinkedIn and X a few hours later.

  • Content calendar in Google Sheets

    A Google Sheets trigger reads each new row with the caption, platform and date, and Post → Create schedules the post for the time in that row.

  • New YouTube video to LinkedIn and X

    Your channel's RSS feed starts the workflow on each upload, and two Post → Create steps share the video link to LinkedIn and X.

  • AI-written caption as a draft for approval

    A form supplies the topic, an AI model writes the caption, and Draft → Create saves it so a teammate checks it before Draft → Convert to Post schedules it.

  • Alert the team when a post fails

    The Trigger node listens for Post Failed, and a Slack node posts the details to a channel so someone can fix the post and retry it.

Your data is safe

Your API key is stored as an n8n credential and sent only to the Social media studio API. A key acts on one workspace, and a workspace owner can revoke it at any time from Settings → API. Deliveries to the Trigger node are signed, so forged requests are rejected.

Get support

The n8n guide on docs.so-me.studio covers every operation and field. Stuck on a setup step? Check the Help Center.

Documentation

Related integrations

Yes. The node is open source under the MIT license. It calls the Social media studio REST API, which every paid plan includes. The Trigger node uses webhooks, which start on the Creator plan.

n8n Cloud only offers community nodes that n8n has verified; other community nodes need a self-hosted n8n instance. If the node is not available in your Cloud workspace, call the REST API with n8n's HTTP Request node instead.

The node's platform list covers Instagram, TikTok, LinkedIn profiles and Pages, X, YouTube, Facebook, Threads, Pinterest, Bluesky, Mastodon, Dribbble, WordPress, Dev.to, Discord and Slack. WhatsApp and Telegram are messaging only, so they can't receive posts.

When you activate the workflow, the Trigger node registers a webhook subscription and stores its secret. Every delivery is signed with HMAC-SHA256 in the X-Webhook-Signature header, and the node rejects requests whose signature does not match.

Yes. Every operation is a REST call to https://api.so-me.studio/v1 with your key in the X-API-Key header, so the HTTP Request node also covers endpoints the community node leaves out, such as the inbox and analytics.

Schedule once.
Post everywhere.

Stop juggling tabs, draft, customize, and publish to 20 platforms from a single calendar.

n8n Social Media Automation: Node, Setup & Examples