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

# Integrations

> Connect Topcalls to your tools to automate the call lifecycle. No code required.

## Overview

Connect Topcalls to your tools to automate the call lifecycle. Trigger calls when something happens in your CRM, push call outcomes into spreadsheets or messaging apps, and keep leads in sync between systems. Build flows visually, no code required.

<Card title="Browse the full integrations catalog" icon="puzzle-piece" href="https://www.topcalls.ai/integrations" horizontal>
  683+ tools, each with its own page listing every trigger and action. Search and filter by category.
</Card>

## What it does

<CardGroup cols={3}>
  <Card title="Trigger calls from external events" icon="bolt">
    Start a Topcalls call when a row is added to your CRM, a meeting is booked, or a form is submitted.
  </Card>

  <Card title="Deliver call outcomes" icon="arrow-right-from-bracket">
    Route completed calls, transcripts, and dispositions into your CRM, sheets, or chat tools.
  </Card>

  <Card title="Sync leads bidirectionally" icon="arrows-rotate">
    Keep lead data consistent between Topcalls and your source-of-truth systems.
  </Card>
</CardGroup>

## Available triggers

Triggers start a flow when something happens in Topcalls. The names below match what you see in the in-product catalog.

| Trigger                       | Fires when                                                                                  |
| ----------------------------- | ------------------------------------------------------------------------------------------- |
| When a Call Ends              | A call ends, regardless of outcome                                                          |
| When a Call Fails             | A call ends without reaching a person (no-answer, busy, failed, rejected, dispatch timeout) |
| When a Call Hits Voicemail    | A call is answered by a voicemail system instead of a person                                |
| When a Callback Is Requested  | A call ends with a disposition meaning the caller asked for a callback                      |
| When an Appointment Is Booked | A call ends with a disposition meaning an appointment was booked                            |
| When a Follow-up Is Scheduled | A call ends with a disposition meaning a follow-up was scheduled                            |
| When a Conversion Happens     | A call ends with a disposition you have marked as a conversion                              |

## Available actions

Actions are steps you add to a flow to make Topcalls do something. Below is a representative set; the full catalog is visible in-product.

| Action                | Effect                                                   |
| --------------------- | -------------------------------------------------------- |
| Make a Call           | Place an outbound call with a script and voice           |
| Stop In-Progress Call | Hang up a call that is currently in progress             |
| Cancel Queued Call    | Cancel a call that is queued but has not started dialing |
| Add Lead              | Create a lead and assign it to a list                    |
| Update Lead           | Change fields on an existing lead                        |
| Bulk Import Leads     | Insert many leads in one call                            |
| Start Campaign        | Activate a campaign so it begins dialing leads           |
| Pause Campaign        | Pause an active campaign without cancelling queued calls |
| Find Call by ID       | Look up a single call and return the full record         |
| List Recent Calls     | Return the last N calls for your account                 |
| Get Account Balance   | Return remaining call minutes and balance details        |

## Supported destinations

Connect Topcalls to 683+ tools across the categories below. The cards show a representative sample; the [full catalog](https://www.topcalls.ai/integrations) has a searchable page for every tool.

<CardGroup cols={2}>
  <Card title="CRM" icon="address-book">
    HubSpot, Salesforce, Pipedrive, Freshdesk, Zendesk
  </Card>

  <Card title="Calendar & scheduling" icon="calendar">
    Google Calendar, Cal.com
  </Card>

  <Card title="Spreadsheets & databases" icon="table">
    Google Sheets, Airtable, Notion
  </Card>

  <Card title="Messaging & email" icon="message">
    Slack, Discord, Gmail, SendGrid, Mailchimp
  </Card>

  <Card title="Commerce & payments" icon="credit-card">
    Stripe, Shopify
  </Card>

  <Card title="Telephony & SMS" icon="phone">
    Twilio
  </Card>
</CardGroup>

More destinations are added regularly. Browse the [full catalog](https://www.topcalls.ai/integrations) to see every supported tool; if one you use isn't there yet, [let us know](https://www.topcalls.ai/contact).

## Setup walkthrough

<Steps>
  <Step title="Open the Integrations tab">
    Sign in at [topcalls.ai](https://www.topcalls.ai/auth/sign-in) and click **Integrations** in the left sidebar.
  </Step>

  <Step title="Pick a destination">
    Browse the [integrations catalog](https://www.topcalls.ai/integrations) (or the **Integrations** tab in-app) and click the tool you want to connect. Each entry shows the triggers and actions available for that destination.
  </Step>

  <Step title="Authorize the connection">
    Sign in with OAuth or paste an API key, depending on the destination. Topcalls stores credentials encrypted and only uses them for the flows you build.
  </Step>

  <Step title="Build your flow">
    Drag a trigger onto the canvas, add one or more actions, and map the fields between them. The visual editor previews the data at every step.
  </Step>

  <Step title="Test with a sample event">
    Run the flow against a sample event before turning it on for live traffic. Once you're happy with the result, enable it and the flow runs automatically.
  </Step>
</Steps>

## Webhooks vs Integrations

<Tip>
  **Webhooks** deliver call events directly to your endpoint with a JSON payload. Best when you have a backend that can receive and process them.

  **Integrations** route the same events through a no-code builder to other tools. Best when you want to push data into a CRM or messaging app without writing code.
</Tip>

You can use both. Webhooks for the systems your engineers own, Integrations for the tools your operations team uses.

## Where to next

<CardGroup cols={2}>
  <Card title="Webhooks Guide" icon="webhook" href="/guides/webhooks">
    Set up webhooks, handle payloads, and verify signatures.
  </Card>

  <Card title="Webhooks & Events" icon="bolt" href="/concepts/webhooks">
    Read the event model, available events, and retry semantics.
  </Card>
</CardGroup>