Description

n8n-nodes-dialnexa

This package provides n8n community nodes for DialNexa, a Voice AI platform for inbound and outbound phone calls. It supports individual calls, call lookup and filtering, agent lookup, batch calls, and signed call-outcome webhooks.

Installation
Operations
Credentials
Call outcome trigger
Billable operation safety
Compatibility
Examples
Resources
Version history

Installation

For verified community nodes, search for DialNexa in n8n’s node panel and install it when prompted. Until verification is complete, follow n8n’s community node installation guide on a self-hosted n8n instance and install n8n-nodes-dialnexa from npm.

Operations

Call

• Trigger Call: Place a single outbound call with an agent, E.164 phone number, metadata, optional published agent version, and optional call-log notes.
• Get Call: Retrieve one call by ID.
• List Calls: Retrieve calls with filters for agent, call, batch, direction, status, sentiment, phone number, end reason, and date range.

Agent

• List Agents: Retrieve all agents in the connected DialNexa workspace. Agent selectors in call operations use this endpoint as a searchable list.

Batch Call

• Create Batch Call: Upload a CSV, XLSX, or XLS file and start or schedule a batch.
• Get Batch Call: Retrieve one page of calls and progress for a batch.
• List Batch Calls: Retrieve batch jobs, optionally filtered by status.

The batch upload file must be 10 MB or smaller and contain a phone_number column. Every other column becomes a dynamic variable available to the agent. Batch titles can contain at most 35 characters.

Credentials

1. In DialNexa, open Settings > API Keys.
2. Create an API key.
3. Copy the full key_id:secret value. The part before the colon is not sufficient by itself.
4. In n8n, create a DialNexa API credential and paste the full value into API Key.

n8n stores the value as a password field and sends it as Authorization: Bearer :. The credential test reads the workspace’s agent list and does not place a call.

Call outcome trigger

The DialNexa Trigger can subscribe to:

• call.completed
• call.failed

When the workflow is activated, the trigger creates a DialNexa user webhook for n8n’s production webhook URL. It generates a unique signing secret, stores the secret in the workflow’s encrypted/static node data, and subscribes only to the selected events. Deactivating or deleting the trigger removes the DialNexa webhook.

Every incoming request must include x-nexa-signature: sha256=. The trigger computes HMAC-SHA256 over the exact raw request body and uses a constant-time comparison before it exposes the payload to the workflow. Requests with a missing or invalid signature receive HTTP 401.

The raw trigger output can include callid, status, sentiment, summary, transcript, extracteddata, duration, recordingurl, agentid, metadata, and, for eligible organizations, billing. Turn on Simplify to omit the transcript and return at most ten high-value fields.

The n8n production webhook URL must be publicly reachable over HTTPS before the workflow can activate successfully.

Billable operation safety

Trigger Call and Create Batch Call can create real, billable calls. They deliberately do not retry automatically.

If either operation times out or returns an ambiguous server response:

1. Do not immediately run it again.
2. Use List Calls with stable metadata, or List Batch Calls, to check whether the first request succeeded.
3. Submit another create request only after confirming that no matching call or batch exists.

Expected API guidance:

• 400: Correct validation fields, including E.164 phone numbers.
• 401: Check the full API key.
• 402: Add DialNexa wallet balance.
• 403: Complete KYC and enable the required destination or telephony route.
• 404: Check the agent, call, or batch ID in the connected workspace.

Compatibility

• Node.js 22 or newer for package development.
• n8n versions that support community node API version 1 and @n8n/node-cli generated packages.
• Built and checked against the current @n8n/node-cli version listed in package.json.

Examples

• examples/call-completed-workflow.json starts a workflow when a DialNexa call completes or fails and routes completed calls separately from failed calls.

Resources

• DialNexa API introduction
• DialNexa authentication
• DialNexa calls API
• DialNexa batch calls API
• DialNexa user webhooks API
• n8n community node documentation

Version history

0.1.0

Initial release with call, agent, batch call, and signed call-outcome trigger support.