Skip to main content
DialNexa workflows use integrations through Application nodes. Wati templates use Native mode, while connected providers such as Resend use Cloud mode. Both paths can map lead data, post-call fields, call attributes, and static configuration into required fields. DialNexa workflow Application node using a connected cloud integration action with mapped fields and success and failure branches.
Cloud actions need explicit success and failure outputs. Native Wati uses one continuation output, so review lead history and invocation evidence when the provider rejects a message.

​
Before You Begin

Connect and validate the provider, prepare test lead values, and map every required field before activation. For Cloud actions, wire explicit success and failure outputs. For native Wati, connect the single continuation output.

​
DialNexa Workflow Integration Fields

These are the stored configuration keys behind an Application node - you never type them by hand. Picking the integration, action, and template in the node’s dropdowns fills them in.

​
Data Mapping Sources

Lead variables

Values uploaded with the lead, such as name, phone number, email, city, or appointment date.

Call attributes

Runtime call values and post-call analysis values, such as interested, reason, preferred time, or support issue.

Static config

Fixed template name, broadcast name, subject, or text body.

Invocation response

Provider message id, response payload, error code, and latency.

​
Wati And Resend Workflow Examples

​
Build A Reliable Application Node

1

Validate provider connection

Do this before adding the node to an active workflow.
2

Choose the adapter mode

Select Native for WhatsApp (Wati) templates. Select Cloud for connected integrations and their workflow-safe functions. Wati is intentionally absent from the Cloud picker.
3

Sync and select Wati templates

For Wati, sync approved templates from the Integrations page first, then use the searchable template picker in the Application node.
4

Map every required field

Use lead variables, post-call analysis fields, call attributes, or static values. Empty fields should be intentional, not surprising.
5

Connect the available outputs

Name Cloud success and failure paths clearly. Native Wati has one continuation output.
6

Test one lead

Open lead history and check the integration invocation result.
7

Scale only after evidence is clean

One successful test should show correct request payload, provider response, and downstream branch.
Composio-backed cloud executions are billed in batches of 100 at approximately INR 1.79 per batch. Billing does not block workflow execution, so review integration invocation evidence and wallet transactions together.

​
Workflow Integration Mistakes

Cloud provider actions can fail because of credentials, rate limits, template rules, missing fields, or invalid recipient data. Always route the Cloud failure output. Native Wati uses one continuation path, so review invocation evidence separately.
Replace hard-coded email addresses, phone numbers, and template parameters before launch.
If a workflow needs a stable value, extract it into a post-call field first and map that field.
A workflow node can only map fields that are already available at that point in the workflow.

​
Verify The Workflow Integration

Run one successful action and one controlled failure. For Cloud actions, confirm the lead follows the expected success or failure output. For native Wati, confirm the message result in lead history and verify the single continuation path.

Application Nodes

Configure the workflow node.

Lead Variables

Map data into actions.

WhatsApp With Wati

Send WhatsApp messages.

Email With Resend

Send email messages.