Skip to main content

Import / Export

You can export any application (Tool / Agent / Voice Agent) as a config artifact and import it into another workspace, environment, or deployment.

This is how teams move from staging to production, copy applications between tenants, and share reference implementations across SimplAI deployments.

Export​

Open the application's options menu and select Export. The platform generates a config artifact that includes:

  • The application configuration (node graph, base instructions, settings).
  • References to every SimplAI resource the application depends on (Knowledge Bases, Tools, Connections, Models, etc.).
  • Human-readable resource names alongside the resource IDs.

The exported artifact downloads to your machine as a single file.

Why resource names are embedded​

When the target deployment is different from the source — a different SimplAI environment, account, or tenant — the target backend usually cannot resolve the resource IDs from the source. Without embedded names, you'd see a list of opaque IDs as "missing dependencies" on import, with no way to know what each ID was supposed to be.

By embedding the resource names at export time, the import UI can show you readable, actionable information about missing dependencies, even across deployments.

Import​

In the target workspace, open the application list and select Import. Upload the export artifact.

The import flow:

  • The frontend sends the config to the backend for resolution — the backend tries to look up each referenced resource ID on the target.
  • For each reference:
    • If the target backend resolves the ID, the import UI shows the resolved resource details (current name, type, status).
    • If the target backend cannot resolve the ID (because the resource doesn't exist on the target), the import UI falls back to the embedded name from the export — so you still see which dependency is missing.

Missing dependencies​

For each unresolved reference, you choose how to handle it:

  • Map to an existing resource on the target (e.g., point the imported Tool at a different Knowledge Base that already exists locally).
  • Create a new resource if it should be a one-to-one copy.
  • Leave unresolved if you'll wire it up later — the import will save as a draft.

Until every dependency is resolved, the imported application stays in a draft state and isn't publishable.

Setup dialog​

When you import an application, a setup dialog opens for missing dependencies and unset configuration values (e.g., empty environment variables, missing API keys for new model connections). Work through each item to bring the application into a runnable state.

Audit logging​

Both export and import are captured in the Audit log:

  • Application exported — resource type, exported by, timestamp.
  • Application imported — resource type, imported by, timestamp, the set of dependencies that were mapped or created.

When import-export is not enough​

For tighter cross-environment workflows — e.g., shipping changes from staging to prod via CI/CD — export-import is operator-friendly but not automated. The SDK & Developer path is the right way to wire application config into source control and pipelines.