Post to social media from Make.com
Make.com can publish to social media through the Schedule & Chill REST API using the built-in HTTP "Make a request" module. Point it at https://schedulenchill.com/api/posts with a bearer token and one module schedules to LinkedIn, Bluesky, Mastodon and YouTube — instead of maintaining a separate Make connection per network.
Free · No credit card · No trial timer
Use the HTTP module with an Authorization header. One request publishes or schedules across every connected account.
- How it connects
- REST API via HTTP module
- Publishes to
- LinkedIn, Bluesky, Mastodon and YouTube
Connect Make.com in 5 minutes
Create an API key
In Schedule & Chill, go to Settings → API Keys and generate a key.
Add an HTTP module to your scenario
Search for HTTP → Make a request. Set the method to POST and the URL to https://schedulenchill.com/api/posts.
Set the headers
Add Authorization with the value Bearer YOUR_API_KEY, Content-Type: application/json, and Accept: application/json.
Build the body
Choose Raw body type, JSON content type, and map your scenario data into content and social_account_ids. Add scheduled_at for a future post.
Run once and check
Make shows the 201 response with the created post. The socialAccounts array carries a per-account delivery status you can route on.
HTTP module — raw JSON body
{
"content": "{{1.title}} — read the full post: {{1.url}}",
"social_account_ids": [789, 790],
"media_ids": [456],
"scheduled_at": "{{formatDate(addHours(now; 3); \"YYYY-MM-DDTHH:mm:ss\")}}Z",
"platform_content": [
{ "account_id": 790, "content": "{{1.longFormVersion}}" }
]
}What Make.com can and cannot do
What you can do
- Publish now or schedule for later from any scenario
- One module reaches all connected platforms
- Per-platform copy overrides with platform_content
- Attach media library assets with media_ids
- Route on per-account delivery status in the response
- Cancel a scheduled post with a DELETE request
Where it stops
- There is no official Make app in the marketplace yet — you use the generic HTTP module and map the JSON yourself.
- Media must already exist in the media library; upload it first and pass the returned id.
- Account connections are made once in the dashboard via OAuth and cannot be completed from a scenario.
What people build with it
Airtable content calendar
Watch an Airtable base for rows marked Ready, then post each one at its scheduled time. Your team plans in Airtable; Make ships it.
AI-generated posts on a timer
A scheduled scenario calls an AI module for fresh copy, then hands it to the HTTP module. Consistent output without a person in the loop.
E-commerce product announcements
A new Shopify product triggers the scenario, which builds the caption from product fields and announces it on every channel.
Make.com questions
Add an HTTP "Make a request" module, POST to https://schedulenchill.com/api/posts, set an Authorization: Bearer header with your API key, and send content plus social_account_ids as a raw JSON body. One module covers every connected platform.
Yes. Pass scheduled_at as an ISO 8601 timestamp in the future. Schedule & Chill holds the post in its own queue and publishes it, so your scenario finishes immediately and does not consume operations while waiting.
The response lists every targeted account with its own status and error message. Add a router after the HTTP module to branch on failures and notify your team.
Not yet. The REST API works with the built-in HTTP module, which requires no installation and no connection approval.
Yes. Posting to five networks with native modules costs at least five operations. One HTTP request to Schedule & Chill fans out to all connected accounts and costs one.
Yes, via media_ids. Upload the asset to the media library first with a multipart POST to /api/media, then reference the id it returns.
Last reviewed July 26, 2026
Connect a different tool
Wire Make.com 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