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 enabled for your organization.
DialNexa Integration Availability
DialNexa integrations can be native, workspace-enabled cloud connections, 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. | | Workspace-enabled cloud provider | The provider and actions appear only when enabled for your organization and adapter. | 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. | Submit the provider, action, inputs, trigger, result, and failure behavior. | For planning ideas, browse the Integration Catalog. Treat the dashboard’s current provider and function list as authoritative for implementation.Integration Concepts
| Concept | Meaning |
|---|---|
| Provider | The product family, such as Wati or Resend. |
| Adapter | The connection method DialNexa uses for that provider - chosen when the integration is connected, then reused by every action that runs through it. |
| Function | The catalog operation an action resolves to, such as Wati’s send-message function. Selected automatically when you pick an action. |
| Connection type | Credential entry or a hosted connection flow, depending on the provider. |
| Status | Connection state such as connected, pending, or error. |
| Action | A specific operation, such as sending a WhatsApp template or sending an email. |
| Invocation | A stored action execution result with redacted request, redacted response, missing fields, error, and latency. |
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.
Invocation review
Debug missing fields, provider errors, message ids, and latency.
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.| Voice call outcome | Integration action | Useful pages |
|---|---|---|
| Caller books a demo. | Send a confirmation email and add a calendar event. | Email with Resend, Google Calendar, Gmail. |
| Lead qualifies during the call. | Add CRM context and alert the owner. | HubSpot, Salesforce, Slack. |
| Support issue needs a person. | Create or update a ticket with summary and transcript context. | Zendesk, Intercom. |
| Outbound reminder reaches the right person. | Send a WhatsApp template or email follow-up after the branch completes. | WhatsApp with Wati, Resend. |
| Campaign results need review. | Write call outcomes into a spreadsheet before widening automation. | Google Sheets, call data model. |
Integration Decision Guide
| Need | Use |
|---|---|
| Send a WhatsApp reminder, confirmation, or template follow-up | Wati. |
| Send a written summary, appointment confirmation, or manual-review email | Resend. |
| Call your own internal API during a call | Custom Function, not a dashboard integration. |
| Receive call events in another system | External Webhook. |
| Ask DialNexa to add a new app or catalog action | Request integration. |
Use An Integration Safely
Validate connection
Confirm the provider accepts the credentials before wiring production workflows.
Wire success and failure
Workflows should handle both outcomes. Provider errors, missing fields, and timeouts need an explicit failure path.
Related Reading
Connecting Integrations
Set up credentials and validation.
WhatsApp With Wati
Send WhatsApp messages and templates.
Email With Resend
Send email follow-ups.
Integration Functions
Understand action execution evidence.