Updated 2026-06-19
Connector overview
How SmixAI connects to systems — the System → Environment → Credential model and what's supported today.
Overview
A connector lets SmixAI read a system's configuration and usage so it can find inefficiencies. SmixAI reads metadata and counts (objects, fields, automation, license and storage usage) — not your customer records. Connections are organized in three levels so you can manage multiple orgs and environments cleanly.
Key concepts
- System — a named instance you own (e.g. "Acme Salesforce").
- Environment — a deployment inside a system: production, sandbox, developer, staging, scratch, or other. Scans run per environment.
- Credential — the encrypted token/keys for an environment. One is marked primary.
Supported systems
| System | Status |
|---|---|
| Salesforce | Live — full scan + discovery |
| GitHub | Preview / planned |
| Slack | Preview / planned |
| Google Workspace | Preview / planned |
| Microsoft 365 | Preview / planned |
| ERP | Preview / planned |
| Database | Preview / planned |
Only Salesforce is connectable today. The other types appear in the product as placeholders so you can see where the platform is heading.
What data SmixAI reads
- Object and field definitions, record counts (not record contents).
- Automation and code metadata (Flows, Apex classes, validation rules, etc.).
- Org limits (data/file storage), licenses, and user activity used by discovery rules.
See Security & data handling for storage and encryption details.
Use cases
- Multiple orgs: model each Salesforce org as its own System, each with production and sandbox Environments.
- Safe-first scanning: connect and scan a sandbox before connecting production.
Next steps
- Connect Salesforce (OAuth) or server-to-server auth for automated scans.