How every connection works
Credentials you supply, and can revoke.
Scoped to the permissions shown beside it.
Off until one of your administrators turns it on.
Read-only unless you enable a write, and writes need approval.
What we connect to, and what it reads.
Eleven boundaries, ten shipping and one on the roadmap. Each one says what crosses it and what stays where it is.
Your CRM
Salesforce
Microsoft Dynamics 365 (coming soon)
Accounts, contacts, opportunities and leads in, with field mapping and import rules you write. Writes back only the fields you enable, only after a person approves the change. Salesforce ships today; Dynamics 365 is the next connector on the roadmap.
Your finance system
Sage (coming soon)
QuickBooks (coming soon)
On the roadmap: invoices and payments from your finance system, beside the account they belong to. Neither connector ships today.
Your warehouse
PostgreSQL
Direct database connectors
Product usage read straight from your own store, with no analytics vendor in the path.
Calendar
Microsoft 365
Google Calendar
Each person authorizes their own calendar. Eligible customer meetings are found automatically. You set the lookahead and whether the recorder is scheduled for them.
Customer email
Microsoft 365
Outlook
Authorized customer email under a privacy policy you set, with its own domain matching and sync monitoring.
Outbound mail
Google Workspace
Microsoft 365
Amazon SES
Send platform mail through your own provider, with OAuth or an app password, so notifications come from your domain.
Meetings
Microsoft Teams
Zoom
Google Meet
Native rooms
Connectors contribute metadata and transcripts. Recording comes only from our own recorder, visibly named in the room, after someone attests to consent.
Conversations
Gong
Slack
Gong transcripts imported alongside native capture. Slack is opt-in per channel. We do not crawl what you have not linked.
Support
Freshdesk
Zendesk
Jira Service Management
ServiceNow CSM
Tickets feed the health score directly, with severity and SLA behavior.
Documents
Amazon S3
SharePoint
Documents you upload are stored in Amazon S3 in our AWS account, encrypted at rest. SharePoint is reference-only: we hold a pointer and your own permissions still decide who opens it.
Identity
Microsoft Entra ID
Keycloak
SSO through Microsoft Entra ID, with email-domain discovery and enforced SSO where you require it. Ferent Sign-in runs on Keycloak, with multi-factor authentication your administrator can require.
Something missing from that list?
Tell us which system and what you need out of it. We would rather say no early than describe a connector that does not exist yet.