Integrations overview
Opulent works through APIs where they exist and through the screen where they do not, so a system without an API is not left out.
Integrations give a run governed access to business and developer systems. Access is granted per system and per action, and reading is granted separately from writing.
Two paths reach a system. Where an API exists, the run uses it: faster, cheaper, and easier to verify. Where one does not, Computer Use drives the interface the way a person would. The second path is what keeps a legacy system from blocking a workflow.
What connects
| Category | Examples |
|---|---|
| Messaging and intake | Slack, Microsoft Teams, Outlook, email, webhooks |
| Work tracking | Linear, Jira, GitHub, GitLab, Asana, ClickUp |
| CRM and revenue | Salesforce, HubSpot, Apollo, Clay, Attio |
| Finance and ERP | NetSuite, SAP, Stripe, QuickBooks, Xero, Bill |
| Documents and storage | Google Drive, Google Docs and Sheets, Notion, Confluence, Dropbox, Box, Excel |
| Data and analytics | Snowflake, Databricks, Postgres, dashboards |
| Monitoring and incident | Datadog, Sentry, PagerDuty |
| Specialized tools | Any MCP server your team runs |
Grant the smallest set the task requires. A recurring automation should carry an explicit tool allowlist rather than every connection available to the organization.
Where results land
What a run writes lands in your system of record. The point of connecting a CRM is not to produce a report about the CRM; it is for the record to be correct afterwards, with a read-back confirming the write.