05 / INTEGRATIONS · WORKFLOW PATTERN
Repeat connected tool actions with an item journal.
A trusted sequence can become a parameterized workflow. Deterministic steps replay without a model while the journal keeps each item’s outcome.
THE WORK TODAY
Your agent keeps making the same sequence of connected tool calls for different records. Every repeated task starts another reasoning loop.
WITH A SAVED PROCEDURE
A trusted sequence can become a parameterized workflow. Deterministic steps replay without a model while the journal keeps each item’s outcome.
What happens.
Your agent defines the MCP steps, their inputs and the expectations that prove success. The saved workflow can combine these tool calls with browser or HTTP work. A model is useful while learning or repairing the task; it is not required to decide every step of an unchanged deterministic replay.
- Read the next item
- Call the connected tool
- Save the returned value
- Continue the procedure
- Verify the declared result
WHAT GOES IN
items + workflow
WHAT COMES OUT
Journaled tool results
What makes it useful.
Use this pattern when the tools expose predictable actions and result checks. Direct mode and host mode have different execution capabilities, so follow the setup guide for the chosen path. Host permissions and the connected tools’ authorization still apply. This is a supported pattern, not a claim that every MCP tool can run in every mode.
THE CHECKS
- ✓ Tool errors remain errors
- ✓ Each item has a result
- ✓ No automatic retry of uncertain commits
Requires compatible, authorized MCP tools and a trusted workflow. Agent-managed connections use host mode; the host’s execution permissions still apply.
Inspect the source Open the interactive showcase