Resources · Make integration

Microsoft Advertising Reports Make integrationAutomate Microsoft Advertising Reports with Make.

Tired of exporting ad reports by hand? The Microsoft Advertising Reports Make integration gives you 6 action modules to request, check and download reports. This guide is for marketers and ops people, and it walks you from connection to a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Microsoft Advertising Reports Make integration do?

It lets Make, a no-code automation tool, ask Microsoft Advertising for a report and hand the result to your other apps. You build a scenario, the automation made of modules, and each module is one brick: here, six actions that request, track and fetch your reports.

A report that lands on its own. The shortest path is Run a Report: one module generates the report type you pick and downloads it, so the next module can store or share it. Good for a media buyer who wants the same view without opening the ad console.

A two step flow for heavier requests. Run a Generate Report Request sends the request and returns a request ID. Download a Report then checks that request and fetches the file once its status reads Success. If you need to see where a request stands, Get a Generate Report Request Status answers with the status and, when data exists, a download URL.

Calls the ready-made modules do not cover. Make a SOAP API Call and Make a REST API call reuse your connection for requests outside the other four modules. They suit someone comfortable reading the Microsoft Advertising API reference.

What Make does not do here: the app has no trigger, so nothing starts the moment a campaign changes. Your scenario runs on a schedule or starts from another app. Make also notes that its own doc page for this app is AI-generated, so check vendor details with Microsoft. For a wider view of the tool, read our Make review, and if you are also looking at n8n, see n8n vs Make. Plan limits are summed up in Make pricing.

Connect

How do you connect Microsoft Advertising Reports to Make?

  1. 01

    Gather your Microsoft credentials

    You need a Microsoft Advertising account and a developer token. In the Azure Portal, open App registrations, pick your app and copy the Client ID and Tenant ID. Under Certificates and secrets, click New client secret, then Add.

  2. 02

    Open the connection window in Make

    Add any Microsoft Advertising Reports module to your scenario and click Create a connection. A connection is your ad account linked to Make once, then reused by all six modules. Give it a clear label in Connection name if you manage several accounts.

  3. 03

    Paste the values and authorize

    Enter the credentials you copied, or follow the on-screen prompts. If Azure asks for a callback URI, use https://www.integromat.com/oauth/cb/microsoft-advertising-reports. Once saved, Make can read your account from every module.

First scenario

Your first scenario with Microsoft Advertising Reports

GoalWhen the scenario's schedule fires, Make asks Microsoft Advertising for a report, then downloads it as soon as it is ready.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add a first module. Since this app has no trigger, the schedule will start the run.

  2. 02

    Request the report

    Search Microsoft Advertising Reports, pick Run a Generate Report Request and select your connection. Fill the fields: Make lists what it can read once you are connected.

  3. 03

    Add the download step

    Click the + on the right and add Download a Report. Map the request ID from the first module so the second one knows which report to fetch.

  4. 04

    Test with Run once

    Click Run once. Each module shows the bundles it received, a bundle being one item passed along. Check that the report arrived before you go further.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default; pick the interval that suits you, then switch the scenario on.

Modules

The six Microsoft Advertising Reports modules

Microsoft Advertising Reports gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Microsoft Advertising Reports1

Download a Report

Action

In MakePolls for a report status and downloads the generated report if its status is "Success".

You get the finished report file handed to the next module, without checking on it yourself. It keeps asking Microsoft for the request status and downloads the report once that status is Success.

When to use it
right after Run a Generate Report Request, mapping the request ID it returned.
Watch out
it needs a request ID from an earlier step, so place it after the module that created that ID.
Microsoft Advertising Reports2

Get a Generate Report Request Status

Action

In MakeRetrieves a current status of the generate report request by report request ID. The module will also return a download URL of the report If the status is "Success" and there is data present for the specified time period,.

This gives you a quick answer on where a report request stands, by its request ID. When the status is Success and the chosen period holds data, it also returns a download URL you can pass along.

When to use it
when you want to branch the scenario on the status, or send the link rather than the file.
Watch out
no data for the period means no URL, so plan that case.
Microsoft Advertising Reports3

Make a SOAP API Call

Action

In MakePerforms an arbitrary authorized SOAP API call.

With this one you reach any authorized SOAP request of the Microsoft Advertising API while Make handles authentication through your connection. It is the way out when none of the report modules does what you need.

When to use it
for an operation you found in the Microsoft documentation that no other module exposes.
Watch out
you write the request yourself, so keep the vendor reference open.
Microsoft Advertising Reports4

Run a Generate Report Request

Action

In MakeMakes a request for generating report and returns the report request ID that can be used for polling the status of a request.

It starts report generation on the Microsoft side and gives you back a request ID, the handle later modules use to follow and fetch that report. Think of it as placing the order.

When to use it
as the first step of a two part flow, paired with Download a Report or the status module.
Watch out
on its own it returns only the ID, not the report, so always add a follow-up module.
Microsoft Advertising Reports5

Run a Report

Action

In MakeGenerates and downloads a report of the selected type.

The one-stop option: pick a report type, and this module generates it and downloads it in the same step. Your scenario stays short, with a single Microsoft Advertising brick before the destination app.

When to use it
when you just want the report delivered and have no need to follow the request status yourself.
Watch out
each run counts as an operation, one execution Make bills on your plan.
Microsoft Advertising Reports6

Make a REST API call

ActionIn the docs only

Make publishes no description for this module; its name points to a REST request sent with your existing connection, as an alternative to the SOAP call module. It helps you reach the API without a second login.

When to use it
when the Microsoft documentation describes a REST request for what you need.
Watch out
test it with Run once first, since no official note explains its settings.
Need help

Need help automating Microsoft Advertising Reports with Make?

A person reads every message.

FAQ

Microsoft Advertising Reports and Make: common questions

01Is the Microsoft Advertising Reports Make integration free?
Yes, on the Make side. Microsoft Advertising Reports is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and lift the active scenario cap. Your Microsoft Advertising account is a separate matter, and its own terms apply.
02What do you need to connect Microsoft Advertising Reports to Make?
You need a Microsoft Advertising account and a developer token. You also register an app in the Azure Portal to get a Client ID, a Tenant ID and a Client secret, then paste those in the Make connection window after clicking Create a connection. If Azure asks for a callback URI, use the Make address given in the connection steps above. Copy the secret before leaving the Azure page, as the setup steps ask.
03Can Microsoft Advertising Reports start a Make scenario in real time?
No. The app has no trigger module, scheduled or instant, so it cannot start a scenario on its own. Two options remain. You can set a schedule on the first module, every 15 minutes by default, and let Run a Report or Run a Generate Report Request open the flow. Or you can start the scenario from another app's trigger and add the Microsoft Advertising Reports modules after it. Either way, test with Run once first.
04What if a Microsoft Advertising Reports module is missing in Make?
Use the two open modules. Make a SOAP API Call sends any authorized SOAP request through your connection, and Make a REST API call covers REST requests the same way, so you are not limited to the four report modules. The app has no generic Make an API Call module beyond those. If the request is tricky to write, the team can help you build it through the contact form on this page.
05Should you use Make or n8n for Microsoft Advertising Reports?
It depends on how you like to work. Make offers 6 ready modules for this app, including a one-step Run a Report and two raw API modules, all set up visually with no code. n8n often has a node for the same app, so check its node list before you decide. Compare the report modules each tool gives you and which editor your team already knows, then test your first flow on the Free plan.