Agent Step

Last Updated: June 12, 2026

The Agent step is a workflow step in Vasion Automate that embeds AI capabilities directly into automated workflows. Instead of routing data to external tools or relying on manual intervention for analytical tasks, the Agent step allows workflows to process information and produce structured outputs inline, without interrupting the automation.

Traditional workflow automation relies on fixed, rule-based logic. If a task falls outside a predefined condition, the workflow either fails to handle it or requires custom development to address it. The Agent step replaces rigid if-then logic with a configurable AI agent that evaluates context, applies reasoning, and returns predictable text outputs for use in later steps.

This feature is in beta. Capabilities, configuration, and availability might change as development continues. Contact your Vasion representative with feedback to help shape this feature.

How the Agent Step Works

When a workflow reaches the Agent step, the step receives data from prior workflow steps, such as document outputs, Intelligent Document Processing (IDP) results, or form inputs, and applies natural language instructions defined by the workflow builder. The agent evaluates the data against those instructions and returns a response in the configured output format, which subsequent steps in the workflow can consume directly.

The Agent step is powered by Amazon Web Services (AWS) and uses Claude Sonnet for AI processing, which provides a balance of speed and capability.

Key Points

Review the following key points:

  • Accepts runtime data from prior workflow steps, including documents, IDP results, and form inputs, to produce context-aware outputs.
  • Supports natural language instructions, allowing nondevelopers to define agent behavior without writing code.
  • Executes inline in the workflow, eliminating the need for external tools or manual context switching.

Requirements

Review these Requirements before you start.

In addition to the general requirements, the Agent step requires the following:

  • The workflow must include at least one prior step that produces data the Agent step can consume, such as a document, IDP result, or form input.
  • This feature is available in the APAC, EMEA, and US regions.

Important Considerations

Review the following:

  • Agent step output is text only and stored in workflow variable fields.
  • The agent cannot take workflow actions. To use the agent output, configure following workflow steps to route or proceed appropriately.
  • To view agent outputs, you must configure an Email step after the Agent step and include the output variable in the email. For more details refer to Email Step.

Next Steps

Refer to the following: