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, because the alternative is a customer finding out after they have connected a production system. Anything we have not connected is listed at the bottom rather than left off.

CRM

Two CRMs connect over OAuth. They are not in the same state, and the difference is worth being exact about, because it is the difference between SAGARIS observing your pipeline and SAGARIS changing it.

Salesforce

Connected over OAuth from inside SAGARIS, against your own org. The connect step lives in onboarding and on the CRM screen rather than in Settings.

Into SAGARIS
Opportunities, accounts, contacts, leads, campaigns, tasks, events, notes, email messages and cases are extracted into SAGARIS, along with field history. The record in SAGARIS is the one the pipeline gates and the agents act on.
Back into Salesforce
Activity SAGARIS generates is written back into your org as standard Task and Event records, with calls and emails as Task subtypes. These are standard objects, so nothing has to be installed in the org before a write can land.
The boundary
Writes are held behind one deployed environment switch, and the resolver treats anything other than an explicit live value as a dry run, so the safe state is the default. Ongoing freshness comes from a scheduled poll rather than a real-time event stream. Self-service disconnect from Settings is not built: the button is there and it is disabled, and revoking today means asking us or revoking the grant in Salesforce.

HubSpot

Connected over OAuth from your workspace settings, against your own portal.

Into SAGARIS
For HubSpot, reading is live. Companies, contacts, deals and tasks come across on connection, followed by engagements, tickets, conversations, forms, email events and property history, kept current by a webhook feed and a scheduled poll.
Back into HubSpot
For HubSpot the write-back path is a dry run: it computes the exact mutation it would send, records it, and does not send it. Four shapes are produced, against deals, qualification properties, call objects and activity records.
The boundary
This is not a plan-level restriction on your portal and it is not a switch we can turn on for you. The released code does not write to HubSpot. If your evaluation depends on SAGARIS writing into HubSpot, it will not. Separately, custom objects and property write-back are gated by your HubSpot subscription tier, and a free portal is blocked outright.

Mail and calendar

SAGARIS sends from your mailbox and books on your calendar, which means these connections carry the highest trust of any on this page. Each one names the mechanism it uses, because an OAuth grant and an app-specific password are different promises.

Gmail

OAuth, per mailbox

Mail syncs into the unified inbox, where it sits on the same deal timeline as calls and texts, and SAGARIS sends from the connected mailbox rather than from a shared address of ours. Tokens are encrypted before they are stored.

The grant covers reading, labelling and sending for the mailbox you connect. It is one mailbox at a time, not a domain-wide delegation.

Google Calendar

OAuth, per calendar

Free and busy time is read so a meeting is only ever offered in a slot that is genuinely open, and events are created, moved and cancelled on the real calendar. A created event carries a Google Meet link. This is what the booking flow and the AI receptionist write against when a caller agrees to a time.

The connection is refused rather than half-made if Google returns no refresh token, because a connection that cannot renew itself would fail silently a week later.

Yahoo Mail, iCloud Mail and AOL Mail

IMAP and SMTP, app-specific password

These connect with an app-specific password that you generate in your own account security settings. The password is encrypted before it is stored, and mail flows into the same unified inbox as the OAuth mailboxes.

There is no OAuth flow for these providers. An app password is a credential you hold and can revoke at the source, and a provider with no configured transport is refused rather than attempted.

Notifications and call recordings

These two are configured with a credential you supply rather than with an OAuth grant, which changes who holds what. In both cases you can revoke access at the source without touching SAGARIS.

Slack

Incoming webhook or bot token, supplied by your admin

Product notifications are delivered into a channel you choose: the ones marked critical, action required or warning, which is the set worth interrupting someone for. An admin pastes either an incoming-webhook URL or a bot token and a default channel, and can rotate either one later.

Delivery only, and in one direction. There is no Slack app to install, no slash command and no way to approve or reply from inside Slack, so anything a notification asks you to do is done in SAGARIS. The destination host is pinned to Slack when the credential is saved and checked again on every send, so a tampered value cannot be used to reach somewhere else.

Fireflies and Gong

Inbound webhook, authenticated with a token you generate

A recorder you already run can push a finished call transcript into SAGARIS. The recording is archived against the contact it belongs to, the meeting is marked as having happened, and the post-call work runs against the transcript exactly as it would for a call placed inside SAGARIS.

SAGARIS does not call out to these products, so it holds no credential of yours for them and cannot pull a transcript on its own. The push is configured on their side or through an automation tool that can send a webhook. Two payload shapes are parsed in full, and those are the two named here.

Anything else: build it on the API

If the system you need is not on this page, the honest answer is that we have not built a connector for it, and the useful answer is that there is a documented public interface you can build against. It is authenticated with a workspace API key you mint and revoke yourself.

REST API

Read and write contacts, deals and activity, enrol a contact into a sequence, and manage suppression. Writes are idempotent and share one response envelope, and an OpenAPI document describes the whole surface so you can generate a client rather than hand-roll one. REST API documentation.

Outbound webhooks

Register an endpoint and SAGARIS posts to it when something happens on the record. Every delivery is signed so you can verify it came from us, and a failing endpoint is retried with backoff before the delivery is dead-lettered rather than dropped. Webhook documentation.

MCP endpoint

SAGARIS serves a Model Context Protocol endpoint, so an AI client can read your CRM, your sequences and your Brain with the same workspace API key. It is read only and scoped to your workspace, which is the point: an assistant can answer questions about your pipeline without being able to change it. About the MCP endpoint.

What SAGARIS does not connect to

A list of connections is only useful next to the list of things that are absent, so here is ours. Several of these have code written and are still not something you can turn on, which is a distinction most integration pages have no way to express.

Microsoft 365, meaning both Outlook mail and Outlook calendar

The clients are written and the connection is not open. On the production service the Microsoft credentials are not configured, and the connect endpoint says exactly that when you call it, so there is nothing to connect to today. The Google equivalent of the same endpoint, running in the same process, does open. If you run Outlook, this is the answer you need before a trial rather than during one, so we would rather publish the asymmetry than let you find it.

Calendly

The connection logic exists, including the webhook subscription that would keep bookings current, and there is no control in the product that reaches it. Production reports the credentials as unconfigured as well. Treat it as absent.

Pipedrive, and every CRM that is not Salesforce or HubSpot

There is no code for these, not a partial connector. The set of CRM providers SAGARIS recognises is two, and a request naming any other is refused rather than silently accepted.

Zapier and the automation tools

There is no SAGARIS app in any automation marketplace. What exists is the public REST API described above, which a Zap or a similar tool can call with a workspace key like any other client. That is a real path, and it is not the same thing as an app you can install.

Zoom, Otter and other call recorders

The inbound transcript webhook accepts a push from anything that can send one, and full payload parsing exists for the two products named earlier on this page. Another recorder can reach us through an automation tool that reshapes its payload, but we would be overstating it to list them as connections.

LinkedIn

A LinkedIn step in a sequence is real, and it is performed by your rep rather than by us. The step puts the contact on a daily shortlist and holds the sequence there until a person sends the message and it is logged. SAGARIS does not send to LinkedIn on your behalf. Publishing to social networks is a separate module that is not switched on, and no date is published for it.

If a connection you need is on this list, tell us. We would rather hear it from you before you buy than build in the dark, and we will say plainly whether it is something we intend to do.

What buyers actually ask

  • MOST ASKED

    If 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.

  • It depends which one, and the difference is large enough that it should decide your evaluation. Salesforce write-back is real: activity SAGARIS generates lands in your org as standard Task and Event records, held behind one deployed switch. For HubSpot the write-back path is a dry run, meaning it computes the exact mutation and does not send it, and there is no switch we can turn on for you because the released code does not write. Reading is live for both.

  • 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, and what it generates flows back where write-back is live.

  • Yes. You connect the mailbox and SAGARIS sends from it, rather than from a shared address of ours. Gmail connects over OAuth. Yahoo, iCloud and AOL connect with an app-specific password you generate in your own account, encrypted before it is stored.

  • No. You connect from inside SAGARIS, which authorises against your org or portal directly, and nothing has to be installed in Salesforce for a write to land because SAGARIS writes standard objects rather than a custom package.

  • For the mailboxes, calendar and HubSpot you can disconnect in 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.

Next door

What this connects to

Book a demo