Social Media Automation in Make
Publish to Instagram, YouTube, TikTok, LinkedIn, X, Facebook, Threads, Pinterest, Reddit, Bluesky, Google Business, Discord, Telegram, Slack, Mastodon and WordPress from a single HTTP module in any Make scenario — no per-platform connector babysitting.
Why use IndReelForge inside Make?
Make has dozens of native social-media modules — but each one is a separate connector with its own auth, its own rate limits, and its own quirks. Worse, most of them only support one network at a time, so a fan-out scenario quickly becomes a tangle of routers and aggregators. IndReelForge collapses all of it into a single HTTP module with one Authorization header. Pass an array of platform names, the post is published everywhere.
Prerequisite — IndReelForge setup
Three things you need from your IndReelForge dashboard before you wire up Make.
Step 1
Create a profile
In your dashboard create a profile (e.g. main). Its name becomes the user field on every API call.
Step 2
Connect socials
Open the profile and click Connect next to each network. Each profile holds one account per network — TikTok, Instagram, YouTube and so on.
Step 3
Generate an API key
From the API Keys page, create a key (2FA must be on). Copy it once — you'll paste it into a Make constant in the next section.
Configure the HTTP module
Six clicks inside Make and your scenario can publish to every connected social account.
- 1
Add the HTTP module
In your scenario, click + and pick HTTP → "Make a request". Drop it after whichever module produces the content you want to publish.
- 2
Set Method = POST and URL
Method: POST. URL: https://api.indreelforge.com/api/upload (use /api/upload_photos for image carousels and /api/upload_text for text-only posts).
- 3
Add the Authorization header
Toggle "Headers" on. Add a header named Authorization with value "Apikey {{constants.UPLOAD_POST_API_KEY}}". Store the actual key as a Make constant in your team settings — never inline.
- 4
Set body type to multipart/form-data
Under "Body type" pick "multipart/form-data". This is required because uploads include a binary file alongside text fields.
- 5
Add the form fields
See the field reference below. Add user, title, one platform[] entry per network, and a "video" field set to type Binary mapped to the file from the previous module.
- 6
Save & test
Click "Run once". A 200 response with { "success": true, "upload_id": "..." } means the post is queued. Failed networks come back inside platform_statuses with per-network error messages.
Form-data field reference
Required and optional fields the HTTP module sends to /api/upload.
| Field | Value | Required |
|---|---|---|
user | Your profile name (e.g. main) | Required |
title | Caption / video title text | Optional |
platform[] | tiktok, instagram, youtube, …(repeat once per network) | Required |
video | Binary file (from previous module)(type: Binary) | Required |
Pro tip — store the key as a constant
In Make, go to your team → Constants → Create. Name it UPLOAD_POST_API_KEY. Reference it everywhere as {{constants.UPLOAD_POST_API_KEY}}. Exported scenario blueprints will reference the constant by name, never the value.
Security — treat the key like a password
Don't paste the API key into a Slack message or commit it to git. If you ever leak one, revoke it from the API Keys page in your dashboard and roll a new one — old keys stop working instantly.
Multi-platform fan-out
Add platform[] three times if you want to post to TikTok, Instagram and YouTube simultaneously. One operation in Make, one upload record on IndReelForge, three published posts.
Common gotchas
platform[]must be a repeated field, not a comma list.- Free plan can't post to TikTok — upgrade to Basic+ first.
- Max video size is 500 MB. Larger files return 413.
Example scenarios you can build today
Real Make.com patterns the IndReelForge team has shipped — copy as starting points.
Watch a Google Drive folder
Drop a video into a Drive folder. Make picks it up, sends it to IndReelForge with your default caption, and writes the resulting upload_id back to a Google Sheet.
Airtable approval queue → fan-out
Editors stage posts in Airtable with a "Publish" checkbox. Make polls every minute, sends approved rows to IndReelForge with the schedule_at field, and flips the row to "Queued".
OpenAI caption + 16-network fan-out
Generate a caption with the OpenAI module, then a single HTTP module fans the same post out to all 16 networks. No router, no aggregator, no per-platform connector.
Webhook → instant cross-post
Trigger from a custom webhook (CMS publish, Stripe purchase, GitHub release). Reformat the payload, hit the IndReelForge HTTP module, and the announcement lands on every channel within seconds.
FAQ
How do I connect Make.com to IndReelForge?
In your Make scenario, add an HTTP > "Make a request" module. Set Method = POST and URL = https://api.indreelforge.com/api/upload, then add an Authorization header with the value "Apikey YOUR_API_KEY". Set body type to multipart/form-data and add fields for user, title, platform[] and your video binary. One module replaces a separate connector for every social network.
Does Make.com have a native IndReelForge module?
A native modular app is on the roadmap. Today, the recommended setup is the generic HTTP module — it gives you full access to every IndReelForge endpoint (upload, schedule, analytics, comments) without waiting on connector updates and works with every Make plan including the free Core tier.
How do I avoid hardcoding my API key into the scenario?
Use Make's constants / variables feature. Create a constant called UPLOAD_POST_API_KEY in your team settings, then reference it in the Authorization header as "Apikey {{constants.UPLOAD_POST_API_KEY}}". When you export or share the scenario blueprint, the actual key never leaves your account.
Can I post to multiple platforms in one Make module?
Yes. Add the platform[] field multiple times in the form-data body — once for each network. Make supports duplicate field names by clicking the "Add item" button under the same parameter. IndReelForge fans the post out to every listed platform in one call.
How does pricing scale with high-volume Make scenarios?
Make charges per operation (one HTTP request = one operation). IndReelForge's paid plans are unlimited-upload, so even if your scenario runs hundreds of times per day your IndReelForge bill is flat. The combination is dramatically cheaper than per-post pricing on legacy schedulers.
Explore More
Other automations
Supported platforms
Plug IndReelForge into Make in under 5 minutes
Start free with 10 uploads per month, no credit card required. Upgrade to unlimited when your scenario scales.