CRM

GoHighLevel

Connect a GoHighLevel sub-account. Contacts, opportunities and appointments become outcomes by webhook.

Built, not yet tested liveBuilt. Not yet tested against a live GoHighLevel 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 > GoHighLevel > Connect, and sign in with GoHighLevel. Then set the click-id field and map the stages on the settings page.
Integrations > GoHighLevel > Connect, and sign in with HighLevel. Changes arrive by webhook to one OrcLink app URL; nothing to set up on your side.

What OrcLink reads

Opportunities, appointments and contacts. A rescheduled appointment is not a new booking.

What OrcLink writes back

A contact text field with the key olid, when OrcLink can create it.
Write-back, off by default (the Write back section of this CRM's settings page): for each new lead with a matched ad click, OrcLink finds the record by email, then phone (exact match only; no match or more than one: nothing is written) and writes that click's source, medium, campaign, term, content, channel, landing host, click id type, first and last touch time and the OrcLink outcome id into fields of the CRM (the landing path only if you tick it, never in HIPAA mode). Only empty fields, unless you turn on overwrite. A lead from a site form or chat is written only to a record created within 24 hours of that lead. The email or phone used to find the record is kept only encrypted, until the write is done and at most 24 hours. Writes run while the scheduled job jobs runs (your OrcLink operator schedules it). Never in strict consent mode, never for a visitor who refused consent or sent Global Privacy Control; in HIPAA mode only after the workspace records a BAA with this CRM.

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

Matching needs the OrcLink click id (olid) in a CRM field, filled from the hidden form field named olid; without it OrcLink matches by the hashed email or phone of a lead an earlier visit tied to a click.
Map each GoHighLevel stage to a stage of your outcome dictionary (Outcomes > Stages).