CodivUpload + Make — Automate Social Media Workflows
Connect CodivUpload to Make using our REST API. No native module needed — just an HTTP Request module with your API key and you can trigger cross-platform publishing from any Make scenario.
How it works
Three steps from zero to publishing.
Get your API key
Dashboard → Settings → API Keys → Generate. Copy the key — it's shown once.
Add an HTTP module
In your Make scenario, add Make an HTTP request. Search for 'HTTP' in the module picker. No CodivUpload app needed.
Configure and activate
Method: POST, URL: api.codivupload.com/v1/posts, Headers: Authorization Bearer, Body: JSON with your post fields.
Airtable record created → publish to 12 platforms
A social media manager adds a record to Airtable with the video URL, caption, scheduled date, and target platforms. Make triggers on the new record, formats the data, and sends an HTTP Request to CodivUpload — which handles queuing, token refresh, and multi-platform delivery without any further involvement.
Exact Make module configuration
Copy this into your HTTP Request module. Use Make's data mapping (curly braces notation) to pull values from previous modules dynamically.
Method: POST
URL: https://api.codivupload.com/v1/posts
Headers:
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Body (Raw / JSON):
{
"profile_name": "my-brand",
"post_type": "video",
"platforms": ["tiktok", "instagram", "youtube"],
"media_urls": ["https://cdn.example.com/video.mp4"],
"description": "Automated from Make!",
"youtube_type": "shorts"}Why the HTTP module is actually better
Skipping a native module is a deliberate advantage.
No module approval wait
Make app submissions go through a review process. HTTP module works immediately — same day you sign up.
Every API parameter accessible
Third-party Make apps often expose 5-8 fields. The HTTP module lets you pass all 50+ parameters, including tiktok_post_mode, youtube_type, and platform-specific overrides.
Map any field dynamically
Make's data mapping works seamlessly with HTTP module. Pull caption from Airtable, media URL from Google Drive, and platforms from a dropdown — all wired to the JSON body.
Stable across Make updates
HTTP module is a Make core component — it's never deprecated. Your scenario works regardless of what changes in the CodivUpload app ecosystem.
Coming soon: A native Make app is on our roadmap. Until then, the HTTP module gives you full API access with zero limitations — and migrating to the native app later will be optional, not required.
Make + CodivUpload: How It Works
Make (formerly Integromat) is a visual automation platform that connects apps through modules arranged in a scenario. CodivUpload integrates with Make through the built-in HTTP module — not a native app, and intentionally so. The HTTP module is a core Make component available on every plan, including the free tier.
The integration pattern follows Make's standard data flow: a trigger module detects an event (new Airtable record, incoming webhook, RSS item, scheduled timer), passes structured data through optional routers and transformers, and reaches an HTTP module configured to call POST https://api.codivupload.com/v1/posts. CodivUpload receives the request and handles everything downstream — job queueing, OAuth token refresh for expired platform credentials, and parallel delivery to up to 10 social networks.
Make's visual scenario builder makes this particularly powerful. You can use Router modules to split a single trigger into multiple CodivUpload API calls — for example, sending one version of a post with a video to TikTok and YouTube, and a different version with a static image and longer caption to LinkedIn and Twitter/X. Each branch can pass different platform-specific overrides like tiktok_privacy_level or youtube_type while sharing the same API key and profile.
Because Make processes scenarios in real-time or on a schedule (configurable from every 15 minutes down to instantly on paid plans), you can build workflows that respond to events within seconds. A new product added to your Shopify store can trigger a promotional post across all 12 platforms before your team even reviews it — or you can add a manual approval step using Make's built-in tools.
RSS Feed to Social Media — Auto-Distribute New Articles
Monitor any blog or news RSS feed and automatically publish each new article to your connected social platforms. This scenario is ideal for content marketers who repurpose blog content across social channels.
RSS module detects a new feed item. Make's RSS trigger polls the feed URL at your configured interval and captures the article title, summary, link, and any attached image or enclosure URL.
Make parses and transforms the data. A Text Parser module extracts a clean summary from HTML content. A Set Variable module formats the caption — combining the title, a short excerpt, and the article URL into a social-ready description.
HTTP module calls CodivUpload. The module sends a POST request to api.codivupload.com/v1/posts with the formatted body. The image from the RSS enclosure maps to media_urls, and platforms are set to your preferred channels.
Multi-platform publish completes. CodivUpload delivers the article as native posts on Twitter/X, LinkedIn, Facebook, Instagram, Threads, Bluesky, Pinterest, TikTok, and YouTube — each with the correct format for that platform.
Setting Up the HTTP Module
Here is the detailed configuration for Make's "Make an HTTP request" module. This works on all Make plans.
URL & Method
In the module settings, set the URL to https://api.codivupload.com/v1/posts and the method to POST. Make sure "Parse response" is toggled on — this lets you use the CodivUpload response (post ID, status) in downstream modules for logging or conditional branching.
Headers
Add two header rows. First: name Authorization, value Bearer YOUR_API_KEY (replace with the API key from CodivUpload Dashboard > Settings > API Keys). Second: name Content-Type, value application/json. For production scenarios, store the API key in a Make Data Store or use Make's Connections feature to avoid exposing it in the scenario blueprint.
Body (JSON Template)
Set the body type to Raw and content type to JSON (application/json). Use Make's curly-brace mapping to pull dynamic values from previous modules. Required fields: profile_name, post_type, platforms (array), and description. Add media_urls for image or video posts, and scheduled_at (ISO 8601) for future scheduling.
Error Handling
Add an error handler route to the HTTP module. Use a Resume directive for 429 (rate limit) errors with a retry delay of 10 seconds. For 4xx validation errors, use a Rollback directive that logs the error to Google Sheets or sends a Slack notification with the failed payload for manual review. Make's built-in retry settings support up to 3 automatic retries.
Related resources
Cross-Post to 12 Platforms
Learn how CodivUpload distributes a single post to every major social network in one API call.
API Documentation
Full reference for all 50+ parameters, authentication, error codes, and rate limits.
All Integrations
See how CodivUpload connects with n8n, Zapier, MCP, and other automation tools.
Ready to automate your Make scenarios?
Free plan: 2 profiles, 10 uploads/month. No credit card required.