Workflow automation integration

n8n Social Media Posting

n8n can publish to social media through the Schedule & Chill REST API using the built-in HTTP Request node. POST to https://schedulenchill.com/api/posts with a bearer token and your workflow can schedule to X, LinkedIn, Facebook, Instagram, YouTube, TikTok, and Pinterest — one endpoint instead of seven OAuth integrations.

5 minutes setup
REST API via HTTP Request node

Last updated July 26, 2026

Quick Answer

n8n + Schedule & Chill in one line

Use the HTTP Request node with a Header Auth credential. One POST publishes or schedules to every connected platform at once.

How to connect n8n

5 minutes from API key to first post

1

Create an API key

In Schedule & Chill, go to Settings → API Keys and generate a key.

2

Add a Header Auth credential in n8n

Credentials → New → Header Auth. Set the name to Authorization and the value to Bearer YOUR_API_KEY. Reuse this credential across every node that talks to the API.

3

Find your account IDs

Add an HTTP Request node with GET https://schedulenchill.com/api/capabilities (or call GET /api/posts) to discover the connected accounts and note their ids. You only need to do this once.

4

Add the posting node

HTTP Request → POST https://schedulenchill.com/api/posts with a JSON body containing content and social_account_ids. Add scheduled_at for a future post, or publish_now: true to send immediately.

5

Trigger it from anything

Chain it after an RSS Feed Read, a Google Sheets row, a webhook from your app, or an AI node that drafts the copy. n8n handles the trigger; Schedule & Chill handles delivery.

HTTP Request node — JSON body

Copy this into your n8n setup and replace the ids with your own.

{
    "method": "POST",
    "url": "https://schedulenchill.com/api/posts",
    "authentication": "genericCredentialType",
    "genericAuthType": "httpHeaderAuth",
    "sendBody": true,
    "specifyBody": "json",
    "jsonBody": {
        "content": "{{ $json.summary }}",
        "social_account_ids": [789, 790],
        "scheduled_at": "{{ $json.publishAt }}",
        "platform_content": [
            { "account_id": 790, "content": "{{ $json.linkedinVersion }}" }
        ]
    }
}

What n8n can do

  • Publish immediately or schedule for a future time
  • Fan one workflow out to every connected platform in a single request
  • Per-platform copy overrides with platform_content
  • Attach images and video from the media library with media_ids
  • Read back per-account delivery status with GET /api/posts/{id}
  • Cancel a scheduled post with DELETE /api/posts/{id}

What to know first

  • There is no official n8n community node yet — you use the generic HTTP Request node, which means you write the JSON body yourself.
  • Media has to be in the Schedule & Chill media library first. Upload it via POST /api/media (or upload_media over MCP) and pass the returned id.
  • Accounts are connected once in the dashboard via OAuth; n8n cannot complete that flow.

What teams build with it

Common n8n workflows that end in a published post

RSS to every platform

RSS Feed Read → AI node rewrites the headline per platform → HTTP Request posts it. Your blog auto-syndicates without a scheduler subscription per seat.

Spreadsheet content calendar

Read a Google Sheet of dated posts on a schedule trigger, then POST each row with its scheduled_at. Non-technical teammates fill the sheet; n8n does the rest.

Product events to social

A webhook from your app fires on a new release, customer milestone, or changelog entry, and the workflow announces it across channels automatically.

Frequently asked questions

n8n and social posting — what builders ask

Wire n8n up today

Start your free trial, generate an API key, and make your first call in minutes. Card required, cancel anytime.

Start Free Trial

7-day free trial · Card required · Cancel anytime