Automate·Intermediate·25 min·Updated Sep 30, 2026

Build a multi-step flow with the Workflows agent

Describe an automation across Microsoft 365 in plain language and let the Workflows agent build the working flow.

Download PDF

Microsoft 365

Works With

Business Outcome

A working cross-app automation built without touching Power Automate's flow designer.

Workflow Overview

The apps run in this order.

Power Automate
Teams
Copilot

Step 1: Describe the automation in plain languageCopilot

Write out the trigger, the steps, and the result you want as you'd explain it to a colleague — for example, "when someone submits the intake form, post a summary to the project Teams channel and add a row to the tracking list." Be specific about which form, channel, and list.

Step 2: Let the Workflows agent draft the flowCopilot

Open the Workflows agent in Copilot and paste your description. It maps your steps onto real Power Automate connectors and trigger conditions, then shows you the proposed flow before building it.

Prompt idea:

When a new response arrives on the "Vendor Intake" Forms form, post a summary of the answers to the "Vendor Onboarding" Teams channel and add a new row to the "Vendor Tracker" SharePoint list with the vendor name, contact, and submission date.

Step 3: Review the generated flowPower Automate

Open the flow in Power Automate's designer and check every step: the exact form, channel, and list the agent picked, and any field mappings it guessed at. Fix anything that points at the wrong resource before it goes live.

Step 4: Test with a real submissionPower Automate

Run the flow once with a real or test submission and confirm the Teams post and the list row both land correctly, with the right values in the right fields.

Check the work

  • Confirm the trigger fires on the exact form/list/mailbox you intended, not a similarly-named one.
  • Check field mappings against a real test run, not just the flow's summary view.
  • Re-test after any manual edit to the generated flow.

Source: HBS, "The Workflows Agent: No-Code Automation Built Into Microsoft 365" (2026)

Expected Outcome

A published, tested flow that runs on the trigger you described, visible in your Power Automate flow list.

!

Is AI actually needed here?

Everything the Workflows agent produces here — one trigger, a couple of connector actions, some field mappings — is exactly what Power Automate's own designer builds directly. Describing it in English instead of clicking it in doesn't add capability or judgment for a flow this simple.

Non-AI alternative: Build the same trigger-and-two-actions flow directly in Power Automate's designer — for something this size, it's a similar amount of effort either way, with fewer guessed field mappings to double-check.

Related Workflows

WORK WITH LIMINALS

Make AI useful for your team.

Get practical help with AI consulting or ask about training courses for your team.