Integrations
What SAGARIS connects to,
and in which direction
Every connection below is described by what actually moves through it. Where a connection reads but does not write, this page says so in the same sentence that names it. Anything we have not connected is listed at the bottom rather than left off.
CRM2
Mail and calendar5
Notifications and recordings3
Build on the API3
Statuses checked 17 Oct 2026.
Read across: what comes in, what goes back out, and the status word we measured.Read across: what comes into SAGARIS, what goes back out, and the status word we measured.
- Moves
- Dry run, not sent
- Built, not yet proven
- Nothing moves
CRM
Two CRMs connect over OAuth, against your own org or portal. Read each row across: what comes in, and what goes back.
Salesforce
Connected, reads only
Into SAGARIS
Opportunities, accounts, contacts, leads, campaigns, tasks, events, notes, email messages and cases, with field history.
Back out
Dry run. The change is computed and recorded; nothing is sent.
Status: Connected, reads only
Connect route answered 307, configured
HubSpot
Connected, reads only
Into SAGARIS
Companies, contacts, deals and tasks, then engagements, tickets, forms, email events and property history.
Back out
Dry run for deal stage, qualification properties, call logs and activity logs. Nothing is sent.
Status: Connected, reads only
Connect route answered 307, configured
Mail and calendar
SAGARIS sends from your mailbox and books on your calendar. Each row names its mechanism, because an OAuth grant and an app password are different promises.
Gmail
Available per environment
Into SAGARIS
One mailbox at a time, over OAuth. Reply-tagged, thread-context and known-contact mail.
Back out
Sends from the connected mailbox.
Status: Available per environment
Not verified with a live connect yet
Google Calendar
Connected
Into SAGARIS
Free and busy time, and existing events.
Back out
Creates, moves and cancels events. A created event carries a Google Meet link.
Status: Connected
Connect route answered 401, configured
Yahoo Mail, iCloud Mail and AOL Mail
App password
Into SAGARIS
Mail over IMAP, into the same unified inbox.
Back out
Sends over SMTP.
Status: App password
Read in code; needs a session to test
Notifications and call recordings
Both use a credential you supply rather than an OAuth grant, so you can revoke either at the source without touching SAGARIS.
Slack
Delivery only
Into SAGARIS
Nothing. SAGARIS reads nothing from Slack.
Back out
Notifications marked critical, action required or warning, to a channel you choose.
Status: Delivery only
Read in code; delivery not measured
Fireflies and Gong
Inbound only
Into SAGARIS
A finished transcript, pushed to a webhook you authenticate.
Back out
Nothing. SAGARIS does not call the recorder.
Status: Inbound only
Read in code; an unknown token gets 401
Anything else: build it on the API
If a system is not on this page, there is no connector for it. There is a documented interface, authenticated with a workspace API key you mint and revoke.
REST API
Read and write
Into SAGARIS
Contacts, deals, sequence enrolment and suppression.
Back out
The same resources, written with a scoped workspace key.
Status: Read and write
OpenAPI document route exists
Outbound webhooks
Built; delivery switched on per environment
Into SAGARIS
Nothing.
Back out
Signed events, retried with backoff, then dead-lettered.
Status: Built; delivery switched on per environment
Delivery not measured
MCP endpoint
Reads and scoped writes
Into SAGARIS
Your CRM, sequences and Brain, read by an AI client with the workspace key.
Back out
Scoped writes, each needing its own scope; three LinkedIn events.
Status: Reads and scoped writes
Endpoint answered 405, POST only
Statuses were checked on 17 Oct 2026 against the live product, or read in code where a check cannot reach them. No row shows a sync time, because none is measured.
Reads are live.
Write-back is a dry run.
Write-back is built and switched off in production by a switch on our side, a global one or a per-workspace one. SAGARIS computes the change, records it, and does not send it. That is a rollout decision of ours, not a setting in your org.
HubSpot has a working Disconnect in Settings. Salesforce does not; the button is there and disabled.
How each connection is made
The mechanism decides who holds the credential and where you revoke it. Every one of these can be revoked at the source.
CRM
- OAuth
Salesforce
OAuthFrom onboarding or the CRM screen
- OAuth
HubSpot
OAuthFrom Settings
Mail and calendar
- OAuth
Gmail
OAuthPer mailbox
- OAuth
Google Calendar
OAuthPer calendar
- App password
Yahoo, iCloud, AOL
App passwordEncrypted before it is stored
Notifications and call recordings
- Webhook or token
Slack
Webhook or tokenHost pinned to hooks.slack.com
- Inbound webhook
Fireflies and Gong
Inbound webhookA token you generate and rotate
API
- API key
REST API
API keyWorkspace key, scoped
- API key
MCP
API keySame key; each write needs its own scope
Settings · Integrations. Recorders push to the transcript URL; Slack only receives.
Not connected
What SAGARIS does not connect to
The clients are written for some of these. The connection is not open, and the connect endpoint says so when you call it. No date is published for any of them.
- 503 todayMicrosoft 365, meaning both Outlook mail and Outlook calendar: not connectedInstead: no Outlook path today.
- 503 todayCalendly: not connectedInstead: SAGARIS books on Google Calendar.
- no codePipedrive, and every CRM that is not Salesforce or HubSpot: not connectedInstead: CSV import, or build on the REST API.
- no appZapier and the automation tools: not connectedInstead: call the REST API from your automation tool.
- in your sessionLinkedIn: performed by your rep or your agentOn Today by your rep, or by an agent you connect.
Publishing to social networks is a separate module that is not switched on, and no date is published for it.
Probe log
GET, no session11 Oct 2026, 13:29 UTC
- 503/api/calendar/microsoft/connect"Microsoft 365 Calendar OAuth is not configured on the server."
- 503/api/integrations/calendly/connect"Calendly OAuth is not configured on the server."
- 401/api/calendar/google/connectThe control: Google is configured, so it asks for a session.
Statuses checked 17 Oct 2026.
What buyers actually ask
Six questions, answered the way the product behaves in production today.
More questions? Talk to usIf your CRM is Salesforce or HubSpot, yes, over OAuth against your own org or portal. If it is anything else, there is no connector and we are not going to imply otherwise. The public REST API is the real path in that case, and it is the same surface our own product is built on.
In production today it only reads, from either CRM, and that should decide your evaluation rather than be discovered afterwards. Reading is live for both Salesforce and HubSpot. Write-back to either is built and switched off in production, so it runs as a dry run: SAGARIS computes the exact change and records it without sending it. When it is switched on, Salesforce activity lands as standard Task and Event records. Switching it on is a rollout decision on our side, not a setting in your org or portal.
No. SAGARIS keeps its own record and your CRM keeps being your CRM. What SAGARIS reads becomes the record its agents act on, so the two are not competing for authority over the same field. SAGARIS does not write back into either CRM in production today, because write-back is switched off there.
Yes. You connect the mailbox and SAGARIS sends from it, rather than from a shared address of ours. Yahoo, iCloud and AOL connect today with an app-specific password you generate in your own account, encrypted before it is stored. Gmail connects over OAuth, one mailbox at a time, where it is switched on for the environment; the Gmail page says where that stands. Outlook is not connected, so an Outlook address cannot be used yet.
No, and nothing needs to be. You connect from inside SAGARIS, which authorises against your Salesforce org or HubSpot portal directly, and nothing has to be installed on their side, because reading needs no package and write-back, when it is switched on, uses standard objects (Task and Event in Salesforce, native records in HubSpot) rather than a custom package. That also means there is no managed package to upgrade, and no admin review to clear before you can start.
It depends on the integration, and one of them is worse than the rest. For the mailboxes, the calendar and HubSpot you can disconnect inside SAGARIS, and you can always revoke the grant from the provider's own security settings, which takes effect whatever we do. Salesforce is the exception worth knowing before you connect it: self-service disconnect is not built, the button in Settings is disabled, and revoking means asking us or revoking the grant in Salesforce.
What this connects to
The ledger names each connection. These pages go deeper.
- Learn more
Salesforce integration docs
The objects read, and the switch that keeps write-back off in production.
- Learn more
HubSpot integration docs
What the dry run computes, and which portal tiers gate write-back.
- Learn more
The SAGARIS CRM
What the record looks like once your pipeline is connected.