Production-grade read and write paths for the systems your SDR team already lives in. Bidirectional, idempotent, residency-aware. Click any tile to connect or inspect.
AEs14Meetings · 7d96Lock contention0 eventsp95 book441 ms
connected
Other systems · bring your own
implementation team builds via internal MCP · 5–10 days
Stack we don't list above? Close, Attio, internal lead-scoring services, real-time inventory or pricing APIs, account research in Notion or Coda — our implementation team plugs them in via our internal tool interface. You don't author or maintain anything; we do. Most custom integrations land in a week.
Connect · Salesforce
Sign in
1Sign in
2Scopes
3Field map
We'll redirect you to Salesforce to sign in. Production org or sandbox supported.
Salesforce edition
We use OAuth 2.0 with refresh tokens stored in our EU vault. We never request your password. You can disconnect any time and we tear down the integration cleanly.
Review what celliq can read and write. You can refine these later per object.
Read · leads, contacts, accounts, opportunities
used by brief builder for pre-call context (spec §6.1)
Write · activities (call logs)
one activity per call · idempotent on call_id
Write · contact & lead custom fields
structured qual fields from CallOutcome · per-field validation
Write · opportunities (create / update / reopen)
only when CallOutcome.next_steps[] includes opportunity intent
Read · routing rules
live tool · get_assigned_ae · resolves AE per routing
We've matched your custom Salesforce fields to celliq's CallOutcome contract. Auto-mapped · 11. One needs your attention.