Resources · Make integration

IQM Reports Make integrationAutomate IQM Reports with Make.

Need an IQM Reports CSV export without opening the app each time? The IQM Reports Make integration gives you 2 action modules and no trigger. This guide shows how to link your account, build a first scenario and pick the right module for each job.

Try the IQM Reports integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the IQM Reports Make integration do for you?

The IQM Reports Make integration links your IQM Reports account to Make, a no-code tool where you build a scenario, meaning the automation itself: a chain of modules, each one a brick that acts on one app. Here the app offers two actions, so IQM Reports always sits after something else that starts the flow.

The obvious use is a report on demand. A form, a CRM or any app with a trigger starts the scenario, and Generate CSV Report, as its name suggests, asks IQM Reports for a CSV report. The person who needed the numbers no longer has to log in and export them by hand.

A second pattern keeps the report moving. Once the CSV step has run, the modules you add after it receive what it returned as a bundle, which is one item passed from a module to the next. You map that bundle into the app where your team actually reads reports.

The third case covers everything the two named modules leave out. Make an API Call reaches any endpoint of the IQM Reports API with the same connection, which is handy when a report needs a setting the CSV module does not expose.

Be aware of one real limit: Make's own documentation for IQM Reports is flagged as limited, with no module descriptions and no official connection steps. Test each module with Run once before you rely on it. If you get stuck, the Make troubleshooting guide and the Make training are good next stops. The same app may also exist as an n8n node; the n8n vs Make comparison explains how the two tools differ.

Connect

How do you connect IQM Reports to Make?

  1. 01

    Add a module and open the connection form

    In your scenario, search for IQM Reports and pick one of its two modules. Click Create a connection. A connection is your IQM Reports account linked to Make once, then reused by every IQM Reports module you add later.

  2. 02

    Give the connection a clear name

    This step is optional but worth ten seconds. A name like the client or the workspace it belongs to makes the right account easy to spot when several scenarios share the same app.

  3. 03

    Authorize Make, then save

    Depending on what IQM Reports asks for, you either approve Make on the IQM Reports page or paste the key the app gives you. Click Save and the module is ready to fill in.

First scenario

Your first scenario with IQM Reports

GoalWhen another app starts the scenario, Make asks IQM Reports for a CSV report and hands the result to the next module.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since IQM Reports has no trigger, this first module comes from the app that decides when a report is needed.

  2. 02

    Add Generate CSV Report

    Click the + on the right of that first module, search for IQM Reports and pick Generate CSV Report. Select your connection, or click Create a connection if this is the first time.

  3. 03

    Fill the fields and map the data

    Complete the fields Make shows once the connection exists. Where a value should come from the first module, map it from that module's output instead of typing it by hand.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time, and you can open each module to read the bundles it received. Check what Generate CSV Report returned before adding anything after it.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (a new scenario checks every 15 minutes by default), then switch the scenario on. From now on, each start in the first app leads to a fresh report request.

Modules

What each IQM Reports module does

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

IQM Reports1

Generate CSV Report

ActionIn the docs only

This action asks IQM Reports for a report in CSV form, so the data reaches your scenario without a manual export from the app. It is the module most readers come to this page for.

When to use it
any time a report should be produced because something happened in another app, such as a request logged by a colleague.
Watch out
Make's documentation gives no description of this module, so open the result after Run once before mapping it further.
IQM Reports2

Make an API Call

ActionIn the docs only

With this module you reach any endpoint of the IQM Reports API while keeping the connection you already created, which fills the gap left by an app that has only one ready-made action.

When to use it
when the result you need is not a CSV report, or when the report calls for an option Generate CSV Report does not offer.
Watch out
you write the request yourself, so check what the IQM Reports API expects before you set it up.
Need help

Need help automating IQM Reports with Make?

A person reads every message.

FAQ

IQM Reports and Make: common questions

01Is the IQM Reports Make integration free?
Yes, IQM Reports is a standard app in Make, so it is available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one operation being one module run on one bundle. This page does not cover what IQM Reports itself charges.
02What do you need to connect IQM Reports to Make?
An IQM Reports account and a Make account are enough to start, since Make's documentation lists no other prerequisite for this app. You add an IQM Reports module, click Create a connection, optionally name it, then either approve Make on the IQM Reports page or paste the key the app provides, and click Save. The documentation for this app is marked as limited, so if the connection form asks for something unexpected, the safest move is to check your IQM Reports account settings.
03Does IQM Reports trigger Make scenarios in real time?
No, because IQM Reports has no trigger module in Make, neither scheduled nor instant. A scenario that uses it has to start another way. The first option is a trigger from a different app, so the report is requested when that app reports an event. The second is to begin with an IQM Reports action and set a schedule on it: a new scenario runs every 15 minutes by default, and the Free plan cannot go below that interval.
04What if the IQM Reports module you need is missing in Make?
Use Make an API Call. It is available for IQM Reports and reaches any endpoint of the app's API through the connection you already have, so anything beyond Generate CSV Report stays within reach. The catch is that Make's documentation for this app is flagged as limited, with no module descriptions, so what the IQM Reports API accepts becomes your main guide. Test each call with Run once and read the returned bundle before building on it.
05Should you use Make or n8n for IQM Reports?
It depends on the tool your team already works in, because both can host an IQM Reports automation. Make offers IQM Reports as a standard app with 2 modules, Generate CSV Report and Make an API Call, available from the Free plan. The same app often has an n8n node as well. Compare the two on the modules each one offers for IQM Reports and on how you like to build, rather than on general claims, and try the scenario in the tool you already use.
Same platform

Other docs you might need on this stack.

Browse all integrations