Skip to main content
DialNexa agents can be exported as JSON and imported into any workspace. Importing is the fastest way to replicate an agent configuration across workspaces, onboard a new customer with a pre-built setup, or restore an agent from a backup.

​
Where to Find the Import Action

On the Agents tab, click the Import Agent button in the top right area of the page (next to New Agent). A file picker opens. Select the JSON file exported from DialNexa. Alternatively, if you are in a folder view, the import button is available at the folder level and will place the imported agent into that folder.

​
What the JSON Contains

A DialNexa agent export is a JSON object that captures the full configuration of a specific agent version. The structure includes:
SectionWhat it stores
Agent metadataName, description, and agent type, such as single prompt, conversational flow, or speech to speech.
Conversation stackLanguage, voice provider, voice ID, voice model, LLM provider, model, temperature, transcriber
PromptSystem prompt text, including any {{variable}} placeholders
Welcome messageThe first thing the agent says when a call connects
Voicemail messageThe message left if voicemail is detected
FunctionsHTTP function definitions with endpoint, method, headers, and parameter mappings
Speech settingsResponse eagerness, audio cache, denoising mode, Hinglish map
Call settingsVoicemail detection, end call on silence, max call duration
Post-call analysisExtracted field definitions (intent, sentiment, custom fields)
Dynamic variable defaultsFallback values for variables used in the prompt
Agent webhooksPer-agent webhook endpoint configurations

​
What Does Not Transfer on Import

Some configuration is workspace-specific and cannot be transferred via JSON.
What is excludedWhy
Phone number assignmentsPhone numbers are provisioned per workspace. Reassign after import.
Published version stateThe import creates a draft. You must publish explicitly in the new workspace.
Workflow connectionsWorkflow routing is configured in the destination workspace separately.
Batch call associationsBatch calls reference the imported agent only after you set them up in the new workspace.
Knowledge base attachmentsDocument files are not embedded in the export JSON. Re-attach files after import.
Importing an agent always creates a draft version. The imported agent will not receive any live traffic until you publish it and assign it to a phone number, workflow, or batch call in the destination workspace.

​
How to Import

1

Obtain the export file

In the source workspace, open the agent, click the row action menu or the agent settings menu, and select Export. DialNexa downloads a .json file to your computer.
2

Open the destination workspace

Switch to the workspace where you want to import the agent. If you manage multiple workspaces, use the workspace selector in the top navigation.
3

Click Import Agent

On the Agents tab, click Import Agent. Select the .json file from your computer.
4

Confirm the import

DialNexa validates the file and shows a preview of the agent name and configuration. Click Import to confirm.
5

Review and adjust the draft

The imported agent opens as a draft. Review the stack settings, prompt, and functions. Update anything that needs to differ in the new workspace (for example, API endpoints that point to a different environment).
6

Publish and assign

When the agent is ready, publish it and assign it to the appropriate phone number, workflow, or batch call in this workspace.

​
Supported JSON Format

The import endpoint accepts only JSON files exported by DialNexa. Manually authored JSON or files exported from third-party voice AI platforms are not supported. The expected top-level structure is: 
{
  "agent_name": "...",
  "agent_type": "single_prompt",
  "language": "en",
  "voice": { ... },
  "llm": { ... },
  "transcriber": { ... },
  "prompt": "...",
  "welcome_message": "...",
  "functions": [ ... ],
  "settings": { ... }
}
Fields that are missing from the JSON are set to their workspace defaults on import. Extra unrecognized fields are ignored.

​
Common Import Errors

The file could not be parsed. This happens if the file was manually edited and introduced a syntax error. Open the file in a JSON validator and fix the structure before retrying.
The agent type value in the JSON is not recognized. This can occur if the file was exported from a newer version of DialNexa than the destination workspace supports. Contact support if this occurs.
A voice ID or transcriber referenced in the JSON is not available in the destination workspace’s region or plan. The import succeeds but that specific setting is reset to the workspace default. Review the stack after import.
Functions are imported as-is but the destination workspace cannot validate endpoints at import time. The function will appear in the agent settings. Test it with a test call after import.
Import files have a size limit. If the file exceeds the limit (typically caused by a malformed export), re-export from the source agent and retry.

Types Of Agents

Choose the right agent type before building or importing.

Agent Templates

Start from a pre-built template instead of an export.

Agent Versions and Publishing

Publish the imported draft to make it live.

Agent Folders

Organize imported agents into the right folder.