interaction.captured
What this event means
interaction.captured is emitted when a new interaction record is created for a contact/company thread (email, call, memo, or similar activity).
Webhook type
interaction.captured
Internal source mapping
| Internal event | Trigger path |
|---|
interaction.created | Interaction was created and saved in Klipy. |
Payload example
{
"type": "interaction.captured",
"object": "event",
"data": {
"id": "int_k8n3d1q2",
"title": "Intro call with Acme Analytics",
"summary": "Reviewed current CRM workflow and agreed to a 30-minute follow-up.",
"people": [
{
"object": "contact",
"id": "h7w8y2f1",
"first_name": "Jordan",
"last_name": "Patel",
"email": "jordan.patel@acmeanalytics.com",
"title": "Head of Growth"
}
],
"company": {
"object": "company",
"id": "cmp_a1b2c3",
"name": "Acme Analytics",
"domain": "acmeanalytics.com",
"industry": "SaaS",
"employee_count": 350,
"estimated_revenue": 1200000,
"city": "Austin",
"state": "TX",
"country": "US",
"linkedin": "https://linkedin.com/acme-analytics"
}
}
}
Delivery and idempotency handling
- Keep side effects idempotent. Interactions can be retried during delivery pressure.
- For dedupe checks, prefer
data.id, which is the interaction identifier.
people and company blocks are included for current snapshots; tolerate absent fields.
- Return
2xx only after your integration applies the interaction atomically.
Last modified on April 26, 2026