Prerequisites
- Postsiva Pro plan with API key
- Zapier plan that includes Webhooks (usually Professional+)
- Connected social accounts in Postsiva
Authentication pattern
Every Zapier HTTP call needs:
Store the key in Zapier Storage or an environment variable — never hardcode in shared Zaps.
Zap 1: New row → LinkedIn post
Trigger: Google Sheets — New Spreadsheet Row Action: Webhooks by Zapier — POSTZap 2: Typeform → draft for review
Save as draft instead of publishing immediately:POST /unified/drafts/{id}/publish.
Zap 3: Code step for multi-platform
When you need logic (truncate for Bluesky, add Page IDs): Trigger: Any app Action: Code by Zapier (Python)Zap 4: Schedule from Airtable
Trigger: Airtable — New Record Action: Webhooks POSTPublishAt must be ISO 8601 UTC (e.g. 2026-07-10T14:30:00Z).
Zap 5: Check connection status daily
Trigger: Schedule by Zapier — Every Day Action: Webhooks GETMixed draft + publish
Usedraft_platforms in a Code step:
Handling responses
Postsiva returns per-platform results in multi-platform posts:success fields.
Limitations
MCP for AI Zaps
For AI-heavy workflows, consider n8n with MCP or Cursor with Postsiva MCP instead of Zapier Code steps. See n8n integration and MCP overview.Related
cURL recipes
Shell examples
Authentication
API key scopes