An integration connects an outside service to your records so it can act on them or feed them. Sonta groups them into families — AI providers, mail, telephony, outreach, prospecting, and business systems — plus open routes for anything else: webhooks, a direct connection for AI agents, and your own site. You connect a service once with its credentials, and it becomes available across the CRM.

Requirements: connecting a service needs a role that can manage integrations, plus credentials from the service itself — usually an API key or a sign-in.

Your CRM is not the only tool you use. You send mail, you make calls, you run outreach, you keep stock somewhere else — and increasingly you want AI acting on your data. An integration is how one of those outside services is connected to your records, so it can either act on them or feed them. You connect it once, and it becomes available wherever it makes sense in the CRM.

Families of integrations

Rather than one long list, it helps to see integrations by what they are for.

AI providers. Connect a provider — Anthropic's Claude, OpenAI, Google Gemini — with your own API key, and AI can work on your records. This is the connection that lets an agent read a record and decide what to change, rather than following a fixed rule; the steps are in connect an AI provider.
Mail. Connect your own mailbox so incoming messages become conversations on your contacts and replies go out from your address. See connect a mailbox and email and the inbox.
Telephony. Connect a cloud phone service to call a contact from their record and keep call history alongside everything else you know about them.
Outreach. Connect a sales engagement tool to enroll contacts into sequences and see reply activity flow back onto the record.
Prospecting. Connect a lead database to search for new prospects and pull the ones you want directly into a collection, already structured.
Business systems. Connect an existing system — an ERP, for instance — to sync operational data such as stock and product lists on a schedule, so the CRM reflects what the warehouse knows.

How connecting works

The pattern is the same across families. You choose the service, supply what it needs to trust you — an API key you generate there, or a sign-in that authorizes Sonta — and, where relevant, set a default or two. Credentials are held as credentials: entered once, not pasted into a field on a record. From then on the service shows up where it belongs — the AI provider behind an agent step, the mailbox behind a send, the phone service on a contact card.

The open routes

Not everything you might connect has a card in a catalog, so three general-purpose routes stay open. Webhooks let an outside system push events in, so an automation can react to something that happened elsewhere — or let your automations call out to another service. A direct connection for AI agents lets an assistant work your CRM as a participant, within a role's permissions, described in how an agent connects. And your own website connects as its own client, reading your catalog and writing leads and orders back. Between the catalog and these routes, most things you want to attach have a way in.

What an integration is not

An integration connects a service to your records; it does not hand that service the run of your business. Access is scoped — an agent works within a role, a website is granted specific collections, a connected provider does what it is called on to do. It is worth setting them up in that spirit: connect what you need, where you need it, rather than opening everything by default.

Where to go deeper

Most integrations pay off in combination with the rest of your setup — agents and automations for acting on what comes in, email and the inbox for mail, and using Sonta as your site's backend for your own site. Setting up individual services and building a custom integration have their own pages in this section.

Integrations overview