Integrations

oper8r integrations connect the systems your team already uses: CRM, call recordings, Slack, Drive files, websites, documentation, and agent clients. The goal is not to mirror every field. The goal is to bring the right source-backed context into workflows that people actually use.

Integration Categories

Connection Principles

• Connect only approved systems.
• Use least-privilege scopes.
• Prefer read-only access unless a write workflow is explicitly approved.
• Keep provider credentials out of graph facts, prompts, and skill files.
• Preserve stable external IDs so records can be joined across systems.
• Document what data is shared, private, customer-facing, or out of scope.

Typical Setup Path

1. Identify the workflow and source systems.
2. Confirm security and deployment requirements.
3. Connect the integration in oper8r or through the managed deployment process.
4. Import a small, reviewable sample.
5. Validate retrieval quality and citations.
6. Decide what belongs in the shared employee graph.
7. Roll out to the team with docs, skills, or Slack/MCP/API surfaces.

Example Integration Map

Workflow: Renewal account brief

Sources:
- HubSpot or Salesforce for account, opportunity, owner, and stage.
- Gong or Fathom for recent call themes.
- Google Drive for approved decks, notes, and security docs.
- Slack for internal commitments or escalations where approved.
- Website/docs crawl for current product and public account context.

Output:
- Cited account brief.
- Stakeholder and risk summary.
- Suggested next actions.
- Optional employee graph updates for durable facts.

Next Pages

• Slack
• Google Drive
• Call Recordings
• CRM
• Webscraping