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

# SendGrid Voice AI Integration Guide

> Connect DialNexa voice AI with SendGrid to send approved transactional call follow-ups and monitor delivery, bounce, and suppression results.

The **SendGrid voice AI integration** sends reliable transactional emails after verified call outcomes. Use approved templates and dynamic fields, then track delivery and suppression events so a failed email does not silently end the workflow.

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

## When to use the SendGrid voice AI integration

Use SendGrid when:

* Callers need confirmations, case references, receipts, or requested links by email.
* A dynamic template defines the approved content and required variables.
* Sender authentication and reply handling are configured.
* Bounce, block, and suppression events create a fallback path.

<Tip>
  **Best first workflow:** Send one confirmation template to the verified recipient after a successful call, save the message ID, and create a human task if delivery fails.
</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 SendGrid 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 SendGrid

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

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

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

## High-value SendGrid voice AI workflows

| Call outcome                         | SendGrid result                             | Human control                              |
| ------------------------------------ | ------------------------------------------- | ------------------------------------------ |
| Booking or case is confirmed         | Send the matching dynamic template          | Validate every template variable           |
| Caller requests an approved document | Send a secure link or approved attachment   | Confirm recipient and access               |
| Email is suppressed or bounces       | Record the event and create a fallback task | Do not retry permanent failures repeatedly |
| Content is sensitive or unusual      | Create a draft in another owned process     | Require review before sending              |

## Verify the SendGrid integration

Run a test call and confirm that:

1. Sender, verified recipient, template, and dynamic values are correct.
2. Links and attachments are approved and accessible only to the intended recipient.
3. The DialNexa call ID prevents duplicate email sends.
4. The message ID and delivery result are stored with the source record.
5. Bounce, block, suppression, complaint, and failed-send events create the right fallback.

## Troubleshoot SendGrid integration issues

| Problem                                | What to check                                                                                                                                     |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| SendGrid 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                                                                    |
| Email is not delivered                 | Check verified sender, recipient, template data, suppression, bounce, block, and event results                                                    |
| Duplicate emails appear                | Use the DialNexa call ID as an idempotency key before sending                                                                                     |
| 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)