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

# Trello Voice AI Integration Guide

> Connect DialNexa voice AI with Trello to create cards from confirmed calls, add context to existing work, and assign clear follow-up.

The **Trello voice AI integration** gives small teams a simple visual queue for call follow-up. It works best when one board and list represent a clear process and every created card has an owner, due date, and source link.

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

## When to use the Trello voice AI integration

Use Trello when:

* A small team tracks callbacks, enquiries, service work, or approvals on a board.
* The right board and list can be selected from the call outcome.
* Labels and custom fields have a stable meaning.
* Card movement and closure remain visible to the team.

<Tip>
  **Best first workflow:** Create one callback card in an intake list with the caller, reason, owner, due date, call ID, and link to the full record.
</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 Trello 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 Trello

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

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

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

## High-value Trello voice AI workflows

| Call outcome                        | Trello result                              | Human control                   |
| ----------------------------------- | ------------------------------------------ | ------------------------------- |
| New follow-up is agreed             | Create a card in the correct intake list   | Require member and due date     |
| Caller adds information             | Comment on the matched card                | Match by card ID or external ID |
| Work becomes urgent                 | Add an approved label and notify the owner | Let the team confirm priority   |
| Caller says the request is complete | Add the confirmation                       | Keep card closure human-owned   |

## Verify the Trello integration

Run a test call and confirm that:

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

## Troubleshoot Trello integration issues

| Problem                              | What to check                                                                                                                                     |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Trello 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)