Connectors
Connectors give a workspace read access to your source systems. Any workspace member can connect and manage them under Connectors in the sidebar. Once connected, they are shared: chat, reports, and agents in that workspace can query the system live.
Chat and reports only ever read through a connection. Agents can be granted more than read access per capability, always subject to their permission policy.
Available connectors
| Connector | Type | How it connects |
|---|---|---|
| Apaleo | Operations | OAuth. You choose which supported data areas to grant. Can also feed source-system events to agent triggers. |
| Google Analytics | Web analytics (GA4) | Service-account JSON key plus the GA4 property ID. |
| Productivity | OAuth. | |
| Microsoft 365 | Productivity | OAuth. |
| Brevo | Email marketing / CRM | API key. |
| LIKE MAGIC | Customer operations | API client credentials. |
| PostgreSQL | Database | Host and credentials. The connection is tested before it is saved. |
| SFTP / FTP | File servers | Host and credentials (SFTP, FTPS, or FTP). Usable both as a data source and as a delivery target for report files. |
Custom integrations let you bring your own APIs and MCP servers into a workspace, so agents and chat can work with systems that are not in the catalog. Coming soon: Notion, Stripe, HubSpot, Mailchimp.
Slack and Microsoft Teams are deliberately not on this page: they carry results out rather than data in, and live under Channels.
Connection health
If a connection loses its authorization (for example, access was revoked in the source system or the granting user left), a banner appears at the top of the app with a Reconnect action. Runs that needed the connection fail visibly in the run history rather than delivering wrong data, and everything resumes once reconnected.
Each connector's page also offers a test that verifies the connection end to end.