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

# Calendly Voice AI Integration Guide

> Connect DialNexa voice AI with Calendly to offer the right event type, share booking links, confirm bookings, and reduce scheduling errors.

The **Calendly voice AI integration** helps callers book the correct meeting without back-and-forth messages. It is most useful when event types, routing forms, availability, and ownership are already configured in Calendly.

<Warning>
  A catalog page describes a possible workflow. It does not confirm that a native Calendly connector is enabled in your workspace. Check **Integrations** in the DialNexa dashboard first. If Calendly is not listed, use a custom function, agent webhook, or external automation service.
</Warning>

## When to use the Calendly voice AI integration

Use Calendly when:

* Callers need sales demos, consultations, interviews, onboarding, or service appointments.
* The agent can choose the correct event type from verified call answers.
* A booking link can be sent by the caller's approved channel.
* Booking, reschedule, and cancellation events return to your CRM or support process.

<Tip>
  **Best first workflow:** Qualify the requested meeting type, send the correct Calendly link, and record the confirmed booking against the caller's CRM record.
</Tip>

## Before you begin

Prepare the following:

* A published DialNexa agent that has already passed a basic test call.
* Access to the DialNexa workspace **Integrations** page.
* A Calendly account with permission to read or update the required records.
* One test record that does not affect a live customer.
* A list of actions that can run automatically and actions that require human review.

## Choose how to connect Calendly

| Connection method                                   | Use it when                                                | Important limit                                                             |
| --------------------------------------------------- | ---------------------------------------------------------- | --------------------------------------------------------------------------- |
| Workspace connector                                 | Calendly appears in your DialNexa **Integrations** page    | Available actions and authentication depend on your workspace               |
| [Custom function](/docs/agent-settings/custom-functions) | The agent needs Calendly data during the live conversation | Keep the request fast and return only the fields the agent needs            |
| [Agent webhook](/docs/api-access/agent-webhooks)         | Calendly should receive a result after the call            | Your endpoint must authenticate, retry safely, and prevent duplicate writes |
| External automation                                 | The workflow spans Calendly and several other systems      | Monitor the external workflow separately from the DialNexa call             |

## Build the Calendly voice AI workflow

1. Define the exact event that starts the action, such as a confirmed booking, qualified lead, support escalation, or completed call.
2. Choose the connection method from the table above.
3. Map caller identity, the DialNexa call ID, the verified outcome, and the destination record ID.
4. Add a condition so uncertain, sensitive, destructive, or high-value changes go to a human-owned queue.
5. Store the destination record URL or ID with the call result so your team can trace the handoff.
6. Test success, no-match, duplicate, permission-error, and timeout cases before using live traffic.

## Data to map between DialNexa and Calendly

* DialNexa call ID, call direction, status, and final outcome
* Caller name, phone number, email, and matched customer or account ID
* Structured fields collected during the call, including consent where required
* Short operational summary, requested next step, owner, and due date
* Transcript or recording link only when your privacy policy allows it
* Calendly record ID, record URL, update timestamp, and integration result

## High-value Calendly voice AI workflows

| Call outcome                          | Calendly result                                         | Human control                          |
| ------------------------------------- | ------------------------------------------------------- | -------------------------------------- |
| Qualified caller needs a meeting      | Send the correct event-type link                        | Keep routing answers accurate          |
| Caller needs a one-off booking option | Create or send an approved invitation                   | Confirm owner and expiry               |
| Caller asks about an existing booking | Look up the matched invitee or event                    | Verify identity before sharing details |
| Booking is completed                  | Write the event ID and time back to the business record | Handle duplicate booking events safely |

## Verify the Calendly integration

Run a test call and confirm that:

1. The selected event type and owner match the caller's verified need.
2. The booking link, one-off invite, or existing event belongs to the correct account.
3. Date, time zone, attendee, and routing answers are stored with the confirmed booking.
4. Booking events are deduplicated using the event and call IDs.
5. Expired links, no availability, and booking failures create a clear fallback.

## Troubleshoot Calendly integration issues

| Problem                                | What to check                                                                                                                                     |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Calendly is not shown in the dashboard | Use a custom function, webhook, or external automation service, or [request the integration](/docs/dashboard-integrations/requesting-new-integrations) |
| Authentication fails                   | Reconnect the account and verify scopes, workspace ownership, and token expiry                                                                    |
| No event type or booking is found      | Confirm the event type, owner, invitee email, booking state, and account permissions                                                              |
| Duplicate bookings appear              | Store the Calendly event ID and make booking-event processing idempotent                                                                          |
| The live call becomes slow             | Move nonessential writes to a post-call webhook and keep live lookups small                                                                       |

## Related pages

* [DialNexa integrations overview](/docs/integrations/overview)
* [Connect dashboard integrations](/docs/dashboard-integrations/connecting-integrations)
* [Use integrations in agents](/docs/dashboard-integrations/using-integrations-in-agents)
* [Use integrations in workflows](/docs/dashboard-integrations/using-integrations-in-workflows)
* [Integration workflow tutorials](/docs/tutorials/integration-workflows)