Workflow Builder Agent: Draft → Publish → Diagnose
You don't have to build workflows by hand anymore. The Workflow Builder agent takes a plain-language description, drafts the workflow, publishes a versioned copy, and watches the first run to flag anything that needs adjusting.
When to use it
Reach for the Workflow Builder when:
- You can describe what you want in words but don't want to wire the DAG yourself
- You need a workflow up and running quickly, with the option to refine later
- You want a teammate-readable wiki page generated alongside the workflow
Stick with the visual editor when you want pixel-level control over branching, retries, and concurrency from the start.
The lifecycle
The Workflow Builder follows a three-stage loop:
- Draft — turns your description into a workflow draft you can review before anything goes live
- Publish — promotes the draft to a published version, with a diff against any previous version
- Run + diagnose — kicks off the first execution and watches the output; if a step misfires or returns something unexpected, the agent surfaces concrete suggestions
The diagnose step is what makes this different from a one-shot generator: you get a working workflow and an opinion on what to improve.
What the wiki contains
Every workflow the builder publishes gets a short wiki page covering:
- Purpose — one paragraph on what the workflow does and when to use it
- Inputs — what you pass in and what each input controls
- Steps — each node, what agent runs it, and how it uses prior outputs
- Outputs — what the workflow produces and where it lands (Library folder, conversation reply, notification, etc.)
The wiki lives next to the workflow itself, so anyone in your organization can understand what it does without reverse-engineering the DAG.
Tips for good results
- Be specific about the trigger — "every Friday at 3pm" beats "weekly"
- Name the agents you want involved — the builder will pick reasonable defaults, but naming Content Summarizer or Data Processor up front avoids guessing
- Describe the output shape — "a markdown report saved to the Library folder named 'Weekly status'" gives the builder a concrete target
- Iterate after the diagnose step — the first publish is rarely the last; let the agent's feedback shape v2