Post to social media from n8n
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 LinkedIn, Bluesky, Mastodon, YouTube and TikTok — one endpoint instead of 5 separate OAuth integrations.
Free · No credit card · No trial timer
Use the HTTP Request node with a Header Auth credential. One POST publishes or schedules to every connected platform at once.
- How it connects
- REST API via HTTP Request node
- Publishes to
- LinkedIn, Bluesky, Mastodon, YouTube and TikTok
Connect n8n in 5 minutes
Create an API key
In Schedule & Chill, go to Settings → API Keys and generate a key.
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.
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.
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.
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
{
"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 and cannot do
What you 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}
Where it stops
- 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 people build with it
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.
n8n questions
Use the HTTP Request node to POST to https://schedulenchill.com/api/posts with an Authorization: Bearer header. Send content and social_account_ids in the JSON body. One request reaches every connected platform, so you do not need a separate node or OAuth app per network.
Yes. The API is a plain HTTPS endpoint, so self-hosted and cloud n8n behave identically. Your instance only needs outbound HTTPS access.
Upload the file to the media library first (POST /api/media, or the resumable upload endpoints for large video), then pass the returned id in media_ids on the post request.
Not yet. The REST API works with the built-in HTTP Request node, which needs no installation and works on both n8n Cloud and self-hosted instances.
Yes. Include scheduled_at as an ISO 8601 timestamp in the future. Omit it and add publish_now: true to send immediately. Schedule & Chill owns the queue, so your n8n workflow does not need to stay running until the publish time.
The post object lists every targeted account with its own delivery status and error message. A post can be partially published — some accounts succeed, others fail — and you can retry the failed ones from the dashboard.
Last reviewed July 26, 2026
Connect a different tool
Wire n8n up in 5 minutes
It is free — no card, no trial timer. Make real API calls, connect your account, and see it work.
Start freeFree · No credit card · No trial timer