CRM

SugarCRM

Pull SugarCRM lead statuses and opportunity stages into OrcLink outcomes, matched back to the ad click.

Built, not yet tested liveBuilt. Not yet tested against a live SugarCRM 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 > SugarCRM: paste SugarCRM connection: instance URL|API user name|password, then Connect. It is stored encrypted and never shown again.
Paste one value: instance URL|user name|password of a dedicated read-only API user.

What OrcLink reads

Lead statuses and opportunity stages, every 10 minutes while the scheduled jobs crm-sync and jobs run (your OrcLink operator schedules them).

What OrcLink writes back

Nothing. You add a text field orclink_click_id to Leads (and Contacts) in Studio.
Write-back of source and campaign to SugarCRM: not available yet.

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.
When you connect, OrcLink reads the last 90 days as history: stored and counted, never sent to ad platforms as new events.
Map each CRM stage to a stage of your outcome dictionary (Outcomes > Stages). An unmapped stage is recorded at the entry stage and never sent.