oper8r Docs
Customer-facing implementation guide
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.
Salesforce is usually connected through OAuth by an administrator.
Typical setup uses:
| Salesforce object | oper8r use |
|---|---|
Account | Account identity, domain, owner, segment, region, and hierarchy. |
Contact | Stakeholder identity, title, email, account association, and owner. |
Opportunity | Stage, amount, close date, owner, forecast, renewal, and expansion context. |
Lead | Prospect identity and early pipeline context where used. |
User | Owner and team routing. |
Task or Event | Touchpoint context when enabled. |
Use Salesforce IDs as external IDs whenever possible.
{
"name": "Acme Corp",
"type": "account",
"externalIds": [
{
"provider": "salesforce",
"id": "0018c00002abcDEF",
"type": "Account"
}
]
}
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"
}
]
}
}'
Bring us the workflow, integration, or deployment constraint. We can build it with you, run it for you, or advise your team.