What we do
Tools
Industries
Department
How we workLet's talk →
Home/MS Teams/Teams Workflow
Microsoft Teams

How to Build a Teams Workflow, and When Power Automate Takes Over

The Workflows app in Teams is Power Automate with a shortcut into it: templates for posting alerts, running approvals and sending reminders, built without leaving Teams. It's also what Microsoft now points you to since Office 365 connectors were retired, so if an old incoming webhook stopped posting, this is the replacement. Here's where to click, then the limits worth knowing before a workflow becomes something the business relies on.

Find Workflows in Teams

From the app: open Apps on the left, search for Workflows, and open it. Pick a template from the Create tab or start from blank.

Apps Workflows Create

From a channel: hover the channel name, open More options and choose Workflows. Templates offered here are already pointed at that channel.

Channel More options (...) Workflows

From a message: workflows that run on a message show up under the message's More options, so people can, for example, send a message to a list or start an approval from it.

What catches Teams workflows later

None of these show up in the first week. They show up when the workflow is doing real work.

The owner leaves, and the workflow goes with them

How you'll know: Alerts or approvals stop after someone changes role or leaves the company, and nobody else can edit the flow.

Fix: Add co-owners in Power Automate now, or move important flows to a shared service account your IT team manages. Do it before the person leaves, not after.

The connector you need is premium

How you'll know: You add an HTTP call, a SQL Server step, a custom connector or an on-premises gateway, and Power Automate asks for a premium license.

Fix: Microsoft 365 includes Power Automate with standard connectors such as Teams, SharePoint and Outlook. Premium ones need a Power Automate Premium (per user) or Process (per flow) license. Price that against building the connection outside Power Automate.

Volume outgrows the license

How you'll know: A flow that ran fine in testing throttles or fails when it processes hundreds of records a day.

Fix: Every license has request limits per day. Check the current numbers for your license in Microsoft's Power Platform limits page, and batch work where you can.

Nobody dares edit it

How you'll know: A flow with a dozen nested conditions across several systems, and one person who understands it. Failures mean clicking through run history to find which branch broke.

Fix: That's the point where it should become code with logging and a test, rather than a bigger diagram.

Replacing an Office 365 connector with a Workflows webhook

If a monitoring tool, build server or form used to post into a channel through an incoming webhook connector, this is the swap.

  1. 1

    Pick the webhook template

    Channel More options (...) Workflows

    Search for Post to a channel when a webhook request is received. There are variants that only accept requests from specific users or from people in your tenant, if you want to lock it down.

  2. 2

    Choose the team and channel, then save

    Teams creates the workflow and shows a new webhook URL. Copy it. Anyone holding that URL can post into the channel, so store it like a password.

  3. 3

    Point the sending system at the new URL

    Replace the old connector URL in the tool that sends alerts. It still sends an HTTP POST with a JSON body.

    Watch for: the message format. Workflows post Adaptive Cards only. Tools that sent the old connector message card format need their payload changed, or the post fails or arrives blank.

  4. 4

    Test, then check who owns it

    Send a test alert. Then look at the workflow's owner. It belongs to the person who created it, not to the team or channel.

    Watch for: private channels. The Workflows app can't post there as the flow bot, so it posts on behalf of a user instead.

When a Teams workflow should become something else

For a department's reminders, approvals and alerts, the Workflows app is the right tool, and it's already paid for. Anything built from a Teams template can be opened in the full Power Automate designer when it needs more steps.

The trouble starts when a flow the whole company depends on belongs to one person, needs a premium connector just to reach one API, or holds business rules nobody can read. n-frames rebuilds those as a small service that runs under an account IT controls, logs every run, and still posts into Teams through a Workflows webhook or a Teams bot, so people see the same messages in the same channels.

Questions people ask

What's the difference between Teams Workflows and Power Automate?

They're the same engine. The Workflows app in Teams is a simpler way in, with templates you can launch without leaving Teams. Anything built there can be opened in the full Power Automate designer for more steps and connectors.

What replaced Office 365 connectors in Teams?

Workflows. Microsoft retired Office 365 connectors in Teams, and the replacement for an incoming webhook is the Post to a channel when a webhook request is received template, which gives you a new URL to send alerts to. Messages need to be Adaptive Cards.

Is Power Automate free with Microsoft 365?

Most Microsoft 365 business plans include Power Automate for standard connectors such as Teams, SharePoint and Outlook. Premium connectors (HTTP, SQL, custom connectors, on-premises data) and higher volumes need a separate Power Automate license.

Can a Teams workflow call an external API?

Yes, with the HTTP action, but that's a premium connector, so it needs a Power Automate Premium or per-flow license beyond what Microsoft 365 includes. Without one, a flow can only use standard connectors.

How many actions can a Power Automate flow run per day?

It depends on the license. Each one has its own daily request limit, listed on Microsoft's Power Platform limits page. A flow handling hundreds or thousands of records a day can reach it far sooner than a flow tested with a few sample runs.

Can I build approval logic that checks more than one condition in Power Automate?

Yes, with nested condition steps or a switch. Once a flow has many branches checking live data from several systems, it gets hard to read and maintain in the designer, and that's usually the sign the process has outgrown it.

Why does my workflow post as me instead of the Workflows bot?

Usually because the channel is private. The Workflows app can't post as the flow bot in private channels, so it posts on behalf of a user. Shared and standard channels can use the bot.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.