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.| Field | Purpose |
|---|---|
application_adapter_mode | Whether the node uses Cloud mode or a native action where enabled. |
provider_key | Which integration provider to use, such as Wati or Resend. |
adapter_key | How the provider is connected - the connection variant selected when the integration was set up. |
action_key | Which operation to run, such as send WhatsApp template or send email. |
function_key | The catalog function that implements the action, for catalog-based integrations (for example, Wati’s send-message function). |
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
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
| 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
Choose Cloud mode for connected actions
Cloud mode loads connected integrations and their workflow-safe functions.
Map every required field
Use lead variables, post-call analysis fields, call attributes, or static values. Empty fields should be intentional, not surprising.
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
No failure branch
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
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
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
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.