Import and export
Agents are portable. You can bring one in from another platform, and you can export any Glytos agent as a self-contained file to back up, version, or move between workspaces.
Migrating in
Open Agents -> Import / Migrate. Pick the platform you are coming from:
| Source | Becomes | Kind |
|---|---|---|
| Vapi | A prompt agent | Voice |
| Retell | A prompt agent, or a workflow if it has multiple states | Voice |
| Bland | A prompt agent, or a workflow for a multi-node pathway | Voice |
| OpenAI Assistants | A chat agent | Chat |
| Glytos backup | Whatever it was exported from | Backup |
Each source offers two ways in:
- Connect - paste the platform's API key, and Glytos lists your agents so you can pick which to import. The key is used only for that request and is never stored.
- Paste JSON - paste an export you already have. Useful for one-offs or after a platform has shut its API down.
Every import lands in your Development environment, so you can review and test it before promoting it up.
A multi-step Retell or Bland flow becomes a Glytos workflow: each state becomes a node, and a prompt-based transition becomes an AI edge - the same LLM-decided routing Glytos uses natively. Review the transitions after importing.
Function tools
Function tools come in as stubs: the model knows the tool's name, description and parameters, but only you know the endpoint behind it. An imported tool has no URL and will not run until you open it and set its endpoint and auth. Nothing an import creates can place a live call on its own.
The mapping report after an import lists exactly what carried over and what needs your attention - a tool to wire up, a voice id to confirm, a webhook to reconnect.
Migrating away from OpenAI Assistants
OpenAI is shutting the Assistants API down on 26 August 2026. Import your assistants before then - use Connect while the API is live, or paste an export afterwards. Each one becomes a Glytos chat agent with its instructions, model and function tools.
Exporting an agent
From an agent's menu, choose Export as JSON. You get a portable glytos-agent
document containing the agent's configuration (or workflow graph) with every tool it
uses inlined, so it is fully self-contained.
The export is secret-free. Provider keys, credentials, webhook auth headers and phone numbers are stripped out and listed as reconnect notes instead - so the file is safe to commit to version control or hand to a teammate.
To bring an export back, use Import / Migrate -> Glytos backup and paste it. Tools are recreated, references are re-linked, and the new agent lands in Development. This makes the export a natural fit for backups, templates, and moving an agent between workspaces.