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

> Connect DialNexa voice AI with Google Sheets to append structured call results, update matched rows, and support lightweight team workflows.

The **Google Sheets voice AI integration** is a practical starting point for pilots and small operational workflows. It can append one structured call result per row or update a matched record, but it should not become an uncontrolled substitute for a CRM or transactional database.

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

## When to use the Google Sheets voice AI integration

Use Google Sheets when:

* You are piloting lead capture, surveys, callbacks, collections, or field operations.
* The sheet has fixed column names, ownership, and protected formula columns.
* One stable key identifies the row to update.
* The workflow volume and concurrency are low enough for a spreadsheet.

<Tip>
  **Best first workflow:** Append one row per completed call with the call ID, verified contact, outcome, owner, next step, and timestamp. Treat the call ID as the duplicate-protection key.
</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 Sheets 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 Sheets

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

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

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

## High-value Google Sheets voice AI workflows

| Call outcome                      | Sheets result                                   | Human control                                   |
| --------------------------------- | ----------------------------------------------- | ----------------------------------------------- |
| New call completes                | Append a structured row                         | Protect headers and formula columns             |
| Existing lead or case is matched  | Update only approved columns in the matched row | Require one stable lookup key                   |
| Agent needs simple reference data | Read a small approved range                     | Do not expose the full sheet during a live call |
| Write fails or row is ambiguous   | Add the call to an error queue                  | Never guess which row to overwrite              |

## Verify the Google Sheets integration

Run a test call and confirm that:

1. The workflow uses the intended spreadsheet, tab, header row, and stable lookup key.
2. Only approved input columns change, while formulas and manual columns remain untouched.
3. The DialNexa call ID prevents duplicate appended rows.
4. Missing, duplicate, or ambiguous row matches go to review instead of being overwritten.
5. Permission, quota, and write failures create a visible error row or task.

## Troubleshoot Google Sheets integration issues

| Problem                                     | What to check                                                                                                                                     |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Google Sheets 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                                                                    |
| Row is missing or ambiguous                 | Use one stable unique key and route zero or multiple matches to review                                                                            |
| Duplicate rows appear                       | Use the DialNexa call ID as the append key 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)