Resources · Make integration

Microsoft Power Automate Make integrationAutomate Microsoft Power Automate with Make.

Need a Make scenario to launch a desktop flow and hand back its result? The Microsoft Power Automate Make integration does exactly that with 1 action module. This guide covers the Entra ID connection, a first scenario and the questions that follow.

Enterprise app This app is reserved to Make's Enterprise plan.

Try the Microsoft Power Automate integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Microsoft Power Automate Make integration do for you?

The Microsoft Power Automate Make integration lets a Make scenario (the automation you build in Make, a chain of modules) start one of your Power Automate desktop flows and wait until it returns a result. Something happens in another app, and the desktop flow you already built runs without anyone clicking it.

Kick off a desktop flow from a new record. A module (one brick of a scenario) from another app notices a new row or a new form entry, then Trigger a Desktop Flow starts the matching flow in Power Automate. The result comes back into Make, so the next module can use it.

Chain the result into another tool. Because the module waits for the flow to finish, what the flow sends back travels as a bundle (one item passed from a module to the next) toward a sheet, a CRM or a message. If Airtable is where your team logs requests, the Airtable Make integration pairs well here.

Run a desktop flow on Make's clock. With a schedule on the first module, Make starts the scenario at the interval you set, every 15 minutes by default, and the desktop flow follows.

Know the limits before you start. The app sits on Make's Enterprise plan, it has a single module, no trigger and no Make an API Call module. Plan budgets are covered in Make pricing. The same app often has a node in n8n as well; n8n vs Make lays out how the two tools differ.

Connect

How do you connect Microsoft Power Automate to Make?

  1. 01

    Register an app in Entra ID

    In the Microsoft Entra admin center, open App registrations, click New registration, name it and pick the Supported account types. If asked for a callback URI, paste https://www.integromat.com/oauth/cb/microsoft-power-automate, then click Register.

  2. 02

    Collect the three credentials

    From the Overview page, copy the Client ID and the Directory (tenant) ID. Under Certificates and secrets, click New client secret, add a description, choose an expiration period, click Add and copy the Client secret value.

  3. 03

    Create the connection in Make

    Add the Microsoft Power Automate module to your scenario and click Create a connection. A connection is your Microsoft account linked to Make once. Give it a Connection name if you like, paste the credentials and follow the on-screen sign-in.

First scenario

Build your first scenario with Microsoft Power Automate

GoalWhen something happens in another app, Make starts your desktop flow in Microsoft Power Automate and waits for its result.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since Power Automate has no trigger in Make, this first module comes from the app where the event starts.

  2. 02

    Pick the starting app

    Search that app by name, choose the module that watches for your event and link its account with Create a connection. Fill its fields; Make lists the folders, sheets or objects it can read.

  3. 03

    Add Trigger a Desktop Flow

    Click the + on the right of the first module, search Microsoft Power Automate and pick Trigger a Desktop Flow. Select your connection, then map data from the previous module into the fields.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module's bubble to read the bundles it received, and check that the desktop flow ran and sent its result back.

  5. 05

    Schedule and switch on

    If the first module runs on a schedule, set it (every 15 minutes by default), then switch the scenario on. Each module run on a bundle counts as one operation, the unit Make bills on your plan.

Modules

What the Microsoft Power Automate module does

Microsoft Power Automate gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Microsoft Power Automate1

Trigger a Desktop Flow

Action

In Make“Triggers a Desktop Flow and wait for the result.”

This action starts one of your Power Automate desktop flows from inside a Make scenario, then holds the scenario until the flow finishes and returns its result. You get the output back in Make, ready to map into the next module.

When to use it
a desktop flow already handles a task well, and you want an event in another app to launch it instead of a person.
Watch out
the module is an action, not a trigger, so the scenario needs another app's module or a schedule to start.
Need help

Need help automating Microsoft Power Automate with Make?

A person reads every message.

FAQ

Microsoft Power Automate and Make: common questions

01Is the Microsoft Power Automate Make integration free?
No. Microsoft Power Automate is an enterprise app in Make, reserved to the Enterprise plan, so the Free plan cannot use it. For context, the Free plan gives 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run and access to the standard apps. Paid plans (Core, Pro, Teams and Enterprise) count usage in operations per month. On the Microsoft side, you also need your own Power Automate subscription; check Microsoft's pricing page for that part, since this page does not quote any price.
02What do you need to connect Microsoft Power Automate to Make?
You need an active Microsoft account with access to a Dataverse environment and permissions to authenticate through OAuth. In the Microsoft Entra admin center, you register an app under App registrations, then collect three values: the Client ID, the Directory (tenant) ID and a Client secret created under Certificates and secrets. Back in Make, you add the module, click Create a connection and paste those values. Copy the secret as soon as it appears, because Microsoft will not show it again once you leave the page.
03Can a Make scenario react to Microsoft Power Automate events in real time?
Not from this app, because Microsoft Power Automate has no trigger module in Make. Its only module, Trigger a Desktop Flow, is an action. To start a scenario, you have two options. The first is a trigger from another app: when that app notices a new record, the desktop flow runs next. The second is a schedule on the first module, which runs every 15 minutes by default and can go down to 1 minute on paid plans. The speed then depends on the trigger or schedule you choose.
04What if the Microsoft Power Automate module you need is missing in Make?
It depends on what you need. The app has a single module, Trigger a Desktop Flow, and no Make an API Call module, so you cannot reach other Power Automate features through a generic request. If the task lives in another tool, look for that tool's own app in Make, since the catalog holds more than 3,000 standard apps. If the need goes beyond what one module offers, the team behind this guide can help you design the scenario through the contact form below.
05Should you use Make or n8n with Microsoft Power Automate?
It depends on your setup. On Make, this app requires the Enterprise plan and offers one action, Trigger a Desktop Flow, with no trigger and no generic API module. The same app often has a node in n8n too, so check what that node covers before you decide. Compare the two on the criteria that matter to your team: the modules available for this app, the plan you already pay for and who will maintain the scenarios. The n8n vs Make comparison linked above goes through those criteria in detail.
Same platform

Other docs you might need on this stack.

Browse all integrations