Skip to main content

Exporting and Importing Agents

You can export an entire agent — including its tools, user inputs, flows, data sources, and settings — into a portable JSON file. This file can be shared with teammates, transferred between environments, or kept as a backup. You can also encrypt the bundle with a passphrase for secure sharing.

Exporting an Agent​

  1. Open the agent you want to export in the editor.
  2. Click Export in the toolbar.
  3. Choose which data sources to include. Agent configuration, tools, user inputs, and flows are always included.
  4. Optionally, enter an encryption passphrase to protect the bundle.
  5. Click Export (or Encrypt & Export if using a passphrase).

The bundle is downloaded as a .json file. If you set a passphrase, the file is saved as .encrypted.json instead.

Note: Sensitive information like API keys, OAuth credentials, and passwords are automatically removed from the export. When someone imports the bundle, they will be prompted to provide their own credentials.

Importing an Agent​

  1. From the agent creation screen, click Import Agent.
  2. Select a .json bundle file. If the file is encrypted, a passphrase field appears automatically.
  3. Enter the passphrase (if prompted) and proceed.
  4. Review and customize:
    • Override the agent name if needed
    • Toggle data source inclusion
    • Provide any required credentials that were stripped during export
  5. Click Import to create the new agent.

What happens to data sources?​

  • Same environment: If the original data source exists and you have permission to access it, the imported agent links directly to it — no duplication.
  • Different environment: If the data source doesn't exist or belongs to a different organization, the platform creates a new data source from the available content.

What happens if the AI model isn't available?​

If the model used by the original agent isn't available in your environment, the platform automatically substitutes an available model and shows a warning. You should verify the substituted model meets your needs.

Providing Credentials After Import​

When an exported bundle contained tools with API keys or other secrets, the import modal shows fields for each one. For example:

  • API key for "Weather" tool
  • OAuth client secret for "GitHub" tool
  • Database password for "Analytics" tool

You can fill these in during import or leave them empty and configure them later in the agent's tool settings.

Bundle Encryption​

Encryption is handled entirely in your browser — the passphrase never leaves your device.

  • The bundle is encrypted using AES-256-GCM, a strong authenticated encryption standard.
  • If you forget the passphrase, the bundle cannot be recovered. Make sure to store it securely.

Good to Know​

  • Secrets are never exported. API keys, passwords, and credentials are stripped from the bundle automatically. Recipients will need to provide their own.
  • Cloud data source connections are not preserved across environments. When importing to a different organization, live connections to services like Google Drive or Confluence are not carried over. Only file-based content from those sources is included.
  • Model substitution may occur. Always check that the AI model assigned after import is the one you want.
  • Encryption is one-way. If you lose the passphrase for an encrypted bundle, there is no way to recover it.