FlowRunner
PricingContact
Theme
Start Free

Microsoft Advertising Reports

Advertising

Automate Microsoft Advertising performance reporting: agents submit report requests for campaign, keyword, and audience metrics, poll until generation completes, and retrieve the download URL for the finished file.

3 actions OAuth available
The Monday 6am schedule fires for the weekly paid search review
Submit Generate Report requests a CampaignPerformanceReportRequest with daily aggregation and the spend, clicks, and conversions columns
Poll Generate Report Status runs every few seconds until Status returns Success with a ReportDownloadUrl
The agent downloads the file promptly, since the URL expires within a day
Parsed rows are compared against last week's baseline for spend spikes and conversion drops
The digest posts to Slack with the anomalies called out and the raw file attached
The paid search manager reads the flagged campaigns and decides which budget changes actually get made

What This Integration Enables

Microsoft Advertising's Reporting API is asynchronous SOAP: you submit a request, you poll for status, and you collect a download URL that lives for at most a day. That three-step dance is exactly the kind of work that should never belong to a person, and it is the whole reason this connector exists. FlowRunner agents run the loop end to end for any v13 report type, campaign, keyword, ad group, search query, geographic, audience, or budget, with the aggregation, time range, and column set the request calls for. - Generate any Bing Ads v13 performance report with a custom column set and aggregation - Poll until Success or Error without a human waiting at a screen - Retrieve the download URL and fetch the file before its one-day validity lapses - Reach advanced or newly released report operations through Call SOAP Operation with authentication headers injected automatically This is a read-side connector: it spends time and API quota, not ad budget. The human's role sits downstream, where report findings turn into bidding and budget decisions that FlowRunner routes through [human-in-the-loop](/concepts/human-in-the-loop) review before any spend-side system acts on them.

Without FlowRunner

Reporting is a browser chore Someone logs into the Microsoft Advertising UI, configures the export, waits, downloads, and pastes into a sheet
Bing data arrives late to the party Cross-network reviews run on Google Ads data because the Microsoft side was too tedious to pull
Async means babysitting The report is not ready when requested, so the human either waits at the screen or forgets to come back

With FlowRunner

The submit-poll-download loop is the agent's job Requests go out on schedule, polling runs until Success, and the file is fetched before the URL expires
One report across networks Microsoft and Google performance land in the same sheet the same morning, in the same column layout
Humans read exceptions, not exports The team sees flagged movers with context, not a raw CSV they still have to interpret

Use Case Scenarios

The daily performance sheet nobody compiles

Each morning the agent calls Submit Generate Report for a campaign performance report with daily aggregation, polls with Poll Generate Report Status until the ReportDownloadUrl arrives, downloads the file, and appends the parsed rows to [Google Sheets](/integrations/google-sheets). The finance-facing spend tracker and the marketing dashboard read from the same sheet, so both teams argue from one set of numbers.

Cross-network paid search in one view

The weekly agent pulls Microsoft campaign metrics through the submit-poll-download loop while a parallel branch queries [Google Ads](/integrations/google-ads) with GAQL. Both branches land in a unified report keyed on campaign naming conventions, and a [Slack](/integrations/slack) summary ranks the week's movers across both networks. The Microsoft side stops being the network that gets reviewed only when something looks wrong.

Keyword-level escalation with a person on the decision

A KeywordPerformanceReportRequest runs nightly. The agent compares CTR and conversion trends per keyword against trailing averages and flags decliners that are still spending. Instead of touching bids, it opens a review with the evidence: keyword, spend, trend, suggested action. The paid search manager approves pauses or bid changes, and those decisions flow to the campaign management side with the human's name on them.

Human-in-Loop Highlight

Poll Generate Report Status returns a ReportDownloadUrl that is valid for at most one day, and the request ID it polls dies on the same clock, so a missed pickup means resubmitting and regenerating the report from scratch. The agent owns that deadline: it polls until Success and downloads immediately, which is precisely the babysitting work humans do badly. The judgment call this connector feeds is different. When the downloaded report shows a campaign burning spend with collapsing conversions, the agent does not reach into bidding on its own. It packages the report rows, the trend, and a proposed change, and the paid search manager decides. Report generation is automated because it is reversible; budget decisions are gated because they are not.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

3 actions

Reporting

2
  • Submit Generate Report Submits an asynchronous report request to the Microsoft Advertising v13 Reporting API and returns a Report Request ID to poll. Takes the derived report request type, report name, aggregation, time period, and columns, or Custom Body XML for full control over scope, filters, and custom date ranges. The ID is valid for at most one day.
  • Poll Generate Report Status Polls a submitted report request by ID and returns Pending, Success with a ReportDownloadUrl, or Error. Called repeatedly until the report resolves; it returns the status and URL, not the report data itself, so the download happens as its own step.

Advanced

1
  • Call SOAP Operation Escape hatch for any v13 Reporting Service SOAP operation not covered by a dedicated action. Provide the SOAPAction name and raw inner request XML; the service wraps it in the correct envelope, injects the AuthenticationToken, DeveloperToken, CustomerId, and CustomerAccountId headers automatically, and returns the raw XML response.

Frequently Asked Questions

What can FlowRunner do with Microsoft Advertising Reports?

FlowRunner agents can run Submit Generate Report, Poll Generate Report Status, and Call SOAP Operation in Microsoft Advertising Reports.

Does connecting Microsoft Advertising Reports to FlowRunner require OAuth?

Yes. Microsoft Advertising Reports connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Microsoft Advertising Reports trigger a FlowRunner workflow automatically?

Microsoft Advertising Reports doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Microsoft Advertising Reports

$100 in credits. No card required. Connect in minutes.