Skip to content

Make.com + PostSider

Add a verified publishing step to your Make scenario.

Your scenario owns the trigger and content. PostSider provides the connected social channels and a shared place to review drafts and publishing status. Start with a draft and a readback before adding live publishing.

Start with a working REST example, or explore the API and product use cases.

How it works

A four-step Make HTTP handoff you can reproduce.

This is a configuration recipe using ordinary Make HTTP modules. It is not a native app integration or a claim that a live customer scenario has been executed.

01

Keep your existing Make trigger

Start with a CMS event, CRM change, form entry or manual trigger. Decide what text and channel the scenario should use before it reaches the publishing step.

02

List real connected channels

Use Make HTTP > Make a request to GET /public/v1/integrations with a raw organization API key in the Authorization header. Map a returned channel ID, not a sample ID.

03

Create a draft before scheduling

Call POST /public/v1/posts using the documented JSON schema, a stable Idempotency-Key and type: draft. Configure the platform-specific settings appropriate for the channel.

04

Read the saved record back

Extract the returned post ID and call GET /public/v1/posts/:id. Verify saved content, channel and DRAFT status before adding later publishing or webhook handling.

Concrete example

Make HTTP requests: channel lookup, draft and readback

Use a secure configuration for the organization key and map your actual channel ID. The sample body is an outline; provider-specific settings and your future UTC date must be set before making the request.

Make scenario: HTTP > Make a request

01  GET https://api.postsider.com/public/v1/integrations
    Authorization: <organization API key, raw value>

02  POST https://api.postsider.com/public/v1/posts
    Authorization: <same organization API key>
    Content-Type: application/json
    Idempotency-Key: <stable source event ID>

    Body (map values in Make):
    {
      "type": "draft",
      "date": "REPLACE_WITH_FUTURE_UTC_ISO_DATE",
      "shortLink": false,
      "tags": [],
      "posts": [{
        "integration": { "id": "CONNECTED_CHANNEL_ID" },
        "value": [{ "content": "Draft for review", "image": [] }],
        "settings": {}
      }]
    }

03  GET https://api.postsider.com/public/v1/posts/:id
    Check DRAFT, content and selected destination

STOP. Check per-platform settings in the API reference.

FAQ

Common questions.

Does Make require a native PostSider module?
No. Call the REST API from a standard Make HTTP module, using a PostSider organization key. This example is a module-by-module recipe, not a downloadable native Make blueprint.
Can Make save a post without putting it live?
Yes. Use type: draft, then inspect the stored post and its state in PostSider. Do not add an immediate publish action until you have verified the intended content and destination.
Can I approve drafts from Make?
Make can create the draft, but formal team approvals happen within PostSider on Team, Pro or Ultimate. A prompt or a conditional scenario step is not an enforced PostSider approval permission.
What should I use for retries?
Keep an Idempotency-Key stable for repeated attempts of the same create action and fetch the returned post by ID. Use a new key for a genuinely new post.
Can one Make API key publish for different clients?
Organization keys belong to a PostSider organization. For separate client organizations, configure a separate subscription and credential per organization, and verify the correct key and channels at runtime.

Use the same publishing system from code

Connect the channels once. Keep the workflow in your stack.

Call REST directly, use the typed SDK, or expose the same publishing actions to an MCP-compatible agent.