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

# ActiveCampaign Voice AI Integration Guide

> Connect DialNexa voice AI with ActiveCampaign to update contacts, record call intent, trigger relevant automations, and respect consent.

The **ActiveCampaign voice AI integration** connects call intent with contact, deal, and automation data. It is useful when a verified conversation should change follow-up content, create a sales task, or stop messages that no longer fit the contact.

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

## When to use the ActiveCampaign voice AI integration

Use ActiveCampaign when:

* Marketing and sales share contact and deal context in ActiveCampaign.
* Call outcomes map to a small, governed set of fields, tags, or automations.
* A booked meeting or qualified lead should create an owned sales action.
* Opt-out and contact-preference changes follow your consent process.

<Tip>
  **Best first workflow:** Match the contact, save one structured call-outcome field and a note, then trigger a follow-up automation only for a clearly confirmed interest or booking.
</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.
* An ActiveCampaign 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 ActiveCampaign

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

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

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

## High-value ActiveCampaign voice AI workflows

| Call outcome              | ActiveCampaign result                                    | Human control                                             |
| ------------------------- | -------------------------------------------------------- | --------------------------------------------------------- |
| Lead confirms interest    | Update approved fields and start the relevant follow-up  | Avoid stacking conflicting automations                    |
| Meeting is booked         | Add a note and create an owned sales task or deal action | Keep deal value changes human-owned                       |
| Contact is not interested | Stop inappropriate follow-up and save the reason         | Apply consent rules before subscription changes           |
| Outcome is unclear        | Add a review note only                                   | Do not change score or automation state from weak signals |

## Verify the ActiveCampaign integration

Run a test call and confirm that:

1. The intended contact, deal, owner, and current automation state are matched.
2. Only documented call-outcome fields, tags, notes, or scores change.
3. The DialNexa call ID prevents duplicate notes and automation triggers.
4. Opt-out and consent changes follow the approved process.
5. Conflicting automations, ambiguous matches, and failed writes create a review task.

## Troubleshoot ActiveCampaign integration issues

| Problem                                      | What to check                                                                                                                                     |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| ActiveCampaign 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                                                                    |
| Contact or deal is not found                 | Normalize identity fields and prefer stored ActiveCampaign IDs over loose matching                                                                |
| Duplicate notes or automations appear        | Use the DialNexa call ID as an idempotency key and check current automation state                                                                 |
| 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)