> ## 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.

# Google Calendar Voice AI Integration Guide

> Connect DialNexa voice AI with Google Calendar to check availability, book confirmed appointments, send invites, and prevent scheduling conflicts.

The **Google Calendar voice AI integration** lets a caller book or change an appointment during the conversation. A useful setup checks live availability, confirms the time zone and attendee details, and stores the calendar event ID for later changes.

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

## When to use the Google Calendar voice AI integration

Use Google Calendar when:

* Sales, service, healthcare, education, or field teams accept booked appointments.
* Availability can be checked on the correct owner's or resource's calendar.
* Duration, buffer, working hours, time zone, and booking rules are defined.
* Rescheduling and cancellation use the original event ID.

<Tip>
  **Best first workflow:** Offer two available slots, repeat the selected date, time, and time zone, create the event only after confirmation, and send the invite to the verified attendee.
</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 Google Calendar 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 Google Calendar

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

## Build the Google Calendar 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 Google Calendar

* 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
* Google Calendar record ID, record URL, update timestamp, and integration result

## High-value Google Calendar voice AI workflows

| Call outcome                   | Calendar result                                   | Human control                                |
| ------------------------------ | ------------------------------------------------- | -------------------------------------------- |
| Caller wants an appointment    | Check availability and create the confirmed event | Recheck the slot immediately before creation |
| Caller needs to reschedule     | Update the matched event                          | Verify attendee and original event           |
| Caller cancels                 | Cancel the matched event and record the reason    | Apply cancellation policy where required     |
| Appointment needs a video link | Add the approved conferencing option              | Do not create duplicate meeting links        |

## Verify the Google Calendar integration

Run a test call and confirm that:

1. Availability is checked again immediately before event creation.
2. Owner, attendees, date, time, time zone, duration, location, and meeting link are correct.
3. Reschedule and cancellation actions use the original event ID.
4. The DialNexa call ID prevents duplicate events.
5. Conflict, permission, and invite-delivery failures create a visible task.

## Troubleshoot Google Calendar integration issues

| Problem                                       | What to check                                                                                                                                     |
| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Google Calendar 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 suitable slot is found                     | Confirm calendar, owner, working hours, time zone, duration, buffers, and date range                                                              |
| Duplicate events appear                       | Store the event ID, use the DialNexa call ID for creation, and make retries safe                                                                  |
| 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)