@dialora/n8n-nodes-dialora

This is an n8n community node. It lets you use Dialora, an AI voice-agent platform, in your n8n workflows.

The package ships three nodes sharing one credential:

• Dialora — the main action node for Dialora's public API (/api/v1/*). Resources are grouped by API scope — the Agency scope (tenant users, plans, subscriptions) is live today; Account resources (contacts, calls, campaigns) will appear as new entries in the same Resource dropdown when those APIs ship, with no breaking changes.
• Dialora Trigger — starts a workflow when Dialora posts a call webhook. Copy the node's webhook URL into your agent's Webhook tool configuration, or pass it as webhook_url when creating calls via the API.
• Dialora Call & Wait — starts an outbound call via POST /api/v1/calls (calls:write scope) and suspends the workflow until the call ends; the call event (transcript, summary, extracted data) becomes the node's output.

n8n is a fair-code licensed workflow automation platform.

Installation Operations Credentials Compatibility Usage Adding resources Resources Version history

Installation

Follow the installation guide in the n8n community nodes documentation.

Operations

Agency scope (live)

User

• Create — provision a user (email, name, password, optional phone).
• Get Many — list users, with status / search / sort filters and full pagination.
• Delete — soft-delete a user by ID.

Plan

• Get Many — list catalog plans, with active / provider / sort filters and pagination.
• Get — fetch a single plan by ID.

Subscription

• Create — subscribe a user to a plan (user_id, plan_id).
• Get Many — list subscriptions, with user_id / plan_id / status filters and pagination.
• Get — fetch a single subscription by ID.
• Change Plan — move a subscription to a different plan (server-side proration).

Create and Change Plan operations accept an optional Idempotency Key to make retries safe within a 24-hour window.

Account scope (planned)

Contacts, calls, and campaigns will be added as new resources in the same node when Dialora's account-level APIs become public.

Dialora Trigger

Fires with the call result whenever Dialora POSTs to the node's webhook URL. Two ways to wire it up: paste the URL into the agent's Webhook tool configuration in Dialora (flat payload: transcript, summary, extractions, analytics, status, numbers, direction), or pass it as webhook_url on POST /api/v1/calls (signed event envelope: type, created_at, data). An Only Completed Calls toggle skips everything except status: "completed" payloads and call.completed events.

Dialora Call & Wait

Starts an outbound call (agent, from number, to number, optional variables / metadata), passing n8n's per-execution resume URL as the call's webhook_url, then pauses the execution — no polling, no resources consumed while waiting. When Dialora posts the terminal call event (call.completed, call.failed, call.busy, call.no_answer, call.canceled), the workflow resumes with the event as this node's output. An optional Max Wait (Minutes) resumes the workflow with its input data if no event arrives in time. Requires an API key with the calls:write scope. Note: Dialora only delivers webhooks to publicly reachable URLs — a local n8n instance needs a public WEBHOOK_URL.

Credentials

You need a Dialora API key. Mint one from the Agency dashboard under API Keys; the key looks like dlr_live_… (production) or dlr_test_… (non-production) and is granted scopes such as users:read, users:write, plans:read, subscriptions:read, subscriptions:write, calls:read, calls:write. The operation you run must be covered by the key's scopes, or the API returns 403 permission_denied — the Call & Wait node needs calls:write, and the credential test needs calls:read.

In n8n, create a Dialora API credential and paste the key. Set Base URL to https://api.dialora.ai for production or https://dev.api.dialora.ai for development. The credential is sent as Authorization: Bearer <key> and tested against GET /api/v1/calls?limit=1.

Dialora's public API uses a single dlr_… key format across all scopes — future account-level resources will use this same credential; a key's granted scopes determine which operations it can run.

Compatibility

Built against the n8n community node API v1 (n8n-workflow peer dependency). Tested with current n8n.

Usage

• Pagination: enable Return All on any Get Many operation to walk every page automatically, or leave it off and set Limit to cap results.
• Filters: optional filters and sorting live under the Filters section of each Get Many operation.
• The node unwraps Dialora's { "data": … } response envelope, so downstream nodes receive the resource objects directly. Rate-limit (429) and validation (422) responses surface as node errors.

Adding resources

The code mirrors the API's scope structure while the n8n Resource dropdown stays flat:

• credentials/DialoraApi.credentials.ts — the one shared credential.
• nodes/common/ — shared helpers: pagination.ts (paginationFields, unwrapData) and request-defaults.ts (DIALORA_REQUEST_DEFAULTS).
• nodes/Dialora/resources/<scope>/ — one folder per API scope (agency/ today). Each scope's index.ts exports <scope>ResourceOptions + <scope>Description; each <scope>/<resource>/ holds an index.ts of operations plus per-operation field files.
• nodes/Dialora/resources/index.ts — composes all scopes into the node's Resource dropdown.

To add a resource to an existing scope, create resources/<scope>/<resource>/ and register it in that scope's index.ts. To add a new scope (e.g. account/), create the folder with its own aggregator and spread it in resources/index.ts — the node, credential, and package wiring need no changes.

Resources

• n8n community nodes documentation
• Dialora public API reference

Version history

• 0.5.5 — Aligned Dialora Call & Wait with the live POST /api/v1/calls contract (webhook_url, variables, required from_number); Dialora Trigger now also recognizes public API call.completed events.
• 0.5.0 — Added Dialora Trigger (call-completion webhook trigger) and Dialora Call & Wait (start a call, suspend until the completion webhook resumes the workflow).
• 0.4.0 — Consolidated into a single Dialora node with resources grouped by API scope (agency/ now; account/ later).
• 0.3.0 — Split into two nodes sharing one credential; hoisted shared helpers to nodes/common/.
• 0.2.0 — Realigned to the real agency API (/api/v1/*): Bearer auth + Base URL credential, and User / Plan / Subscription resources. Replaced the boilerplate User.get / Company operations.
• 0.1.0 — Initial scaffold.