Free cookie consent management tool by TermsFeed

Deploy AI Agents Between Environments

On This Page

Deploying AI agents from a development environment to testing and production follows the same import/export process as other Appian design objects. This page explains what moves between environments, what you need to prepare, and how to validate your AI agents after deployment.

Keep this key point in mind when deploying AI agents:

  • An AI agent's configuration and behavior move with the object. The tools it uses (like process models, rules, records, documents, and folders) do not and must be present and accessible in the target environment.
  • AI agents don't retrain after deployment. Their reliability comes from good prompts, well-scoped tools, and iterative testing and monitoring.

Tip:  Treat each deployment as you would any other Appian release. Package clean dependencies, verify access, and validate with representative test data before you enable them in production.

What moves

The following table details which parts of an AI agent move during deployment and what you need to ensure is present in the target environment.

Element Deployment behavior Details
AI agent configuration Moves This includes Instructions, configured Inputs and Outputs, and the list of assigned Tools.
Tools (Process, AI Agent, Record Type, Rule, Document, Folder) Must exist in target environment Tools are separate design objects. Deploy them (and their dependencies) to the target environment and ensure AI agent initiators have access. Child AI agents configured as tools are displayed as precedents for the parent AI agent, and the parent AI agent is displayed as a dependent for each associated child agent. Standard impact analysis and delete checks will apply.
MCP connected systems Must exist in target environment If your AI agent uses MCP tools, include the MCP connected system in your deployment package. Verify that the MCP server URL and credentials are valid in the target environment.

Versioning

Each time you save, you create a new AI agent version. You can use the version history to track changes, compare behavior across releases, and revert if needed. When you deploy an AI agent, you move the latest version of its configuration.

Tip:  Establish a simple version tag convention in your export package description (for example, AI agent:CaseTriage v14). It makes rollbacks and cross-environment comparisons faster.

Before you deploy

To prepare your AI agent for deployment, follow these steps:

  1. Package dependencies:
    • Include the process models, expression rules, decisions, record types, documents, and folders referenced by the AI agent's tools.
    • Remove any overlapping or duplicate tools to reduce ambiguity. For example, if you have both a "Get Customer Data" rule and a "Customer Info" record type that return similar information, choose one.
  2. Verify security:
    • Confirm the initiator (the user or calling process) in the target environment has the necessary permissions to every tool the AI agent may call. For example, the initiator needs Viewer access to record types, Initiator access to process models, and Editor access to documents.
  3. Align inputs and outputs:
    • Keep input and output names clear and consistent with the objects that will use them, such as process variables, interfaces, or records.

Deploy between environments

To deploy an AI agent, follow these steps:

  1. Export the AI agent (and its required tools) from the source environment using Appian's standard export process.
  2. Import the package into the target environment.
  3. Resolve dependencies:
    • Map any environment-specific references if needed, for example, hierarchy folders, groups, or constants.
    • Confirm the underlying design objects kept their expected UUIDs, or update tool links if you deliberately created new objects in the target environment.
  4. Save and publish the imported AI agent.

Note:  If your deployment strategy promotes shared tools across multiple AI agents, validate those tools first to prevent failures. You can also use compare and deploy for AI agents, just like other Appian design objects.

Validate after deployment

After deployment, it's important to validate the AI agent's behavior:

Note:  If you don't have access to your production environment, coordinate with system administrators to perform these validation steps.

  1. Run saved test cases in the AI agent's Build tab to confirm that the inputs, tool calls, and outputs behave as expected in the new environment.
  2. Monitor initial runs in the Monitor tab. Review the request status, tool-call counts, duration, and any errors.

For detailed testing and monitoring guidance, see Monitor AI Agents. For troubleshooting deployment issues, see Troubleshooting AI Agents.

Common validation checks

Here are some common items to check during validation:

  • Permissions: The initiator can access all tools the AI agent may invoke.
  • Process tools: Long-running nodes have sensible timeouts and error handling.
  • Rule tools: Guard against nulls, and unit-test with the same inputs the AI agent uses.
  • Record queries: Target a single record type. Move aggregations or joins into rules.
  • Document tools: Provide text-based, supported files, and avoid scanned or image-only PDFs.

Learning and model behavior

  • No automatic retraining: AI agents do not automatically learn or retrain on deployment. Their performance depends on the LLM configured by the platform, your prompt, and the tools you provide.
  • Refine via iteration: Use structured testing and monitoring to improve AI agent behavior. You can adjust prompts, refine which tools are available to the AI agent, and modify inputs or outputs as you observe the results.

Feedback