About the integration

There is no native Social media studio app in Make (formerly Integromat) yet. Make's built-in HTTP and Webhooks apps cover the connection: the HTTP app's Make a request module calls the Social media studio REST API to create, schedule or draft posts, and a Custom webhook trigger receives the events Social media studio sends when posts publish, fail or get comments.

What you can automate with Make

Make scenarios are good at moving data between many apps. One HTTP step turns sheet rows, feed items or form answers into scheduled posts, and a webhook brings publishing events back into the scenario.

  • Create posts on any publishing destination you have connected, to publish now or at a set time
  • Save posts as drafts so a teammate reviews them before they are scheduled
  • Map captions, links and dates from earlier modules into the request body
  • Attach images and videos from your media library by file ID
  • Start scenarios on events such as post.published, post.failed or inbox.comment_received

How to set it up

You need an API key from a Social media studio plan that includes API access. Make's HTTP and Webhooks apps are built in, so there is nothing else to install.

  1. 1As a workspace owner in Social media studio, open Settings → API and create an API key.
  2. 2In your scenario, add the HTTP app's Make a request module with the POST method and the URL https://api.so-me.studio/v1/posts.
  3. 3Add an X-API-Key header with your key and send a JSON body with text, socialMedia (for example LINKEDIN) and postType (for example TEXT). Add scheduledAt in ISO 8601 to schedule the post instead of publishing it now.
  4. 4To start scenarios from Social media studio, add a Webhooks Custom webhook trigger, copy its address, and add it as an endpoint under Settings → Webhooks with the events you want.

Example request

This request schedules a LinkedIn post. Leave out scheduledAt to publish right away, and add accountId when more than one account is connected for that platform.

POST https://api.so-me.studio/v1/posts
X-API-Key: YOUR_API_KEY
Content-Type: application/json

{
  "text": "New on the blog: how we plan a month of posts https://example.com/blog/monthly-plan",
  "socialMedia": "LINKEDIN",
  "postType": "TEXT",
  "scheduledAt": "2026-11-02T09:00:00Z"
}

Example Make scenarios

  • New blog post to scheduled posts

    The RSS app watches your feed, and two HTTP requests schedule a LinkedIn post and an X post for each new article.

  • Google Sheets rows to scheduled posts

    A Google Sheets module watches for new rows with caption, platform and date, and an HTTP request schedules each one for the time in that row.

  • New YouTube video to LinkedIn and X

    The YouTube app watches your channel for new videos, and two HTTP requests share the link to LinkedIn and X.

  • AI-written caption as a draft for approval

    An OpenAI module writes the caption, and a POST to /v1/drafts saves it so a teammate reviews it before it is scheduled.

  • Failed post alert

    A custom webhook receives post.failed, and the scenario sends the details to Slack or email so someone can retry the post.

Your data is safe

Your API key sits in the HTTP module's headers, so limit who can edit the scenario, and revoke the key from Settings → API if it is ever exposed. Webhook deliveries are signed with your endpoint's secret.

Get support

The REST API quickstart and the webhook docs on docs.so-me.studio cover every field used here. Stuck on a setup step? Check the Help Center.

Documentation

Related integrations

Not yet. The setup on this page uses Make's built-in HTTP and Webhooks apps, which work with any REST API, so you don't need to wait for a native app.

Any paid plan, since all of them include API access. Starting scenarios from our webhooks needs Creator or above. The pricing page shows what each plan includes.

Each delivery carries an X-Webhook-Signature header, an HMAC-SHA256 of the raw body signed with your endpoint's secret. Checking it needs that exact raw body. If your scenario can't get it, keep the webhook address private and read the post from the API before acting on an event.

Yes. Keep the file in your media library and send its ID in fileIds, or upload a new file first with the presigned upload endpoints that the API reference describes.

The post is marked as failed and a post.failed webhook fires, so a scenario can alert you. You can retry it from the dashboard or with POST /v1/posts/:id/retry.

Schedule once.
Post everywhere.

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

Automate Social Media Posting With Make.com