Connecting DialNexa Integrations

Connect DialNexa integrations such as Wati and Resend with credentials, hosted flows, API keys, sender email, validation, disconnect, and connection status review.

Connecting DialNexa integrations creates an organization-level connection that workflows and eligible agent actions can use. Wati and Resend use credential-style setup in the dashboard, and other future providers may use hosted connection flows.

A connection saved without validation is like a locked door with a handwritten key taped nearby. Check it before building on it.

Connection Methods

Method	How it works	Examples
Credentials	User enters required fields in DialNexa.	Wati API key, Resend API key, Resend from email.
Hosted flow	DialNexa opens a provider-managed connection URL where supported.	Future or requested providers may use this pattern.
Validation	DialNexa checks whether the stored connection can be used.	Use before workflow launch or agent exposure.
Disconnect	Removes the organization connection for the provider and adapter.	Use when rotating credentials or removing access.

Provider Credential Requirements

Provider	Required connection fields	Action depends on
Wati	API key.	Valid WhatsApp templates, phone numbers, message body, and template parameters.
Resend	API key and from email.	Verified sender setup, recipient email, subject, and text body.

Connection Statuses

Status	Meaning	What to do
Connected	Credentials are stored and validation succeeded.	Safe to use in workflows, then monitor invocations.
Pending	Connection exists but has not completed validation or hosted return.	Validate again or complete the provider flow.
Error	The provider or adapter returned a failure.	Open the error, update credentials, then validate.
Disconnected	No active organization connection is available.	Reconnect before using actions.

Connect And Validate

1. Open Integrations

   Choose the provider row, such as Wati or Resend.

2. Enter required credentials

   Add API key and any provider-specific fields. For Resend, include the from email that should send messages.

3. Save the connection

   Save credentials before wiring workflows or agent actions.

4. Validate

   Confirm the provider accepts the connection. Validation failure is cheaper here than inside a live campaign.

5. Use one test action

   Run a small workflow or action test and inspect invocation evidence.

Connection Troubleshooting

Configured but actions fail

Validate the connection and inspect invocation errors. The action may be missing required fields even when credentials are valid.

Pending status remains

Hosted connection may not have completed, or validation may not have run after saving credentials.

Resend sender fails

Confirm the from email belongs to the connected Resend setup and is allowed to send.

Wati template fails

Confirm the template exists, is approved, and receives the correct number of parameters.

Related Reading

WhatsApp With Wati

Connect and send WhatsApp messages.

Email With Resend

Connect and send emails.

Using In Workflows

Use connected actions.

Integration Functions

Debug action execution.