Skip to main content
DialNexa dashboard integrations connect calls to the tools your team already uses. A voice agent can collect information, but the business value usually appears when that information becomes a WhatsApp message, an email, a CRM update, a workflow branch, a ticket, or a review row. DialNexa Integrations page showing Gmail and Google Calendar rows with connection status, view functions, configure, disconnect, and validate connection actions.
The Integrations page in your workspace is the source of truth for current availability. A public catalog page does not guarantee that a provider or action is available in your workspace.

​
DialNexa Integration Availability

DialNexa integrations can be native, cloud connections that DialNexa has enabled on the platform, or catalog guidance. Check the provider row and supported functions in the dashboard before designing a production workflow. | Availability type | What it means | How to verify | | --- | --- | --- | --- | | Native dashboard support | DialNexa provides a first-class connection and action path. Wati and Resend are the documented native examples. | Find the provider in Integrations, connect it, and inspect supported functions. | | Cloud provider | DialNexa enables cloud providers and their actions for the whole platform. A provider appears in your workspace once DialNexa has enabled it. | Use the provider row and View functions in your workspace. | | Public catalog guidance | The page explains possible voice AI workflow patterns. It does not prove availability or an exact action contract. | Check the dashboard before relying on the page. | | Requested integration | The provider or required action is not currently available to your workspace. | Request the tool and describe the action, inputs, trigger, result, and failure behavior in the request message. | For planning ideas, browse the Integration Catalog. Treat the dashboard’s current provider and function list as authoritative for implementation.

​
Integration Concepts

​
Where Integrations Are Used

Workflow Application nodes

Send WhatsApp messages, emails, or other catalog actions after workflow branches.

Agent functions

Expose selected integration actions to an agent when the model should act during a call.

Connection validation

Confirm credentials still work before relying on actions.

Action results

Find where action results appear and fix missing fields or provider errors.

Voice AI provider selection

Choose the call stack before connecting the outcome to other tools.

Integration catalog

Browse provider and business-system pages that can support call workflows.

​
Voice Call Examples

These examples depend on the providers and actions enabled in your workspace.

​
Integration Decision Guide

​
Use An Integration Safely

1

Connect credentials

Enter required fields or complete the hosted connection flow.
2

Validate connection

Confirm the provider accepts the credentials before wiring production workflows.
3

Map action fields

Use lead variables, call attributes, or static values for every required input.
4

Wire success and failure

Workflows should handle both outcomes. Provider errors, missing fields, and timeouts need an explicit failure path.
5

Review the result

For agent actions, check the call transcript in Call History. For Cloud workflow nodes, check the lead history, which records the provider, action, status, and error summary. For native Wati nodes, check the message in Wati.

Connecting Integrations

Set up credentials and validation.

WhatsApp With Wati

Send WhatsApp messages and templates.

Email With Resend

Send email follow-ups.

Integration Functions

Find where action results appear.