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

> Connect DialNexa voice AI with Google Docs to create structured call notes, proposals, or handoff documents from approved templates.

The **Google Docs voice AI integration** turns structured call data into a document people can review and share. It is useful for interview notes, consultation summaries, briefs, and proposals when you start from an approved template instead of dumping a transcript.

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

## When to use the Google Docs voice AI integration

Use Google Docs when:

* A call outcome needs a readable document, not just CRM fields.
* An approved template defines headings, required facts, and placeholders.
* Someone reviews customer-facing or legally important documents.
* The final document ID and permissions can be stored with the source record.

<Tip>
  **Best first workflow:** Create an internal call brief from a template using verified fields, decisions, open questions, owner, and next step. Link to the recording instead of copying the full transcript.
</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 Docs 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 Docs

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

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

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

## High-value Google Docs voice AI workflows

| Call outcome                        | Docs result                                   | Human control                                |
| ----------------------------------- | --------------------------------------------- | -------------------------------------------- |
| Consultation or interview completes | Create a structured internal summary          | Mark uncertain facts for review              |
| Sales call needs a proposal draft   | Populate an approved template                 | Require review before sharing externally     |
| Support escalation needs a brief    | Create a handoff document with evidence links | Keep private customer data restricted        |
| Existing document must be found     | Search by stable ID or controlled metadata    | Avoid broad content search during live calls |

## Verify the Google Docs integration

Run a test call and confirm that:

1. The document uses the correct approved template and destination folder.
2. Verified facts, decisions, questions, owner, and next steps appear in the right sections.
3. Uncertain information is labeled for review instead of presented as fact.
4. The document ID and DialNexa call ID are linked for traceability.
5. Customer-facing documents require review and have the correct sharing permissions.

## Troubleshoot Google Docs integration issues

| Problem                                   | What to check                                                                                                                                     |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Google Docs 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                                                                    |
| Template or document is not found         | Store and use the exact Google Docs and destination-folder IDs                                                                                    |
| Duplicate documents appear                | Use the DialNexa call ID and document type as the 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)