Zapier Social Media Scheduler: Connect via Webhooks

Get your API key →  Works with Zapier today, via Webhooks.

SchedPilot does not have a native Zapier app yet. You can still schedule posts from any Zap using Webhooks by Zapier, which calls the SchedPilot API directly — here is the exact configuration.

Set up the action

Add Webhooks by Zapier → Custom Request as the action step in your Zap:

Field	Value
Method	POST
URL	https://api.schedpilot.com/developers/v1/post
Data Pass-Through?	No
Headers	X-API-KEY = your key · Content-Type = application/json

Put this in the Data field, mapping your trigger’s fields into content:

{
  "content": "{{your_trigger_field}}",
  "date": "2026-08-11",
  "time": "09:30",
  "timezone": "America/New_York",
  "accounts": [{"id": 1234, "type": "twitter"}]
}

Get your account id and type once from GET https://api.schedpilot.com/developers/v1/accounts and paste them in. Set "post_instant": true instead of date/time to publish the moment the Zap fires.

Typical Zaps

• New row in Google Sheets → schedule a post
• New RSS item → publish to LinkedIn and X
• Airtable record marked “approved” → queue for a specific time
• Form submission → post immediately

Being straight with you

A webhook step is more setup than a native integration, and Zapier will not autocomplete your account IDs. If you have not committed to Zapier, n8n and Make are the smoother paths — and n8n is self-hostable if cost matters. A native Zapier app is something we would rather build than fake.

If your Zap involves AI

Agents do not need Zapier at all. Install schedpilot-mcp, set SCHEDPILOT_TOKEN, and Claude or any MCP-compatible agent gets create_post, upload_media, and four more tools directly.

Rate limits apply to Zaps like anything else: 30 writes and 60 reads per hour, per user. API access is on every plan from $21/month.

Get your API key →  |  Create Post reference  |  Pricing