Push experiences into CortexDB from any of Zapier's 6,000+ apps using Webhooks by Zapier.
Zapier Integration
Use Webhooks by Zapier as the action step in any Zap to call CortexDB's /v1/experience endpoint.
Configure
- In a Zap, add Webhooks by Zapier → POST.
- URL:
https://api-v1.cortexdb.ai/v1/experience - Headers:
| Key | Value |
|---|---|
Authorization | Bearer YOUR_CORTEX_TOKEN |
X-Cortex-Actor | service:zapier (or per-Zap actor) |
Content-Type | application/json |
- Body (JSON):
{
"scope": "org:acme/source:zapier",
"modality": "imported",
"content": {
"kind": "text",
"text": "{{1.event_text}}"
},
"context": {
"observed_at": "{{zap_meta_human_now_iso}}",
"labels": ["zapier", "{{1.trigger_app}}"]
},
"idempotency_key": "zap-{{zap_meta_id}}-{{1.id}}"
}
Zapier's per-run zap_meta_id plus the source event's id give a stable idempotency key — replays from Zapier's retry mechanism write once.
Common Zap shapes
- Gmail → CortexDB — capture every email matching a filter as a
documentexperience. - Calendly → CortexDB — capture booked meetings as
observationexperiences. - Stripe → CortexDB — capture invoice events as triples (
content.kind=triple).
See also
- POST /v1/experience
- Make.com — similar pattern, often cheaper for high-volume Zaps