Using Integrations In DialNexa Workflows

Use DialNexa integrations in workflow Application nodes with Wati, Resend, connected providers, action config, variables, success and failure outputs, and invocation evidence.

DialNexa workflows use integrations through Application nodes. A workflow can send a Wati WhatsApp message, send a Resend email, or run another enabled catalog action by mapping lead data, call attributes, and static configuration into required fields.

Always wire the failure output. External services have opinions, limits, and bad days.

Workflow Integration Fields

Field	Purpose
provider_key	Which integration provider to use, such as Wati or Resend.
adapter_key	Which connection adapter to call.
action_key	Which operation to run, such as send WhatsApp template or send email.
function_key	Catalog function identifier when provided.
action_config	Message body, template name, parameters, email fields, or other action inputs.
outputs.success	Next node after a successful provider result.
outputs.failure	Next node after an error or missing requirement.

Data Mapping Sources

Lead variables

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

Call attributes

Values extracted from a previous call, 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

Workflow moment	Integration action	Required mapping
Lead booked an appointment	Wati template or Resend email.	Recipient phone or email, appointment date, time, location, agent name.
Call outcome is interested	Wati follow-up template.	Lead phone, template name, lead name, offer or next step.
Call outcome needs manual review	Resend email.	Ops recipient, call summary, call link or lead id, reason.
Payment reminder failed by WhatsApp	Resend fallback email.	Recipient email, amount, due date, support contact.

Build A Reliable Application Node

1. Validate provider connection

   Do this before adding the node to an active workflow.

2. Map every required field

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

3. Name outputs clearly

   Success and failure paths should be obvious on the canvas.

4. Test one lead

   Open lead history and check the integration invocation result.

5. Scale only after evidence is clean

   One successful test should show correct request payload, provider response, and downstream branch.

Workflow Integration Mistakes

No failure branch

Provider actions can fail because of credentials, rate limits, template rules, missing fields, or invalid recipient data. Always route failure.

Static test data left in production

Replace hard-coded email addresses, phone numbers, and template parameters before launch.

Using call text instead of extracted fields

If a workflow needs a stable value, extract it into a post-call field first and map that field.

Action placed before data exists

A workflow node can only map fields that are already available at that point in the workflow.

Related Reading

Application Nodes

Configure the workflow node.

Lead Variables

Map data into actions.

WhatsApp With Wati

Send WhatsApp messages.

Email With Resend

Send email messages.