Start from the scenario you already have
Use a CMS event, form, CRM update, scheduler or product event as the trigger. PostSider only needs to handle the publishing step.
Make.com + PostSider
Connect Make.com to a social media publishing API
Let Make orchestrate the scenario and use PostSider for the last mile: connected social accounts, scheduling and publishing from one API.
Start with the social media scheduler API or browse the full developer platform.
How it works
One HTTP module is enough to hand the post to PostSider.
Keep your existing Make scenario intact. The social step becomes a normal API request rather than a chain of provider-specific modules.
Add an HTTP module
Call the PostSider public API from Make with the API key in the Authorization header and JSON as the request body.
Choose draft, schedule or publish
Use the publishing mode that matches the workflow. Draft is useful when a person still needs to review the copy.
Keep the post visible after the scenario runs
The result stays in the PostSider calendar and can also be read through the API by later steps in the scenario.
Concrete example
A practical Make HTTP module setup
The endpoint and headers stay the same across scenarios. Map the content, target channel and publish mode from whatever modules ran earlier.
Make scenario -> HTTP > Make a request
Method: POST
URL: https://api.postsider.com/public/v1/posts
Body type: Raw / JSON
Headers:
Authorization: {{POSTSIDER_API_KEY}}
Content-Type: application/json
Request content:
Map values from earlier modules into the current
PostSider request body documented in the API reference.Related developer guides
Go deeper where your workflow needs it.
Social media automation API See how PostSider fits into CMS, backend, cron and automation workflows. Read more → PostSider + Zapier The same HTTP pattern works from a Zap when Zapier is your orchestration tool. Read more → PostSider + n8n Use ready-made n8n workflow files when you want a more code-friendly automation setup. Read more →
FAQ
Common questions.
Can Make.com publish social media posts through PostSider?
Yes. Add an HTTP module to the scenario and call the PostSider public API with your API key.
Do I need a separate Make module for each social network?
No. Make talks to PostSider; the individual social accounts are connected inside PostSider.
Can the scenario create drafts for approval?
Yes. A draft-first workflow is useful when generated or templated copy needs a human review before publication.
Can another Make module run after the post is created?
Yes. Use the API response immediately, or webhooks/API state when a later step depends on the final publishing result.