Author: Nadali. Prepared using AI.
On October 29, 2026, AWS announced that existing Standard and Express Step Functions workflows can serve as AI-agent tools through AgentCore Gateway. The agent chooses when to start and what input to supply; the workflow still defines the step sequence.
In brief: this is an integration option for SMBs whose technical teams already use AWS, not a ready-made assistant for every business. A fixed sequence does not replace an access-permission review.
Questions for your contractor
Our editorial recommendation: before connecting anything, ask for the list of actions the agent will actually receive. Separate starting a workflow, reading its result and stopping it. Assign an owner and assess the consequences of an error for each action.
The connector documentation explains that pinning a particular workflow does not constrain every operation. Permissions to read execution history or status and stop an execution need separate IAM scoping. Task tokens must be kept secret.
The AWS tutorial says all targets on one gateway share its service role. Where different IAM boundaries are needed, AWS recommends separate gateways. The gateway and workflow must be in the same Region.
A practical review sequence
- Choose a harmless test workflow with fictional data. Do not start with real payments or customer records.
- Record acceptable inputs and when a human decision is required. An agreed sequence does not establish that the input itself is correct.
- Ask the team to test both permitted actions and rejection of prohibited ones.
- Decide who checks completion and investigates failure; an agent saying “started” is not evidence that the work finished.
This is a proposed review sequence, not a Nadali test result.
Availability and limits
AWS states availability in AgentCore Gateway Regions and standard charges for both services. Standard and Express do not support identical operations: in particular, history, separate status checks using DescribeExecution and stopping through this connector apply to Standard.
The takeaway: assess the integration by its permitted actions and result verification, not merely its ability to start a workflow from a conversation.
Sources read November 1, 2026. Nadali has not deployed the integration or measured savings. Cover: a reused conceptual AI illustration, not the AWS interface.
