An integration is not useful because it is connected. It is useful when a call or workflow can do the right thing with it.
Public Integration Catalog
| Integration | Use it for | Typical inputs | Best place to use |
|---|---|---|---|
| Wati | Send WhatsApp session messages or approved WhatsApp template messages. | Phone number, message body, template name, template parameters, broadcast name. | Workflow Application nodes and integration-backed agent actions where enabled. |
| Resend | Send transactional or follow-up emails. | From email, recipient email, subject, text body. | Workflow Application nodes after call outcomes or lead qualification. |
| Request integration | Ask for a provider or action that is not in the catalog. | Tool name, action needed, trigger point, required fields, expected result. | Integration request modal. |
Integration Concepts
| Concept | Meaning |
|---|---|
| Provider | The product family, such as Wati or Resend. |
| Adapter | The connection method DialNexa uses for that provider. |
| 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
| 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. External services fail loudly, quietly, and sometimes poetically.
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.