Skip to main content
Zapier has no native Postsiva app yet. Use Webhooks by Zapier plus Code by Zapier (or Formatter) to call the REST API with your workspace key.

​
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:
HeaderValue
X-API-Keypsk_live_YOUR_KEY
Content-Typeapplication/json
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 — POST
FieldValue
URLhttps://backend.postsiva.com/unified/post/text
Payload typeJSON
DataSee below
{
  "platforms": ["linkedin"],
  "default_text": "{{1.Caption}}"
}
Headers: 
X-API-Key: psk_live_YOUR_KEY
Content-Type: application/json

​
Zap 2: Typeform → draft for review

Save as draft instead of publishing immediately: 
{
  "platforms": ["linkedin", "threads"],
  "default_text": "{{1.Answer}}",
  "draft": true
}
Add a second Zap with manual approval → 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) 
import requests

api_key = "psk_live_YOUR_KEY"  # Use Zapier Storage in production
caption = input_data["caption"]

# Truncate for Bluesky if cross-posting
bluesky_caption = caption[:300]

response = requests.post(
    "https://backend.postsiva.com/unified/post/text",
    headers={
        "X-API-Key": api_key,
        "Content-Type": "application/json",
    },
    json={
        "platforms": ["linkedin", "bluesky"],
        "default_text": caption,
    },
)
output = {"status": response.status_code, "body": response.text}
Map Code step output fields in a follow-up action.

​
Zap 4: Schedule from Airtable

Trigger: Airtable — New Record Action: Webhooks POST 
{
  "platforms": ["instagram"],
  "default_text": "{{1.fields.Caption}}",
  "default_image_id": "{{1.fields.MediaId}}",
  "scheduled_time": "{{1.fields.PublishAt}}"
}
PublishAt 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 GET 
URL: https://backend.postsiva.com/unified/oauth/token
Headers: X-API-Key: psk_live_YOUR_KEY
Filter: Continue only if a platform shows disconnected → send alert email.

​
Mixed draft + publish

Use draft_platforms in a Code step: 
payload = {
    "platforms": ["linkedin", "facebook", "threads"],
    "default_text": caption,
    "draft_platforms": ["linkedin"],
    "facebook": {"facebook_page_ids": [page_id]},
}
LinkedIn drafts; Facebook and Threads publish immediately.

​
Handling responses

Postsiva returns per-platform results in multi-platform posts: 
{
  "results": [
    {"platform": "linkedin", "success": true, "post_id": "..."},
    {"platform": "bluesky", "success": false, "error": "NOT_CONNECTED"}
  ]
}
In Zapier, add a Filter or Paths step to branch on success fields.

​
Limitations

LimitationWorkaround
No native OAuth in ZapierConnect accounts in Postsiva app first
File uploadUpload to Postsiva separately; pass media_id
Binary media in WebhooksUse Code step with requests multipart upload
Real-time post statusPoll GET /unified/scheduled-posts on schedule

​
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.

cURL recipes

Shell examples

Authentication

API key scopes