> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atonom.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Integrations
> Add, use, and remove third-party integrations with Atonom — OAuth apps, calendars, CRMs, conferencing, and custom connectors.
Atonom connects to the tools your team already uses — CRMs, calendars, conferencing platforms, help desks, and custom APIs. This guide explains how to add an integration, use it with Cloud Employees and other product features, and remove it when you no longer need it.
For integration-specific setup (calendar scopes, Gorgias marketplace flow, custom HTTP connectors), see the guides linked at the bottom of this page.
***
## Adding an integration
Follow these steps to connect a third-party app to your Atonom workspace.
### Step 1: Open the Integrations catalog
1. Sign in to the [Atonom dashboard](https://app.atonom.ai).
2. Go to **Settings → Integrations**.
3. Browse the catalog by category, or use **Active** to see integrations already connected to your workspace.
You need administrator access to connect most workspace-level integrations. Some integrations, such as personal calendars, are configured per user under **My Settings**.
### Step 2: Select the integration
1. Click the integration you want to add (for example, a CRM, conferencing provider, or help desk).
2. Review the integration description and the permissions Atonom will request.
### Step 3: Authenticate and authorize
Most integrations use OAuth:
1. Click **Start activation** (or the equivalent connect button on the integration page).
2. You are redirected to the third-party provider to sign in.
3. Review the requested permissions and click **Allow** or **Authorize**.
4. You are redirected back to Atonom. The integration page should show a connected state.
Some integrations require API keys or credentials instead of OAuth. Enter the required values on the integration settings page and save.
### Step 4: Enable and configure
After connecting:
1. Turn the integration **On** if a master toggle is shown on the integration page.
2. Complete any integration-specific configuration (field mappings, feature settings, etc.).
3. On the **Settings** tab of the Integrations page, assign the integration to the product features it should power (for example, CRM sync or notifications).
For per-user integrations such as calendar booking, each user must also complete setup under **My Settings** (see [Calendar Setup](/integrations/calendar-setup)).
### Troubleshooting
If you run into problems while adding an integration, try the following:
| Issue | What to check |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| OAuth access denied | Sign in with an account that has permission to authorize apps for your organization. Retry the connection flow. |
| Authorization errors or missing scopes | Confirm your IT team has granted admin consent for the required OAuth scopes. See integration-specific permission guides where available. |
| Integration not available | Your subscription may not include the integration. Contact your account team or [support](/support). |
| Connection succeeds but features do not work | Confirm the integration is **On**, feature mappings are saved on the **Settings** tab, and any per-user setup (such as calendar connection) is complete. |
| Provider-side restrictions | Some tenants restrict which users or apps can connect (for example, Microsoft Entra security groups). Work with your identity admin to allow the Atonom app. |
For calendar-specific issues, see the [Calendar Setup troubleshooting guide](/integrations/calendar-setup#troubleshooting).
If you still need help, open a [support ticket](/support) and include the integration name, your workspace, the error message, and steps to reproduce.
***
## Using integrations
Once connected, integrations power features across Atonom. The capabilities depend on which integration you connected and how it is configured.
### Workspace-level integrations
**Use case:** Connect a CRM, help desk, conferencing platform, or other shared system so Cloud Employees and workflows can read or write data on behalf of your organization.
**Prerequisites:**
* The integration is connected and **On** in **Settings → Integrations**.
* Feature mappings are configured on the **Settings** tab (where applicable).
* Your Atonom plan includes the integration.
**Common actions:**
| Action | Description | Prerequisites |
| ----------------------------- | ---------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Sync CRM data | Cloud Employees and plays can look up or update contacts, accounts, and opportunities. | CRM connected, enabled, and mapped to CRM features. |
| Create or update tickets | Conversations can create or update records in a connected help desk. | Help desk connected and enabled; Cloud Employee or play configured to use it. |
| Auto-generate meeting links | Booked meetings can include conferencing links from a connected provider. | Conferencing integration connected and enabled; users configure conferencing preferences in **My Settings → My Calendar** where required. |
| Route or enrich conversations | Connected systems can supply routing, inventory, or account context during live conversations. | Integration connected; connector or feature mapping configured. |
### Per-user integrations
**Use case:** Let individual team members connect personal accounts (such as Google or Microsoft Calendar) for scheduling and availability.
**Prerequisites:**
* The user has access to Atonom and permission to connect their calendar.
* OAuth permissions are granted for the user's mailbox and calendar.
**Common actions:**
| Action | Description | Prerequisites |
| ---------------------------------- | ----------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| Book meetings on a user's calendar | Cloud Employees and booking flows schedule meetings during live conversations or via automated plays. | User connected a calendar under **My Settings → My Calendar** and configured meeting and availability settings. |
| Show availability | Atonom reads connected calendars to find open times. | Calendar connected; availability hours and timezone configured. |
| Profile-page booking | Visitors can book meetings from a user's public profile page. | Calendar connected; profile booking enabled in **My Settings → My Profile**. |
See [Calendar Setup](/integrations/calendar-setup) and [Meeting Types](/integrations/meeting-types) for detailed configuration.
### Custom integration connectors
**Use case:** Call your own HTTP or gRPC endpoints from Cloud Employees and other Atonom flows when a first-party integration is not available.
**Prerequisites:**
* A connector is created in **Settings → Integrations → My Connectors**.
* Your server implements the endpoints described in the [Integration Connectors reference](/api-reference/connectors/integration_connectors).
See [Integration Connectors](/integrations/integration_connectors) for setup steps.
***
## Removing an integration
You can disconnect an integration when you no longer want Atonom to access a third-party system.
### Disconnect in Atonom
The exact steps depend on the integration type:
**Workspace-level OAuth integrations (CRM, conferencing, help desk, etc.)**
1. Go to **Settings → Integrations** and open the integration.
2. Turn the integration **Off** to stop Atonom from using it without removing stored credentials.
3. To fully disconnect, remove stored credentials using the disconnect or remove option on the integration page where available. If no disconnect option is shown, contact [support@atonom.ai](mailto:support@atonom.ai) to remove credentials for your workspace.
**Per-user calendar**
1. Go to **My Settings → My Calendar**.
2. Click **Disconnect Calendar** at the top of the page.
**Custom integration connectors**
1. Go to **Settings → Integrations → My Connectors**.
2. Open the connector and delete it. Connector configuration is permanently removed and cannot be undone.
### Revoke access in the third-party provider
Disconnecting in Atonom removes stored OAuth tokens and API credentials from your Atonom workspace. **It does not automatically revoke the Atonom app in the third-party provider.**
To fully remove Atonom's access, also revoke the app in the provider's account or admin settings — for example:
* **Google:** [Google Account permissions](https://myaccount.google.com/permissions)
* **Microsoft:** [Microsoft account app permissions](https://account.live.com/consent/Manage) or your Entra admin consent blade
* **Other providers:** Use the provider's connected-apps or marketplace admin page to remove Atonom
### What happens to your data
When you de-authorize an integration:
| Data | What Atonom does |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| OAuth tokens and API credentials | Removed from Atonom when you disconnect or when support removes credentials for your workspace. |
| Integration configuration | Feature mappings, connector settings, and integration-specific options are cleared when the integration or connector is deleted. |
| Historical synced data | Records already created or synced in Atonom or the third-party system (contacts, tickets, calendar events, conversation logs) are **not** automatically deleted. Remove or retain that data according to your organization's policies. |
| Active Cloud Employees and plays | Flows that depend on the integration may stop working or show errors until you reconnect or update the configuration. |
Before removing an integration used in production, turn it **Off** or update dependent Cloud Employees and plays so customer-facing flows are not interrupted.
If you need Atonom to delete specific stored data after de-authorization, contact [support@atonom.ai](mailto:support@atonom.ai) with your workspace name and the integration you removed.
***
## Integration guides
Connect Google or Microsoft Calendar and configure meeting booking
Connect Atonom to Gorgias from the Gorgias App Store
Build custom HTTP or gRPC connectors for your systems
Open a support ticket or email the Atonom team