Add contacts from Zapier and check outgoing updates
Last verified 2026-07-16
Integrations belong to one Workspace. Only Workspace admins can create access keys, destinations, connection checks, or retries. Support viewing is read only.
Send a contact from Zapier
Where: Settings → API & Integrations
- Create an API key and copy it once. Store it in Zapier as a secret.
- Use Webhooks by Zapier to POST JSON to /api/ingest/contacts.
- Set Authorization to Bearer followed by the workspace API key.
- Include campaignId, an idempotencyKey, and a contact object. Reusing the key returns the original stored event and does not enroll twice.
- Map standard contact fields directly. Map approved custom fields by their stable field keys, not their display labels.
Receive outgoing events
Outgoing updates are not currently available, and no release date is promised. Delivery requires the integration and its delivery safeguards to be ready.
When outgoing delivery is available, add an HTTPS webhook under API & Integrations and choose the updates it may receive. Klosent records each update before delivery and keeps the same event ID and delivery ID across retries so the receiving tool can avoid duplicates.
Test delivery validates the saved connection safely and records the result without contacting the destination. Outbound delivery remains unavailable until the integration and its delivery safeguards are ready.
- X-Integration-Event identifies the event type.
- X-Integration-Delivery is stable across automatic retries.
- X-Integration-Timestamp is the Unix signing time.
- X-Integration-Signature is v1= followed by HMAC-SHA256 of timestamp, a period, and the exact request body.
- Campaign completion updates include the exact reporting dates and explain when only part of an older campaign's history was available.
- Return any 2xx status after storing the delivery. Retries for temporary service limits wait between attempts and stop at the allowed retry limit. A timeout, unclear connection result, or receiving-service error stops for admin review so an update that may already have arrived is not sent twice.
Delivery history and safe retries
Delivery history shows the status and limited number of attempts without exposing destination secrets or message text. An admin may retry only a delivery that was confirmed rejected. The retry keeps the same event ID so the receiving tool can avoid duplicates.
Do not automatically retry a timeout, unclear connection result, receiving-service error, or item awaiting manual review. The receiving tool may already have accepted it. Check with that tool first. If you cannot confirm the outcome, contact support before taking any further action.