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

# monday.com Voice AI Integration Guide

> Connect DialNexa voice AI with monday.com to create items from calls, update approved columns, and assign operational follow-up.

The **monday.com voice AI integration** connects call outcomes with board-based work. It is useful when a board has a clear item type, required columns, ownership rules, and one stable key for finding existing work.

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

## When to use the monday.com voice AI integration

Use monday.com when:

* Teams manage leads, requests, onboarding, projects, or field operations on boards.
* The call maps to one board, group, and item template.
* Approved columns hold customer, owner, status, due date, and call ID.
* Automations are tested for every status value the agent can set.

<Tip>
  **Best first workflow:** Find or create the item using a stable external ID, add the call update, and assign the promised next action with a 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 monday.com account with permission to read or update the required boards.
* 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 monday.com

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

## Build the monday.com 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 monday.com

* 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
* monday.com board and item IDs, item URL, update timestamp, and integration result

## High-value monday.com voice AI workflows

| Call outcome                               | monday.com result                   | Human control                              |
| ------------------------------------------ | ----------------------------------- | ------------------------------------------ |
| New request arrives                        | Create an item in the correct group | Check duplicates before creation           |
| Existing work is discussed                 | Add an update to the matched item   | Match by item or external ID               |
| Follow-up is confirmed                     | Set owner and due date columns      | Keep owner fallback rules                  |
| Caller suggests completion or cancellation | Record the outcome                  | Require review before final status changes |

## Verify the monday.com integration

Run a test call and confirm that:

1. The workflow finds the intended monday.com item 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 monday.com item and understand the next step without reading the full transcript.

## Troubleshoot monday.com integration issues

| Problem                                  | What to check                                                                                                                                     |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| monday.com 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)