Application Node Fields
These are the stored configuration keys - what the API returns for the node. In the builder you do not type them; they are filled in automatically when you pick the integration, action, and template from the node’s dropdowns.| Field | Purpose |
|---|---|
| application_adapter_mode | cloud for connected hosted integrations or native for native actions where enabled. |
| provider_key | Integration provider such as Wati, Resend, or another connected cloud provider. |
| adapter_key | Connection adapter used for the provider, such as composio for cloud actions. |
| action_key | Specific action to run. |
| function_key | Function-level key for catalog actions when provided. |
| template_name | Wati template name or action-specific template. |
| parameters | Values passed into the template or action. |
| outputs.success | Next node after successful action. |
| outputs.failure | Next node after failed action. |
Variable Sources
Use the picker rather than typing placeholders from memory when possible.| Source | Example values | Notes |
|---|---|---|
| Lead Variables | {{first_name}}, {{plan_name}} | Must have workflow fallback values before activation when used by templates or conditions. |
| Post Call Analysis | {{callback_datetime}}, {{call_outcome}} | Scoped to the current outbound agent for the workflow Voice Call node. |
| Call Attributes | {{call_id}}, {{call_status}}, {{call_duration}}, {{call_sentiment}}, {{call_summary}} | Injected at runtime and not treated as uploaded lead columns. |
Common Application Actions
Use actions that fit the workflow moment.Wati template
Send a WhatsApp template with named parameters and broadcast name.
Wati session message
Send a WhatsApp session message where the provider supports it.
Resend email
Send email with from address, recipient, subject, and text body.
Catalog action
Run an available integration action through its configured connection.
Prepare An Application Node
Choose the adapter mode
Use Cloud for connected integration functions. Use Native only for native actions enabled in your workspace.
Map variables
Use the variable picker for lead variables, post-call analysis fields, and runtime call attributes.
Wire success and failure
Connect both success and failure outputs. Generic integration nodes require both paths before execution.
Billing For Cloud Integration Actions
Composio-backed Application node executions are counted for billing whether the provider action succeeds or fails, because DialNexa still sends an integration execution request. Billing is batched in groups of100 executions at approximately INR 1.79 per batch. The wallet deduction is recorded after a batch is reached and does not block workflow execution.
Review wallet transactions and integration invocation evidence together when reconciling workflow automation costs.
Related Reading
Using Integrations In Workflows
Connect workflow actions.
Lead Variables
Map data into templates.
Integration Functions
Understand action catalog behavior.
Voice AI Provider Selection
Choose the call stack before automating the follow-up path.