> ## 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 Drive Voice AI Integration Guide

> Connect DialNexa voice AI with Google Drive to store approved call artifacts, retrieve trusted file links, and keep folder access controlled.

The **Google Drive voice AI integration** helps teams organize files created or requested during a call. Use it for approved summaries, recordings, transcripts, or customer documents only when folder ownership, retention, and sharing permissions are defined.

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

## When to use the Google Drive voice AI integration

Use Google Drive when:

* Call artifacts need an organized, access-controlled storage location.
* The destination folder can be chosen from a customer, project, case, or date rule.
* Sharing stays restricted to approved users or groups.
* Retention and deletion rules cover recordings and transcripts.

<Tip>
  **Best first workflow:** Save an approved call summary to a restricted folder, name it with the call ID and date, and write the Drive file ID back to the source 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 Google Drive 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 Drive

| Connection method                                   | Use it when                                                    | Important limit                                                             |
| --------------------------------------------------- | -------------------------------------------------------------- | --------------------------------------------------------------------------- |
| Workspace connector                                 | Google Drive 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 Drive 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 Drive should receive a result after the call            | Your endpoint must authenticate, retry safely, and prevent duplicate writes |
| External automation                                 | The workflow spans Google Drive and several other systems      | Monitor the external workflow separately from the DialNexa call             |

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

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

## High-value Google Drive voice AI workflows

| Call outcome                     | Drive result                                                | Human control                            |
| -------------------------------- | ----------------------------------------------------------- | ---------------------------------------- |
| Approved artifact is created     | Save it in the correct restricted folder                    | Apply retention and naming rules         |
| Team needs a file after the call | Store the file ID or restricted link on the business record | Do not create public links by default    |
| Caller requests a document       | Retrieve the approved file                                  | Verify recipient and current permissions |
| Folder match is uncertain        | Route the artifact for review                               | Never guess a customer folder            |

## Verify the Google Drive integration

Run a test call and confirm that:

1. The artifact is stored in the intended Shared Drive and restricted folder.
2. Filename, file type, call ID, customer or case reference, and date are correct.
3. Sharing stays limited to approved users or groups.
4. The Drive file ID is written back to the source record.
5. Folder ambiguity, permission failure, and upload failure create a review task.

## Troubleshoot Google Drive integration issues

| Problem                                    | What to check                                                                                                                                     |
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Google Drive 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                                                                    |
| Folder or file is not found                | Store and use Drive IDs instead of relying on names alone                                                                                         |
| Duplicate files appear                     | Use the DialNexa call ID and artifact type in the filename and creation key                                                                       |
| 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)