IQM Reports
AdvertisingConnect AI agents to IQM, a programmatic advertising demand-side platform. Agents build and run campaign reports, schedule them to recur, and download the results for downstream analysis.
What This Integration Enables
This is a reporting connector on a demand-side platform, and that boundary is the point rather than a limitation to apologize for. Nothing here changes a bid, pauses a campaign, moves budget or touches creative. What it does is make the reporting surface of IQM something a workflow can drive end to end. That is where the recurring manual cost in programmatic media actually lives: not in the buying decision, which a person should be making anyway, but in the exports, reformats and distributions that surround it.
Agents run a saved report by ID or an ad-hoc one by supplying dimensions, metric columns, a date range and a timezone, with pagination and sorting, and they generate a downloadable CSV or XLS URL the same two ways. They list saved reports with filters and search, read a single report's full configuration including its scheduling details, and create, update, duplicate and permanently delete report definitions. They create a recurring email delivery of a saved report to a subscriber list, update that schedule's recipients, file type, frequency, delivery day or end date, and remove it. Two discovery operations make the rest usable: Get Dimensions and Metrics returns the full catalog of dimension filters and metric column keys with their IDs and display names, and Get Timezones returns the timezone IDs the report actions expect.
Three details determine whether a report is right rather than merely successful. Dimensions are supplied as a serialized JSON string of filter objects, so a malformed or mistyped filter produces a report that runs and reports the wrong grouping rather than an error. Dates are Unix epoch timestamps in milliseconds and a report's date range cannot exceed one year. And Download Report returns no URL at all when the report has no data, which a flow must handle as a distinct case rather than as a failure. There is no trigger and no webhook subscription in this surface, so every recurrence is either a FlowRunner schedule driving Execute Report or an IQM-side email schedule created with Schedule Report Email.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Daily campaign metrics into the warehouse
Each morning the agent calls Get Dimensions and Metrics once to resolve the campaign, device type and gender filters and the impression, click, CTR and spend column keys, then runs Execute Report for the previous day with the account's timezone ID from Get Timezones. It pages through the rows and appends them to BigQuery or a tracker in Google Sheets. Because the dimension set is resolved from the catalog rather than retyped, yesterday's rows and today's rows group the same way and can actually be compared.
A file for a client, produced and delivered by the flow
A client expects a weekly performance file. The agent calls Download Report for the saved report ID with the file type set, receives the URL, and posts it to the account channel in Slack with the period and the campaigns covered. When the report has no data for the period IQM returns no URL at all, so the agent reports that explicitly as an empty period rather than passing along a broken link or a silent success.
Report definitions managed as a set
A new advertiser is onboarded and needs the same six report shapes the agency runs for everyone else. The agent lists the existing definitions with List Reports, reads each configuration with Get Report, and calls Duplicate Report with a new name per report, then Update Report to swap the campaign filter to the new advertiser. Retired definitions are removed with Delete Report, which also removes any email schedule attached to them and cannot be undone, so the flow lists what it is about to delete before it deletes anything.
Human-in-Loop Highlight
Schedule Report Email is the gate on this connector, because it is the only action here that keeps acting after the flow finishes. Every other operation produces rows or a file that a person can throw away. This one creates a recurring delivery of ad-serving metrics, including spend, as a CSV or XLS to a named subscriber list on a frequency and delivery day, running until the end date. Delete Report Schedule stops the next send. It does not recall the one already sitting in somebody's inbox, and on a media account the subscriber list frequently reaches outside the agency to the advertiser, so a wrong dimension set or a wrong recipient is a disclosure rather than a formatting mistake. The agent therefore proves the report before it schedules it. It runs Execute Report once against the same definition, and attaches the first rows, the resolved dimensions and metric columns from Get Dimensions and Metrics, and the timezone name from Get Timezones. Then it asks the account lead: "Ready to schedule [report name] as CSV, weekly on [day] until [date], to these four subscribers. Sample rows and the exact metric set are below, and spend is included. Confirm the recipients and the metrics, or amend." The lead confirms and the agent calls Schedule Report Email. This is what human-in-the-loop is for: not slowing down the reporting, but putting a person on the one decision that keeps repeating itself after everyone has stopped watching.
Agent Capabilities
13 actionsRunning Reports
2- Execute Report Runs a report and returns the resulting rows of ad-serving metrics. Execute a saved report by passing its ID, or run an ad-hoc report by supplying dimensions, columns, a date range which cannot exceed one year, and a timezone. Supports pagination and sorting.
- Download Report Generates a downloadable file URL, CSV or XLS, for a report. Download a saved report by ID, or an ad-hoc report by supplying file type, dimensions, columns, date range, and timezone. If the report has no data, no URL is returned.
Report Definitions
6- List Reports Retrieves a paginated list of saved reports, with optional filtering by customer IDs and a search term, and configurable sorting. Returned report IDs can be used with the Get, Execute, Update, Delete, Duplicate, and scheduling actions.
- Get Report Retrieves the full configuration of a single saved report by its ID, including its name, date range, dimensions, columns, timezone, request type, and any email scheduling details.
- Create Report Creates and saves a new report definition from the given name, dimensions, columns, date range which cannot exceed one year, and timezone. Returns the new report ID, which can then be executed, downloaded, or scheduled.
- Update Report Updates the configuration of an existing saved report. Only the fields you provide are changed. The report is identified by its ID, and any supplied date range cannot exceed one year.
- Delete Report Permanently deletes a saved report by its ID, along with any associated email schedule. This action cannot be undone.
- Duplicate Report Creates a copy of an existing report identified by its ID, optionally giving the copy a new name. Returns the ID of the newly created report.
Scheduled Delivery
3- Schedule Report Email Creates a recurring email delivery schedule for a saved report, sending it as CSV or XLS to one or more subscribers. For non one-time frequencies you must set a delivery day and an end date. Optionally enable a running total that starts from the earliest campaign start date. This is the action routed for human sign-off.
- Update Report Schedule Updates an existing email delivery schedule for a report, identified by the report ID. Only the fields you provide are changed, such as the subscriber list, file type, frequency, delivery day, or end date.
- Delete Report Schedule Removes the email delivery schedule for a report, identified by the report ID. The report itself is not deleted, and previously delivered emails are not affected.
Reference Data
2- Get Dimensions and Metrics Retrieves the full catalog of report dimensions and metrics available on the IQM platform, including their IDs, keys, display names, and categories. Use these keys to build the dimensions and columns for the report actions.
- Get Timezones Retrieves the list of timezones supported by the IQM platform, including each timezone's ID and name. Use the returned IDs for the timezone parameters of the report actions.
Frequently Asked Questions
What can FlowRunner do with IQM Reports?
FlowRunner agents can run Execute Report, Download Report, and List Reports in IQM Reports, plus 10 more actions.
Does connecting IQM Reports to FlowRunner require OAuth?
IQM Reports uses a custom authentication method to connect to FlowRunner.
Can IQM Reports trigger a FlowRunner workflow automatically?
IQM Reports doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with IQM Reports
$100 in credits. No card required. Connect in minutes.