Zapier
WCP integrates with Zapier via the Webhooks by Zapier and Code by Zapier built-in apps. No custom Zapier app is needed.
Trigger a Sync from Zapier
Section titled “Trigger a Sync from Zapier”Use Webhooks by Zapier → POST as an action step:
| Field | Value |
|---|---|
| URL | https://workflowcontextprotocol.info/api/sync/run/await |
| Payload Type | json |
| Data | (leave empty — no body needed) |
| Headers | Content-Type: application/json |
The response JSON contains synced, errors, conflicts, duration_ms — all available as variables in subsequent Zap steps.
Example Zaps
Section titled “Example Zaps”1. Sync every time a Notion page is updated
Section titled “1. Sync every time a Notion page is updated”Trigger: Notion → Page updated ↓Action: Webhooks → POST /api/sync/run/await ↓Filter: only continue if errors = 0 ↓Action: Slack → Send message "Notion sync complete: {{synced}} items"2. Alert on sync conflicts
Section titled “2. Alert on sync conflicts”Trigger: Schedule → Every 30 minutes ↓Action: Webhooks → GET /api/conflicts?status=pending ↓Filter: only continue if response body is not empty ↓Action: Gmail → Send email "WCP has {{count}} unresolved conflicts"3. Auto-resolve conflicts (source wins)
Section titled “3. Auto-resolve conflicts (source wins)”Trigger: Schedule → Every hour ↓Action: Webhooks → GET /api/conflicts?status=pending ↓Action: Code by Zapier → loop over conflicts array ↓Action: Webhooks → POST /api/conflicts/{{conflict_id}}/resolve Body: {"winning_app": "notion"}Reading the Response
Section titled “Reading the Response”Zapier automatically parses JSON responses. After a POST /api/sync/run/await, you can reference:
| Variable | Value |
|---|---|
synced | Number of entities synced |
errors | Number of errors |
conflicts | Number of new conflicts detected |
duration_ms | Sync duration in milliseconds |
Limitations
Section titled “Limitations”- Zapier doesn’t support WebSockets, so you can’t receive push events from WCP’s
/wsendpoint directly. Use scheduled polling instead (see examples above). - For real-time event handling, use n8n which includes a native WCP Trigger node with WebSocket support.
All Useful Endpoints
Section titled “All Useful Endpoints”| Action | Method | URL |
|---|---|---|
| Run sync & wait | POST | /api/sync/run/await |
| Run sync (background) | POST | /api/sync/run |
| Get sync status | GET | /api/sync/status |
| List pending conflicts | GET | /api/conflicts?status=pending |
| Resolve conflict | POST | /api/conflicts/{id}/resolve |
| List connections | GET | /api/connections |
| List recent logs | GET | /api/logs?limit=20 |