> ## Documentation Index
> Fetch the complete documentation index at: https://docs.60db.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration setup guides

> Step by step: create the key or app in each provider, connect it in 60db, and give its tools to an agent

Each guide below shows where to create the key (or OAuth app) in the provider, what to type in 60db, and which tools the agent gets. For how integrations work in general, see [Agent integrations](https://docs.60db.ai/features/agents-integrations.md).

## The same three steps for every integration

**1. Create the key in the provider**

Follow the provider's guide below. Copy the key right away: many providers show it only once.

**2. Connect it in 60db**

Open **Agents > Integrations**, click the provider, fill in the form and click **Connect**. 60db runs a live test with your details and shows **Connected**, or the reason it failed. Keys are stored encrypted and never shown again; the form shows only their last characters.

**3. Give the tools to an agent and tell it when to use them**

Open the agent > **Tools & webhooks** > add the tools you want. Then click **Copy instructions**, fill in any values it asks for (for example your Cal.com event type), copy the text and paste it into the agent's **Instructions**, wherever it fits your call flow. Click **Save changes**. An agent uses a tool only when its Instructions say when to. See [Tell the agent when to use its tools](https://docs.60db.ai/features/agents-integrations.md#tell-the-agent-when-to-use-its-tools).

> [!TIP]
>
> Test with one call after setup: open the agent's **Tool log** tab to see every tool call, its input, its answer and how long it took.

## Scheduling

### Cal.com

Tools: `list_event_types`, `get_available_slots`, `create_booking` (books the meeting during the call; it appears in Cal.com at once).

**1. Create an API key**

In Cal.com open **Settings > Developer > API keys**, click **New**, give it a name (`60db`), choose **Never expires** or a date, and click **Save**. Copy the key (it starts with `cal_live_`).

**2. Connect in 60db**

**Integrations > Cal.com** > paste the **API key** > **Connect**.

**3. Add the tools and the instruction**

Add all three tools to the agent. In **Copy instructions** pick your **Event type** from the list (loaded from your account) and check the **Time zone**, then copy and paste.

* Booking needs the caller's **name and email**; the instruction tells the agent to ask for them and read the email back.
* The agent must book a time that `get_available_slots` returned, copied exactly (for example `2026-11-17T10:00:00.000+05:30`). A time outside your Cal.com availability is refused.

### Calendly

Tools: `list_event_types`, `get_available_times`, `create_scheduling_link`.

> [!WARNING]
>
> Calendly cannot book a meeting during a call. `create_scheduling_link` makes a one-time booking link; the meeting appears in Calendly only after the caller opens the link and picks a time. To book on the call, use [Cal.com](#calcom). To send the link, also add [Twilio](#twilio) (SMS) or [WhatsApp](#whatsapp).

**1. Create a personal access token**

In Calendly open **Integrations & apps > API & Webhooks > Personal access tokens** (or **Integrations > API & Webhooks**), click **Generate new token**, name it `60db` and copy it.

**2. Connect in 60db**

**Integrations > Calendly** > paste the **Personal access token** > **Connect**.

**3. Add the tools and the instruction**

In **Copy instructions** pick the **Event type**. The instruction tells the agent never to say a meeting is booked.

`get_available_times` only accepts a window that starts in the future and is at most 31 days long.

## CRM

### HubSpot

Tools: `search_contact`, `create_contact`, `create_note`, `log_call`.

**1. Create a private app**

In HubSpot open **Settings** (gear icon) > **Integrations > Private Apps** > **Create a private app**. Name it `60db`. On the **Scopes** tab add **`crm.objects.contacts.read`** and **`crm.objects.contacts.write`**. Click **Create app**, then **Continue creating**, and copy the **Access token** (starts with `pat-`).

**2. Connect in 60db**

**Integrations > HubSpot** > paste the **Private app token** > **Connect**.

### Salesforce

Tools: `find_contact` (contacts and leads by email or phone), `create_case`, `log_call`. Salesforce connects only with **Connect with Salesforce** (OAuth); there is no key to paste.

**1. Create an OAuth app in Salesforce**

In Salesforce **Setup**, search **App Manager** > **New External Client App** (or **New Connected App**). Turn on **OAuth**, set the **Callback URL** to the Redirect URL shown under the **Connect with Salesforce** button in 60db, and add the scopes **Manage user data via APIs (api)** and **Perform requests at any time (refresh\_token, offline\_access)**. Save, then copy the **Consumer Key** (client ID) and **Consumer Secret**.

**2. Connect in 60db**

**Integrations > Salesforce** > paste the **OAuth client ID** and **secret** > **Connect with Salesforce** > log in and click **Allow**. 60db renews the sign-in automatically.

If 60db shows the button without client fields, 60db's own Salesforce app is set up: just click **Connect with Salesforce**.

## Customer support

### Zendesk

Tools: `create_ticket`, `get_ticket`, `search_tickets_by_email`. Zendesk connects with **Connect with Zendesk** (OAuth) or an API token. See [Zendesk](https://docs.60db.ai/features/agents-integrations.md#zendesk-api-token) for both ways.

**API token, step by step:**

**1. Create the token**

In Zendesk open **Admin Center > Apps and integrations > APIs > API tokens** > **Add API token**, name it `60db`, copy the token and click **Save**. No **Add API token** button? Open **APIs > API configuration**, turn on **Allow API token access** and save.

**2. Connect in 60db**

**Integrations > Zendesk** > **Subdomain** (`acme` for `acme.zendesk.com`), **Agent email** (the email of the person who created the token) and **API token** > **Connect**.

> [!WARNING]
>
> Zendesk ends API tokens on **30 April 2027**. Use **Connect with Zendesk** where you can.

### Freshdesk

Tools: `create_ticket`, `get_ticket`.

**1. Copy your API key**

In Freshdesk click your **profile picture** (top right) > **Profile settings**. Your key is under **Your API Key** on the right (click **View API key** and complete the check if asked).

**2. Connect in 60db**

**Integrations > Freshdesk** > **Domain** (`acme` for `acme.freshdesk.com`) and the **API key** > **Connect**.

### Intercom

Tools: `find_contact`, `create_ticket`, `add_conversation_note`.

**1. Create an app and copy its access token**

Open the **Intercom Developer Hub** (Settings > Integrations > Developer Hub) > **New app**, name it `60db`, choose your workspace and create it. Open **Authentication** and copy the **Access token**.

**2. Connect in 60db**

**Integrations > Intercom** > paste the **Access token** > **Connect**.

`create_ticket` needs a ticket type: create one under **Settings > Tickets** in Intercom first, and enter its ID as **Ticket type** in **Copy instructions**.

### Plain

Tools: `upsert_customer`, `create_thread`.

**1. Create a machine user and API key**

In Plain open **Settings > Machine users** > **Add machine user**, name it `60db`. Open it > **Add API key** and tick **customer:create**, **customer:edit**, **thread:create** and **thread:read**. Copy the key.

**2. Connect in 60db**

**Integrations > Plain** > paste the **API key** > **Connect**.

## IT service management

### ServiceNow

Tools: `create_incident`, `get_incident`. ServiceNow connects with an **OAuth client ID and secret** (recommended) or a user name and password. The full guide, including the integration user, the client credentials setting and the OAuth app, is in [ServiceNow](https://docs.60db.ai/features/agents-integrations.md#servicenow).

### Jira

Tools: `create_issue`, `get_issue`.

**1. Create an API token**

Open **id.atlassian.com > Security > Create and manage API tokens** > **Create API token**, name it `60db`, choose an expiry and copy the token.

**2. Connect in 60db**

**Integrations > Jira** > **Site** (`acme` for `acme.atlassian.net`), **Account email** (the Atlassian account that created the token) and the **API token** > **Connect**.

`create_issue` needs a **project key**: the letters before the number in issue keys (for example `SUP` in `SUP-12`). Enter it as **Project key** in **Copy instructions**. Issues are created as type **Task** unless the agent names another type that exists in the project.

### PagerDuty

Tool: `trigger_incident`.

**1. Add an Events API v2 integration**

In PagerDuty open **Services > Service Directory** > your service > **Integrations** > **Add an integration** > **Events API V2** > **Add**. Copy the **Integration Key** (32 characters).

**2. Connect in 60db**

**Integrations > PagerDuty** > paste the **Routing key** > **Connect**.

The live test checks the key's format and sends PagerDuty a harmless "resolve" for an alert that does not exist; it cannot prove the key belongs to a live service. Trigger one test incident from a call to be sure.

## Messaging

### Slack

Tool: `post_message`.

**1. Create a Slack app with a bot**

Open **api.slack.com/apps** > **Create New App** > **From scratch**, name it `60db` and pick your workspace. Open **OAuth & Permissions** > **Bot Token Scopes** > add **`chat:write`**. Click **Install to Workspace** > **Allow**. Copy the **Bot User OAuth Token** (starts with `xoxb-`).

**2. Invite the bot to the channel**

In Slack, open the channel and type `/invite @60db` (your app's name). The bot can post only in channels it was invited to.

**3. Connect in 60db**

**Integrations > Slack** > paste the **Bot token** > **Connect**. In **Copy instructions** enter the **Channel** (for example `#leads`).

### Telegram

Tool: `send_message`.

**1. Create a bot**

In Telegram open **@BotFather** > send `/newbot` > choose a name and a username ending in `bot`. Copy the **token** it sends (like `123456789:AAE…`).

**2. Start the bot**

Open your bot (search its username, or `https://t.me/<username>`) and tap **Start**. A bot can only message people who started it.

**3. Find the chat ID**

Open `https://api.telegram.org/bot<TOKEN>/getUpdates` in a browser (your token in place of `<TOKEN>`) and copy the number after `"chat":{"id":`. Empty result? Send the bot another message and reload. For a **group**: add the bot to the group, send a message there, reload; the group ID starts with `-`. For a public **channel**: make the bot an admin and use `@channelname`.

**4. Connect in 60db**

**Integrations > Telegram** > paste the **Bot token** > **Connect**. In **Copy instructions** enter the **Chat ID**.

If the live test says *The provider did not answer in time* with a correct token, Telegram is not answering for that bot: create a new bot with `/newbot` and use its token.

### Twilio

Tool: `send_sms`.

**1. Copy your account details**

In the **Twilio Console** home page, copy the **Account SID** (starts with `AC`) and the **Auth Token** (click **Show**).

**2. Get a number that can send SMS**

**Phone Numbers > Manage > Buy a number**, tick **SMS**, and buy one. On a trial account, you can only text numbers you verified under **Verified Caller IDs**.

**3. Connect in 60db**

**Integrations > Twilio** > **Account SID**, **Auth token** and **From number** (the Twilio number with country code, for example `+15551234567`) > **Connect**.

### WhatsApp

Tool: `send_message` (to your team or the caller, from your own business number). No key is needed.

**1. Connect your number**

Under **WhatsApp > Numbers**, connect your business number and wait until it shows **connected**.

**2. Create a template for new chats**

Under **WhatsApp > Templates**, create a template such as `team_alert` with the body `New lead from 60db: {{1}}` and wait for Meta's approval. It lets the agent message people who have not written to you in the last 24 hours.

**3. Connect in 60db**

**Integrations > WhatsApp** > choose your **WhatsApp number**, the **Template for new chats** and its **Template language** from the lists > **Connect**. Only connected numbers and approved templates are offered; templates with more than one variable are shown but cannot be picked.

**4. Optional: more templates**

Tick the templates the agent may pick by name under **More templates the agent can choose**, for example one for interested callers and one for the rest. See [Different templates for different outcomes](https://docs.60db.ai/features/agents-integrations.md#different-templates-for-different-outcomes).

Full guide and sending rules: [WhatsApp from an agent](https://docs.60db.ai/features/agents-integrations.md#whatsapp-from-an-agent).

## Search

### Exa

Tool: `web_search` (a short answer with sources).

**1. Create an API key**

Open **dashboard.exa.ai > API keys** > **Create key**, name it `60db` and copy it.

**2. Connect in 60db**

**Integrations > Exa** > paste the **API key** > **Connect**. The live test runs one search, which Exa bills.

### Tavily

Tool: `web_search`.

**1. Copy your API key**

Open **app.tavily.com**. Your key (starts with `tvly-`) is on the overview page under **API Keys**; click **+** to create another one.

**2. Connect in 60db**

**Integrations > Tavily** > paste the **API key** > **Connect**.

### Parallel

Tool: `web_search`.

**1. Create an API key**

Open **platform.parallel.ai > API keys** > **Create API key** and copy it.

**2. Connect in 60db**

**Integrations > Parallel** > paste the **API key** > **Connect**. The live test runs one search, which Parallel bills.

## Developer tools

### Cursor

Tools: `launch_agent` (starts a Cursor cloud agent on a repository), `get_agent`.

**1. Create an API key**

Open the **Cursor Dashboard** (cursor.com/dashboard) > **Integrations** > **API keys** > **New API key**, name it `60db` and copy it. Cursor must have access to the GitHub repository the agent will work on.

**2. Connect in 60db**

**Integrations > Cursor** > paste the **API key** > **Connect**. In **Copy instructions** enter **who** may ask for it and the **repository** URL.

### Custom MCP server and custom webhook

Connect your own tools: an MCP server URL (with optional bearer token and headers), or your HTTPS endpoint with actions you define. See [Custom MCP servers](https://docs.60db.ai/features/agents-integrations.md#custom-mcp-servers) and [Custom webhooks](https://docs.60db.ai/features/agents-integrations.md#custom-webhooks).

## Google Calendar, Drive and Sheets

Shown as **Soon** until 60db's Google app is approved by Google. Connections made earlier keep working. See [Connect with OAuth](https://docs.60db.ai/features/agents-integrations.md#connect-with-oauth-google-calendar-google-drive-google-sheets-salesforce-zendesk).

## When the live test fails

| Message | What it means | Fix |
| - | - | - |
| *The provider rejected the credentials* | Wrong or expired key, or a missing permission | Create a new key with the scopes listed in the guide and paste it again |
| *The provider refused the request* | The key works but is not allowed to do this | Add the missing scope or role (for example `chat:write` in Slack, `itil` in ServiceNow) |
| *The provider did not answer in time* | The provider did not reply within a few seconds | Try again; for Telegram, create a new bot |
| *Not found* | Wrong subdomain, site, domain or instance | Check the account name you typed (`acme`, not the full URL, is enough) |

The connection is saved even when the test fails, so you can fix the details and click **Save changes** without starting again.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.