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

# Gmail Voice AI Integration Guide

> Connect DialNexa voice AI with Gmail to draft or send call follow-ups, continue existing threads, and preserve a clear email audit trail.

The **Gmail voice AI integration** turns an agreed call outcome into a clear written follow-up. It works best for confirmations, summaries, requested documents, and internal handoffs where the recipient and content can be verified.

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

## When to use the Gmail voice AI integration

Use Gmail when:

* A caller asks for a written summary, quotation, document, or confirmation.
* The reply should continue a known email thread instead of starting a duplicate conversation.
* A team mailbox has clear ownership and sending permissions.
* Sensitive or high-value emails can be drafted for review before sending.

<Tip>
  **Best first workflow:** Draft a short follow-up using the verified recipient, call summary, and agreed next step, then require a person to review the first production emails before enabling automatic send.
</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 Gmail 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 Gmail

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

## Build the Gmail 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 Gmail

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

## High-value Gmail voice AI workflows

| Call outcome                              | Gmail result                                  | Human control                            |
| ----------------------------------------- | --------------------------------------------- | ---------------------------------------- |
| Caller requests confirmation              | Draft or send a concise summary and next step | Confirm recipient and facts              |
| Call continues an existing email exchange | Reply in the matched thread                   | Avoid threading by subject alone         |
| Caller requests a document                | Attach or link the approved file              | Check access permissions and recipient   |
| Complaint or sensitive request is raised  | Draft an escalation for the owner             | Require review before sending externally |

## Verify the Gmail integration

Run a test call and confirm that:

1. From, to, cc, subject, thread, and attachments are correct.
2. Names, dates, amounts, commitments, and links match the verified call outcome.
3. Existing conversations are matched by thread or message ID, not subject alone.
4. The DialNexa call ID prevents duplicate sends.
5. Sensitive, bounced, or failed emails create a visible review or fallback task.

## Troubleshoot Gmail integration issues

| Problem                             | What to check                                                                                                                                     |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Gmail 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                                                                    |
| Existing email thread is not found  | Match with the stored Gmail thread or message ID instead of relying on the subject                                                                |
| Duplicate emails appear             | Use the DialNexa call ID as an idempotency 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)