What If Your Inbox Sorted, Answered, and Scheduled Itself? Email Automation With Copilot Studio Workflows

How Copilot Studio Workflows Handle Your Email

Most email falls into a few types. Someone wants a meeting, someone needs a reply, something is urgent, or it is just information. Sorting all of that by hand takes a real chunk of every day.

This post walks through an email automation built with Copilot Studio workflows. Every new email is read and sorted into one of those types, and each type gets handled its own way: meeting requests get booked, replies get drafted from your own content, urgent email comes to you for a quick yes or no, and informational email gets filed with a short Teams note.

It looks like a lot of technology, but the build is mostly dragging steps onto a canvas and connecting them.

Watch the Full Walkthrough First

The video builds the whole workflow from a blank canvas, then runs a live test where an urgent email turns into a Teams meeting after one approval. Watching it first makes the steps below much easier to picture.

Which Workflows This Is

There are two things called Workflows, and they are easy to mix up. Microsoft 365 Copilot has a Workflows agent, available through the Frontier program, that handles lighter automations. This post uses Workflows in Copilot Studio (copilotstudio.microsoft.com), which is a full designer with far more options. Workflows built there run on Copilot Credits.

The Building Blocks

A workflow is a set of steps, called nodes, connected on a canvas. The panel on the left lists what you can add:

• Agent: an AI agent with its own instructions, model, and tools. You can build one inside the workflow or bring in an agent you already made in Copilot Studio

• Classify: sorts text into categories you describe

• Copilot: hands a task to Microsoft 365 Copilot, which can work from your documents, Teams messages, and SharePoint sites, or call agents like Researcher and Analyst. In the video this node is called M365 Copilot

• Human review: pauses the workflow until a person responds

• Connectors: actions in other services, including ones outside Microsoft such as ServiceNow

• Logic: functions, variables, if/else conditions, loops, and notes

The workflow in this post uses most of them, starting with the step that kicks everything off.

Step 1: Start With the New Email Trigger

A new workflow opens with a Start node set to a manual trigger, which only runs when you start it yourself. To make it automatic, change the trigger to Connector, choose the Office 365 Outlook connector, and pick When a new email arrives.

Check that the connection shows a green check mark. If it does not, create a new connection and sign in with your own account. Every connected step needs that green check.

Under Show all, you can narrow the trigger to email from one sender. The video leaves those fields blank so every email runs through.

Step 2: Sort Each Email With a Classify Node

Drag a Classify node under the trigger and connect them. In the input field, use the dynamic content picker (the lightning icon, or type a slash) to insert the parts of the email you want considered. The video uses the Body, From, Subject, Importance, and Attachments, with a short instruction to classify the email based on them.

Then pick a model. Sorting email does not need the most powerful option, so the video switches from Claude Opus to Claude Sonnet 4.6, which costs much less. Model choices change often, so pick a current model that fits the job and save the expensive ones for harder steps.

Next, define four categories, each with a name and a plain description:

• Meeting: "An email that is requesting a new meeting."

• Reply Requested: "An email that requires me to reply."

• Priority: "An email that is priority, time-sensitive, and requires immediate attention or action."

• Informational: "An email that is just informational."

You can also add example emails for any category that might get confused. Classify adds a fifth branch, Other, automatically for anything that does not fit.

From here, each branch gets its own handling, starting with the simplest one.

Step 3: Book Meetings Automatically

Connect an Agent node to the Meeting branch. Connect it before configuring it, because a node can only use data from the steps it is connected to. Once it is connected, the lightning icon shows everything from the email.

Give the agent instructions like these: "Set up a 30-minute meeting with [From] in the next 7 days. Use the [Body] of the email to set the agenda and the title of the invite. Include a Teams meeting link so it is an online meeting, make sure the time is free on everyone's calendar, and only send one invitation." The items in brackets are inserted from the dynamic content picker.

Under Tools, choose MCP and add Calendar. MCP (Model Context Protocol) tools bundle several related actions into one connection, so the Calendar tool alone can check availability and create the event. Rename the node to something like Meeting Logic so the canvas stays readable.

Step 4: Draft Replies From Your Own Content

The Reply Requested branch uses two steps. First, a Copilot node drafts the reply, because Microsoft 365 Copilot can draw on your email, OneDrive, SharePoint, and Teams. A message like this works: "Review the details of the email, including the [From], [Subject], [Body], and [Attachments], and using my content, draft an email reply."

Copilot writes the draft but does not put it in your mailbox, so add an Agent node after it. Because it is connected to the Copilot node, it can use that node's response. Its instructions: "Review the draft from the previous step [Copilot response] and save the email as a draft that I can send to [From]." Under Tools, add the MCP Mail tool so it can save drafts. Rename it Email Drafter.

Nothing gets sent on this branch. You review each draft in Outlook and send it yourself.

Step 5: Put a Person in the Loop for Priority Email

Urgent email is where a second opinion helps, so this branch checks with you before acting.

1. Add an Agent node to judge the email

   • Instructions: "Review the email's [Body] and [Importance] and decide whether it is a priority. If it is, summarize it for me."

2. Add a Human review node

   • Use the agent's response as the message, assign it to yourself, and choose Teams as the channel

   • Add a Yes or No input so you can confirm it really is urgent

3. Add an if/else condition on your answer

   • If Yes: an agent named Immediate Meeting sets up a meeting with the sender in the next 30 minutes, with a Teams link, using the MCP Calendar tool

   • If No: an agent named Follow Up Later emails the sender to say you understand the urgency and will be in touch within 24 hours, using the MCP Mail tool

The workflow waits at the review step until you answer, so nothing urgent goes out on the agent's judgment alone.

Step 6: File Informational Email and Catch the Rest

For the Informational branch, add an agent named Info Sorter with instructions like: "Determine if this email is just informational. If it does not require any action from me and is not asking me to set up or join a meeting, it is most likely informational. If so, mark it as read and send me a brief Teams message." Add the MCP Teams and Mail tools.

The video has this agent delete the message. Start with marking it as read, or add an Office 365 Outlook Move email step to file it in a folder, and only switch to deleting once you trust the sorting. A wrong guess is easy to fix when the email still exists.

Do not leave the Other branch empty. Send it to a human review step or a simple Teams notification so nothing falls through quietly. Then save and publish.

Test It Before You Turn It On

Select the play icon to enter test mode and send yourself a test email. In the video, an email marked high importance and described as a time-sensitive update goes through the whole priority path:

• The trigger fires and the Classify node sends it to Priority

• The priority agent summarizes it, and a card arrives in Teams asking for a yes or no

• After a Yes, the Immediate Meeting agent sends a Teams invite, which lands in the sender's inbox moments later

Each node in a test run shows its reasoning and output, so you can see exactly which step made each call.

Tips That Save You Trouble

• Save often. Leaving the designer without saving loses your work

• Rename nodes as you go. Meeting Logic is easier to follow than Agent 1

• Match the model to the step. A less expensive model handles sorting and simple drafting well

• Know how to turn it off. In the Workflows list, open the workflow and disable it if it misbehaves. To turn it back on, review it and publish again

• Every run uses Copilot Credits, and this workflow runs for every email you get. Our free AI Agent Cost Calculator helps you estimate what that adds up to

Where to Take It Next

Email is a good first workflow because the payoff shows up immediately, and once it works, the same pattern of trigger, classify, act, and review fits plenty of other jobs. For an agent that handles one type of request from start to finish, see how we built an HR automation agent in Copilot Studio. What would you sort first?

Have a question or an idea for a future video? Leave a comment on the full video walkthrough on the Collaboration Simplified YouTube channel.

Contact Us

Questions? Reach out anytime.

Phone

+1-949-667-1624

© 2020–Present Collaboration Simplified. All rights reserved.

Collaboration Simplified® is a registered trademark of Shervin Shaffie.

email

info@cosi.pro