Zapier

The Jelliu app for Zapier turns events in your workspace into Zap triggers: a call ends, a contact converts, a campaign finishes. Zapier subscribes to the event, and Jelliu POSTs each occurrence to Zapier as it happens.

The app works in one direction only: Jelliu tells Zapier what happened. It has triggers and no actions. If you want your agents to act inside the apps you have connected to Zapier (create a CRM deal, add a spreadsheet row) during a conversation, connect Zapier MCP to your agents instead. See Hosted automation providers.

How it works

The Zapier API key

Zapier authenticates with its own credential, separate from workspace API keys:

Generate a key

In the dashboard, open Integrations → Zapier → Generate API Key. The key is shown once. Jelliu stores only a keyed hash of it, so a lost key cannot be recovered; generate a new one.

Generating and revoking Zapier keys is restricted to the workspace owner, in a signed-in dashboard session. The underlying endpoints (POST /api/zapier/api-key and DELETE /api/zapier/api-key/{id}) refuse workspace API keys, even full ones, with 403 FORBIDDEN:

This action requires a signed-in admin session — API keys cannot perform credential-management operations.

That way a leaked jl_ key cannot mint a long-lived zk_ credential that would survive revoking it.

Revoke a key

Revoke the key in the same dashboard screen. From then on, requests carrying it receive 401.

Connect Jelliu in Zapier

Triggers

duration is in seconds. outcome is a string such as sale_closed, callback_scheduled, no_answer or voicemail, and can be null when there is no analysis. Treat every field as optional.

Delivery

For every active subscription whose event matches, Jelliu sends:

POST {target_url} HTTP/1.1
Content-Type: application/json
X-Zapier-Event: call.completed
X-Zapier-Delivery-Id: 3f1c2b9a-8d4e-4f6a-9b1c-2e3d4f5a6b7c

{
  "event": "call.completed",
  "timestamp": "2026-09-14T15:42:07.318Z",
  "data": {
    "callId": "5b0d2f7e-9a41-4c3e-8f0a-2c6d1e7b9a10",
    "campaignId": "0f3c8b52-6d1a-4e2f-9b7c-4a5e6d7f8a90",
    "contactId": "a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d",
    "agentId": "7c1d9f30-5e2a-4a7e-9c8f-91a0b1c2d3e4",
    "phoneNumber": "+573001234567",
    "outcome": "callback_scheduled",
    "sentimentScore": 0.6,
    "duration": 184,
    "summary": "El cliente pidió que lo llamen el jueves en la tarde."
  }
}

The Jelliu Zapier app adds an id to each record (the callId, contactId or campaignId from data).

Endpoints

The Zapier app calls these for you. You can also call them directly, for example to feed the same REST Hooks into your own automation tool.

All /zapier/* endpoints authenticate with x-zapier-api-key.

Subscribe

POST /zapier/subscribe

curl -sS -X POST "https://api.jelliu.co/zapier/subscribe" \
  -H "x-zapier-api-key: $JELLIU_ZAPIER_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "event": "call.completed",
    "target_url": "https://hooks.example.com/jelliu/call-completed"
  }'

Response 201:

{
  "data": {
    "id": "c9a4e1f2-3b5d-4c6e-8f7a-9b0c1d2e3f4a",
    "event": "call.completed",
    "target_url": "https://hooks.example.com/jelliu/call-completed"
  }
}

Keep data.id: it is what you pass to unsubscribe.

Unsubscribe

DELETE /zapier/subscribe/{id}

curl -sS -X DELETE "https://api.jelliu.co/zapier/subscribe/c9a4e1f2-3b5d-4c6e-8f7a-9b0c1d2e3f4a" \
  -H "x-zapier-api-key: $JELLIU_ZAPIER_KEY"

Response 200:

{ "data": { "removed": true } }

An unknown or already removed id returns 404 with code SUBSCRIPTION_NOT_FOUND and the message Zapier subscription not found.

Sample data

GET /zapier/triggers/{event}?limit=10

Returns the newest records for the event as a flat JSON array, without a data wrapper, which is the shape Zapier expects. limit accepts 1 to 100 and defaults to 10. A page parameter is accepted and ignored.

curl -sS "https://api.jelliu.co/zapier/triggers/call.completed?limit=3" \
  -H "x-zapier-api-key: $JELLIU_ZAPIER_KEY"

[
  {
    "id": "5b0d2f7e-9a41-4c3e-8f0a-2c6d1e7b9a10",
    "status": "completed",
    "outcome": "callback_scheduled",
    "duration_seconds": 184,
    "call_direction": "outbound",
    "created_at": "2026-09-14T15:39:03.120Z",
    "campaign_id": "0f3c8b52-6d1a-4e2f-9b7c-4a5e6d7f8a90"
  }
]

How samples are selected:

List subscriptions

GET /api/zapier lists the workspace’s Zapier rows. Unlike the endpoints above, it is part of the REST API: authenticate with a workspace API key (read is enough).

curl -sS "https://api.jelliu.co/api/zapier" \
  -H "Authorization: Bearer $JELLIU_API_KEY"

{
  "data": [
    {
      "id": "c9a4e1f2-3b5d-4c6e-8f7a-9b0c1d2e3f4a",
      "tenant_id": "9f0fafb4-1c2d-4e5f-8a9b-0c1d2e3f4a5b",
      "event": "call.completed",
      "target_url": "https://hooks.zapier.com/hooks/standard/123456/abcdef/",
      "is_active": true,
      "last_delivered_at": "2026-09-14T15:42:07.512Z",
      "delivery_count": 42,
      "failure_count": 0,
      "last_error": null,
      "created_at": "2026-09-01T10:00:00.000Z",
      "updated_at": "2026-09-14T15:42:07.512Z",
      "deleted_at": null
    }
  ]
}

Rows whose event is __api_key__ represent generated Zapier API keys, not subscriptions; their id is what the dashboard revokes. The key itself is never returned.

Errors

Limits

• 50 per workspace, keys and subscriptions combined. Every active Zapier API key and every active subscription counts toward the same ceiling of 50. Remove Zaps you no longer use.
• Rate limit. /zapier/* accepts 200 requests per minute per client IP.
• No plan gate. The Zapier triggers are available on every plan.

Related