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

# Notion Voice AI Integration Guide

> Connect DialNexa voice AI with Notion to create structured call notes, update databases, and assign follow-up actions without transcript clutter.

The **Notion voice AI integration** turns a call into a readable note or database record. It works best when an approved template defines the summary, decisions, questions, owner, and next steps instead of copying the whole transcript.

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

## When to use the Notion voice AI integration

Use Notion when:

* Teams keep project, research, recruitment, customer, or meeting records in Notion.
* A database template defines required properties and page sections.
* Call notes should link to the source customer or project record.
* Page access matches the sensitivity of the conversation.

<Tip>
  **Best first workflow:** Create one page from an approved template with the call summary, confirmed facts, decisions, open questions, owner, and due date.
</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 Notion 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 Notion

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

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

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

## High-value Notion voice AI workflows

| Call outcome                          | Notion result                                 | Human control                             |
| ------------------------------------- | --------------------------------------------- | ----------------------------------------- |
| Interview or discovery call completes | Create a structured note from a template      | Mark uncertain statements clearly         |
| Existing project is discussed         | Append a dated update to the matched page     | Match by page or database ID              |
| Follow-up is agreed                   | Update owner, status, and due date properties | Keep status rules consistent              |
| Sensitive call occurs                 | Create only the minimum approved record       | Restrict page access and transcript links |

## Verify the Notion integration

Run a test call and confirm that:

1. The workflow finds the intended Notion record instead of creating a duplicate.
2. Only the approved fields change.
3. The DialNexa call ID is stored for traceability and retry protection.
4. A failed request creates a visible error or human-owned task.
5. The receiving owner can open the Notion record and understand the next step without reading the full transcript.

## Troubleshoot Notion integration issues

| Problem                              | What to check                                                                                                                                     |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Notion 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                                                                    |
| No matching record is found          | Normalize phone numbers and email addresses, then define a clear create-versus-review rule                                                        |
| Duplicate updates 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)