OrcLink
← Help Center

Call tracking

CallRail

Send post-call webhooks to OrcLink. OrcLink checks each one with your CallRail signing token.

Built, not yet tested liveBuilt. Not yet tested against a live CallRail 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 > CallRail: paste CallRail signing token, then Connect. It is stored encrypted and never shown again.
  • Send completed calls to https://<your OrcLink host>/api/webhooks/callrail/<workspace id> (the Integrations card shows the exact URL).
  • Paste the CallRail signing token: OrcLink checks the Signature header of every webhook with it.

What OrcLink reads

  • Post-call and call-modified webhooks: times, duration, result, tracking number, the caller number (hashed on receipt).

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.
  • CallRail does not send a webhook again: a delivery OrcLink could not store is lost.