CRM

CRM integrations give oper8r the commercial system of record for account, contact, opportunity, owner, and pipeline context. CRM data is most useful when joined with call recordings, Drive documents, Slack context, websites, and the shared employee graph.

Supported CRM Patterns

Other CRM and ATS systems can be supported through customer-specific engagements when the workflow requires them.

What CRM Data Supports

CRM context is useful for:

Account briefs.
Renewal and expansion prep.
Pipeline and forecast risk.
Stakeholder coverage.
Owner mapping.
Prior deal precedent.
Customer and prospect history.
External IDs for graph entity resolution.

Typical Objects

Object	Why it matters
Account or company	The commercial organization and account anchor.
Contact	Stakeholder identity, role, and relationship context.
Opportunity or deal	Pipeline stage, amount, close date, owner, and risk context.
Owner	Internal accountability and routing.
Activity	Recent touchpoints and follow-up context when available.

External IDs

Preserve CRM IDs when curating the employee graph. Stable external IDs let oper8r connect the same account or person across CRM, Slack, calls, Drive files, and workflow outputs.

{
  "name": "Acme Corp",
  "type": "account",
  "externalIds": [
    {
      "provider": "salesforce",
      "id": "0018c00002abcDEF",
      "type": "Account"
    },
    {
      "provider": "hubspot",
      "id": "982734",
      "type": "company"
    }
  ]
}

Setup Checklist

Confirm the CRM system of record.
Confirm objects in scope.
Approve read-only scopes first.
Import a small set of accounts or opportunities.
Validate account/contact/deal matching.
Connect calls, Drive files, Slack, and website/docs content as needed.
Decide which durable CRM facts belong in the employee graph.

Supported CRM Patterns

What CRM Data Supports

Typical Objects

External IDs

Setup Checklist

Related Docs

Talk to oper8r