AI and operationsOctober 29, 20262 min · updated November 7, 2026

Step Functions becomes an agent tool through Gateway

Daillac research

AWS: Step Functions workflows as agent tools, October 29, 2026

Written by

Daillac

Editorial and software engineering team

Photographic illustration of a printer producing a sequence of labels in a warehouse at dusk

On October 29, 2026, AWS announced that AI agents can use Step Functions workflows as tools through Amazon Bedrock AgentCore Gateway. Both Standard and Express workflows are supported. The agent chooses when to start the process and what input to send; the workflow then runs the steps that have been defined.

Available in Gateway regions

The AWS announcement describes the capability as available in all regions where AgentCore Gateway is offered. Standard Step Functions and Gateway charges apply. Check the regional scope of the component being used; the presence of another AWS service in a region does not establish availability for this integration.

This division allows an explicit procedure to sit behind an agent tool. It does not establish that incoming data will always be correct or that the agent will select the appropriate process. For a small business, preparation should address the actions the tool permits and the evidence it returns to staff and users.

Choose a process with written rules

Consider a fictional example in which an agent prepares a refund request that goes through an administrative check and a designated approval. The business defines the steps and permissions before making them accessible. This illustrates one possible design; it is neither a tested implementation nor a financial procedure suitable for every organization.

Start with a limited workflow and well-described inputs. Specify required fields, record identifiers and situations that require rejection. In CRM and ERP automation, the tool should receive only necessary information and use an identity authorized for its intended actions. The process owner should approve those boundaries before trials begin.

Recovery needs separate attention. If the conversation ends after launch, a new request should not blindly repeat a business action. Define how to find the previous operation and how to report its state. A custom CRM integration can expose that tracking to employees handling exceptions and make unfinished work easier to assign.

A reasonable next step is to select a reversible process or one subject to approval, then test its failures using fictional data. Check rejected inputs, insufficient permissions and the state after interruption. For a business web application, retain the execution identifier and a follow-up owner. Availability of the integration does not replace those operating decisions or prove the process is ready for production.