CodivUpload + Zapier — Connect Social Media to 5,000+ Apps
Connect CodivUpload to Zapier using our REST API. No native Zapier app needed — Webhooks by Zapier plus your API key is all it takes to trigger multi-platform publishing from any app on Zapier.
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.
Use Webhooks by Zapier
In your Zap, add a 'Webhooks by Zapier' action. Choose 'POST' as the event. No CodivUpload Zapier app required.
Configure and turn on
URL: api.codivupload.com/v1/posts, Header: Authorization Bearer, Payload Type: JSON, Data: your post fields.
New WordPress post → cross-post to 12 platforms
Every time you publish a post on WordPress, Zapier detects it, extracts the featured image URL and excerpt, then sends a Webhooks by Zapier POST to CodivUpload. Within seconds the content is queued for TikTok, Instagram, YouTube Shorts, LinkedIn, and any other platforms you configured.
Exact Zapier webhook configuration
Add this to your Webhooks by Zapier action. Use Zapier's data fields (wrapped in curly braces) to pull values from the trigger step dynamically.
Method: POST
URL: https://api.codivupload.com/v1/posts
Headers:
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Payload Type: json
Data:
{
"profile_name": "my-brand",
"post_type": "video",
"platforms": ["tiktok", "instagram", "youtube"],
"media_urls": ["https://cdn.example.com/video.mp4"],
"description": "Auto-posted via Zapier!",
"youtube_type": "shorts"}Why Webhooks by Zapier is actually better
A native Zapier app would constrain what you can do. Here's why the webhook approach wins.
Available before an official app exists
Getting a Zapier app approved takes months. Webhooks by Zapier is available on every Zapier plan and works immediately.
Full API access, not a subset
Official Zapier integrations expose the fields the developer hardcoded. Webhooks by Zapier lets you pass all 50+ CodivUpload parameters — tiktok_post_mode, youtube_type, and every platform override.
Connects to 5,000+ apps on day one
Any Zapier trigger — WordPress, RSS by Zapier, Notion, HubSpot, Typeform — pairs directly with Webhooks by Zapier. Every app on Zapier is instantly an input for CodivUpload.
No dependency on third-party maintainers
If an unofficial CodivUpload Zapier app were abandoned, your Zaps would break. Webhooks by Zapier is a Zapier core action — it will never disappear.
Coming soon: A native Zapier app is on our roadmap. In the meantime, Webhooks by Zapier gives you full API access with no field limitations — and migrating to the native app later will be your choice, not a necessity.
Zapier + CodivUpload: How It Works
Zapier connects apps through trigger-action pairs called Zaps. CodivUpload integrates with Zapier through the "Webhooks by Zapier" action — not a native Zapier app, and this is by design. Webhooks by Zapier is a core Zapier feature available on all paid plans, giving you direct HTTP access to any REST API without waiting for a dedicated integration.
The pattern works like this: any Zapier trigger (a new row in Google Sheets, a new email in Gmail, a form submission in Typeform, a new entry in Notion) fires your Zap. The data from that trigger flows through optional Filter or Formatter steps, then hits a "Webhooks by Zapier" action configured to POST to https://api.codivupload.com/v1/posts. CodivUpload takes over from there — queueing the post, refreshing any expired OAuth tokens for your connected social accounts, and delivering the content to up to 12 platforms simultaneously.
What makes Zapier particularly valuable for CodivUpload is its trigger library. With 5,000+ apps available as triggers, virtually any business event can initiate social media publishing. A customer leaves a 5-star review on Trustpilot, a new product is added to your Shopify catalog, a team member updates a Notion database, or a HubSpot deal closes — each of these can automatically generate and publish social content through CodivUpload without your marketing team lifting a finger.
The Webhooks by Zapier action supports all CodivUpload API parameters, including platform-specific overrides. You can map Zapier data fields directly to JSON body values — for example, using the trigger's image URL as media_urls, the title as description, and setting youtube_type to "shorts" or tiktok_privacy_level to "public_to_everyone" based on the trigger data.
Notion Database Row to Social Media — Content Calendar Automation
Your content team manages a Notion database as their editorial calendar. When a row's status changes to "Ready to Publish," Zapier automatically sends the post to all configured social platforms via CodivUpload. No manual copy-pasting, no logging into multiple platforms.
Notion trigger fires. Zapier's "Updated Database Item" trigger detects when a row's "Status" property changes to "Ready to Publish." The trigger captures the page title, caption field, media URL, and target platforms from the Notion database columns.
Zapier formats the data. A Formatter step cleans up the caption text (removing Notion formatting artifacts) and a Filter step confirms the status is exactly "Ready to Publish" to prevent duplicate posts from other status changes.
Webhooks by Zapier calls CodivUpload. A POST request hits api.codivupload.com/v1/posts with the Notion data mapped to JSON fields. The platforms array, media URLs, and caption are all pulled from the trigger output.
Content publishes across 12 platforms. CodivUpload queues the post, refreshes expired tokens, and delivers it to Twitter/X, Instagram, Facebook, LinkedIn, TikTok, YouTube, Threads, Bluesky, Pinterest, Google Business Profile, and Snapchat. Your team's Notion row becomes live social content in seconds.
Setting Up Webhooks by Zapier
Here is the detailed configuration for the "Custom Request" action in Webhooks by Zapier. This works on Zapier Starter, Professional, Team, and Company plans.
Action Event & URL
When adding the action step, search for "Webhooks by Zapier" and select Custom Request as the event (not "POST" — Custom Request gives you more control over headers and body format). Set the method to POST and the URL to https://api.codivupload.com/v1/posts.
Headers
In the Headers field, add two key-value pairs. First: Authorization set to Bearer YOUR_API_KEY (get your key from CodivUpload Dashboard > Settings > API Keys). Second: Content-Type set to application/json. Zapier stores these headers securely and reuses them across Zap runs.
Request Body
In the Data field, enter your JSON body. Use Zapier's field mapping (click the "+" button) to insert dynamic values from the trigger step. Required fields: profile_name, post_type (text, image, video, reel), platforms (array of platform names), and description. For media posts, include media_urls as an array. You can also add scheduled_at with an ISO 8601 timestamp to schedule posts for the future instead of publishing immediately.
Testing & Error Handling
After configuring the action, click "Test step" to send a real request to CodivUpload. A successful test returns a 200 status with the created post ID. If you see a 401, double-check your API key. If you see a 422, review the JSON body for missing required fields. For production Zaps handling high volumes (RSS feeds, bulk imports), add a Zapier Delay step of 2 seconds between iterations to stay within the 60 requests/minute rate limit. Zapier also supports "Auto Replay" — failed tasks are automatically retried for up to 7 days.
Related resources
Cross-Post to 12 Platforms
Learn how CodivUpload distributes a single post to every major social network in one API call.
MCP for Social Media
Discover how the Model Context Protocol works with CodivUpload for AI-driven publishing workflows.
API Documentation
Full reference for all 50+ parameters, authentication, error codes, and rate limits.
Ready to connect CodivUpload to 5,000+ Zapier apps?
Free plan: 2 profiles, 10 uploads/month. No credit card required.