Upload Agent Definition
Create a new agent from a previously downloaded workflow JSON file — for backup, duplication, and moving agents between orgs or environments.
Upload Agent Definition is a button on the Voice Agents list (/workflow), next to Create Agent. It creates a brand-new agent from a workflow JSON file instead of building one from scratch or generating one from a description.
This page covers the upload side of the round trip. For everything else about creating and managing agents from the list view, see Agents & Runs. For the graph editor itself, see Voice Agent Builder.
What it's for
Uploading a definition is really a re-import of a file Talkr itself produced. Typical uses:
- Backup — keep a local copy of an agent's definition outside the database.
- Duplicate an agent — download one agent, upload it again to get a second, independent copy you can diverge from.
- Move an agent between orgs or environments — download from one organization (or a staging deployment), upload into another.
- Version-control agent configs outside the UI — commit the JSON file to a repo alongside the rest of your infrastructure.
Getting a valid file
The file has to have a specific shape: a top-level name and a workflow_definition object containing nodes, edges, and viewport. The reliable way to get one in that exact shape is to download it from Talkr first:
- Open the agent you want to export in the workflow builder.
- Click the ⋮ menu in the editor header.
- Choose Download Workflow.
This downloads <agent name>.json — the same file format the upload dialog expects. There's currently no other supported way to hand-author this file; treat it as an opaque export rather than something to construct by hand.
Downloading and re-uploading the same file is the "duplicate agent" workflow if you don't already have a Duplicate Workflow option handy from that same ⋮ menu — both end up creating a second, independent agent from the same starting definition.
What happens on upload
- Click Upload Agent Definition, then drag a
.jsonfile onto the drop zone or click Select File. - Talkr parses the file client-side and checks that
workflow_definition.nodes,.edges, and.viewportare all present. - Talkr sends it to the same endpoint used to create any new agent, so it goes through the usual validation (trigger path uniqueness, node/edge structure, tool references).
- On success, you're redirected straight into the new agent in the workflow builder.
Uploading always creates a new agent — it never overwrites an existing one, even if the file's name matches an agent that already exists. If you upload the same file twice, you get two separate agents.
If the file omits name, Talkr generates one for you (WF-<random id>) rather than failing — you can rename the agent afterward from its settings page.
Troubleshooting
| Symptom | Cause |
|---|---|
| "Failed to upload workflow. Please check if the file is valid." | Not valid JSON, or workflow_definition is missing nodes, edges, or viewport. This is the message shown for any parse or structural problem, including files that weren't produced by Talkr's own export. |
| "Please upload a valid JSON file" (drag-and-drop only) | The dropped file's browser-reported MIME type wasn't application/json. Use Select File instead if your file manager doesn't tag .json files correctly. |
| Upload succeeds but the new agent looks broken or references missing tools | The file was exported from a different organization. Node-level configuration (tools, credentials, trigger paths) doesn't automatically follow the agent across orgs — check tool references in the new agent after upload. |
| Creation fails with a validation error | The definition conflicts with something in the destination org — most commonly a trigger path (used by API Trigger nodes) that's already in use. Talkr validates an uploaded definition exactly like a manually edited one. |
Agents & Runs
Manage your agents from the Voice Agents list, configure per-agent settings, and inspect run history and individual call details.
Campaigns
Create, schedule, and monitor outbound calling campaigns from the Talkr dashboard — CSV upload, concurrency, retries, the circuit breaker, and reporting.