Call tracking

Delacon

Send completed calls to OrcLink by webhook. Add the secret as a custom header or as the Basic-auth password.

Built, not yet tested liveBuilt. Not yet tested against a live Delacon account.

Live: shipped in OrcLink's production release before this one. Built, not yet tested live: built and tested with sample data, not yet run against a live account of the vendor. Coming soon: listed, not available to connect yet.

How to connect

Dashboard > Integrations > Delacon > Connect. Copy the webhook URL and the secret (shown once) into Delacon.
Send completed calls to https://<your OrcLink host>/api/webhooks/delacon/<workspace id> (the Integrations card shows the exact URL).
Send the secret as the X-Orclink-Secret header or as the HTTP Basic-auth password.

What OrcLink reads

Completed calls (JSON). Several likely field names are tried per value; a payload of another shape is ignored with a note, never guessed.

What OrcLink writes back

Nothing.

Never stored

Raw email addresses and phone numbers: hashed (SHA-256) the moment they arrive.
The raw payload: only its SHA-256, for provenance.
Your credentials and webhook secrets in clear: they are stored encrypted (AES-256-GCM).

Known limits

A call keeps a hash of the caller number, its last 4 digits, the tracking number dialled, the call times and result and a recording reference (not the audio). The full caller number only if you turn that on, never in HIPAA mode.
The field names are not yet checked against a real Delacon delivery.