oper8r Docs

Salesforce

Customer-facing implementation guide

Back to overview

Salesforce can provide account, contact, opportunity, lead, owner, and activity context for oper8r workflows. The exact object model depends on your Salesforce configuration, but the integration pattern is consistent: connect with approved scopes, read the records needed for the workflow, preserve stable IDs, and join those records with calls, documents, Slack context, and the oper8r graph.

Connection Pattern

Salesforce is usually connected through OAuth by an administrator.

Typical setup uses:

  • API access.
  • Refresh token or offline access when approved.
  • Read access to selected objects.
  • Optional write access only for explicitly approved workflows.

Common Objects

Salesforce objectoper8r use
AccountAccount identity, domain, owner, segment, region, and hierarchy.
ContactStakeholder identity, title, email, account association, and owner.
OpportunityStage, amount, close date, owner, forecast, renewal, and expansion context.
LeadProspect identity and early pipeline context where used.
UserOwner and team routing.
Task or EventTouchpoint context when enabled.

Example Account Anchor

Use Salesforce IDs as external IDs whenever possible.

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

Example Opportunity Context Request

curl -X POST "https://YOUR_OPER8R_HOST/api/tools/org/YOUR_ORG_SLUG/oper8r_diagnose_risk" \
  -H "Authorization: Bearer $OPER8R_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "account": "Acme Corp",
    "focus": "late-stage opportunity risk",
    "entityScope": {
      "externalIds": [
        {
          "provider": "salesforce",
          "id": "0068c00001oppABC",
          "type": "Opportunity"
        }
      ]
    }
  }'
  1. Confirm the Salesforce objects and fields needed for the workflow.
  2. Start with read-only access.
  3. Import a small group of accounts and opportunities.
  4. Validate owner, stage, amount, and close-date interpretation.
  5. Join Salesforce IDs to call, Slack, Drive, and website evidence.
  6. Only enable write-back workflows after review and audit requirements are clear.

Limitations

  • Custom objects and fields vary by customer.
  • Salesforce account hierarchies may need customer-specific mapping.
  • Opportunity stages can mean different things across business units.
  • Forecast and risk outputs should combine Salesforce with recent evidence, not rely on CRM fields alone.

Talk to oper8r

Bring us the workflow, integration, or deployment constraint. We can build it with you, run it for you, or advise your team.