Agents

Import & Export Agent

Move agent configurations between environments safely and consistently.

Definition #

Import & Export Agent is the process of packaging an Agent configuration and moving it between environments (for example, staging to production) without rebuilding it manually.

It typically includes structure, paths, steps, and widget configuration, with environment-specific values reviewed before activation.

Why it matters #

Teams use import/export to speed up rollout, keep environments aligned, and reduce manual setup errors.

It also improves repeatability when cloning proven journey designs across brands or regions.

How it works #

  1. Export an Agent from the source environment.
  2. Review the package for environment-specific values.
  3. Import into the target environment.
  4. Validate paths, widgets, integrations, and outcomes.
  5. Test with a controlled candidate flow before full use.

Configuration fields #

Common fields to verify before and after import:

  • Agent name and ownership context
  • Path and gate routing definitions
  • Step order and widget settings
  • Compatibility scoring/weight settings
  • Completion and timeout configuration
  • Integration-linked references (email, webhook, signing templates)
  • Branding and appearance settings

Example scenario #

A team finalizes a high-performing Agent in staging and exports it.

They import it into production, update environment-specific integration references, run smoke tests, and then activate the Agent for live traffic.

Common mistakes #

  • Importing without checking environment-specific integration IDs
  • Assuming imported Agent is production-ready without testing
  • Overwriting an active Agent without version/audit review
  • Ignoring missing dependencies in the target environment
  • Skipping post-import validation on journey completion behavior

Troubleshooting checklist #

  • Confirm export file integrity and source version
  • Check required dependencies exist in target environment
  • Verify step count and path structure after import
  • Validate key widgets (form, options, sign-document, webhook)
  • Run end-to-end test with a fresh candidate
  • Compare completion/outcome behavior to source environment
  • Review logs for partial import or validation warnings

Last updated Mar 28, 2026