Resources · Make integration

Reportei Make integrationAutomate Reportei with Make.

What if every Reportei goal, report and client view could start the next task by itself? The Reportei Make integration gives you 11 modules: 7 instant triggers and 4 actions. This guide is for agencies and marketers who report to clients, and it walks you from the connection to a working first scenario.

Try the Reportei integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Reportei Make integration do for you?

The Reportei Make integration links your Reportei account to Make, a visual tool where you build a scenario: the automation itself, a chain of modules that each do one job. Reportei tells Make when something happens (a goal is reached, a report is created, a client opens a report) and Make can create reports, dashboards and timeline milestones for you.

Know the moment a client reads the report. Watch Report Viewed fires when a client opens a report. Route that signal to your CRM or your team chat so the account manager follows up while the numbers are fresh in the client's head.

Turn a missed goal into a visible note. Watch Goal Not Achieved fires when a control goal period ends below target. Pair it with Add Milestone to Timeline and the miss shows up in the client's timeline, next to the data, instead of getting lost in an inbox.

Open a new client without the setup chores. When a deal closes in another app, Create a Dashboard and Create a Report prepare the Reportei side, so onboarding starts with something to show.

What Make does not do here: there is no search module, so the scenario cannot look up an existing report by itself; Make an API Call covers the parts of the Reportei API the listed modules leave out. The Reportei doc in Make also carries a warning that it was written with AI help, so check any detail that matters with Reportei. If you are weighing tools, read the n8n vs Make comparison; to learn the editor properly, the Make training helps, and the Make pricing page explains what each plan allows.

Connect

How do you connect Reportei to Make?

  1. 01

    Generate an API token in Reportei

    In Reportei, open Settings, then API Tokens, and click Generate new token. Copy the token shown on screen. You need an active Reportei account for this menu to be there.

  2. 02

    Add a Reportei module and create the connection

    In your scenario, add any Reportei module and click Create a connection. A connection is your Reportei account linked to Make once, then reused by every Reportei module. You can type a label in Connection name if you like.

  3. 03

    Paste the token and save

    Paste the API token you copied, or follow the instructions Make shows on screen, then save. From now on, Reportei modules in any scenario can pick this connection from the list instead of asking again.

First scenario

Your first scenario with Reportei and Make

GoalWhen a control goal period ends without being reached in Reportei, Make adds a milestone to the client's timeline.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Search for Reportei and pick Watch Goal Not Achieved as the first module.

  2. 02

    Set up the webhook and connection

    Click Create a webhook, then Create a connection and paste your API token. Save the webhook so Reportei knows where to call Make when a goal is missed.

  3. 03

    Add the milestone action

    Click the + on the right of the trigger and choose Add Milestone to Timeline. Map the goal data from the trigger into the milestone so the timeline entry explains what was missed.

  4. 04

    Test with Run once

    Click Run once. Make waits for the next call from Reportei; each item it receives is a bundle. Read the bundles each module received to check what came in and what went out.

  5. 05

    Switch the scenario on

    Turn the scenario on. Because the trigger is instant, it starts as soon as Reportei calls the webhook, and each module that runs uses one operation, the unit Make counts on your plan.

Triggers

What starts a Reportei scenario

7 modules start a scenario when something happens in Reportei. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Reportei as soon as it happens.

Reportei1Watch Automation Executed

Watch Automation Executed

Instant trigger

In Make“Triggers when an automation runs in Reportei.”

Starts your scenario each time one of your Reportei automations runs, so work that Reportei already does can hand off to other tools without you copying anything across.

How it fires
instant: Reportei calls Make through a webhook as soon as the automation runs.
When to use it
an automation you built in Reportei should leave a trace in your project tool each time it runs, so the team sees what went out.
Watch out
the webhook has to be created from this module before anything arrives, so use Create a webhook first and keep the scenario switched on.
Reportei2Watch Goal Achieved

Watch Goal Achieved

Instant trigger

In Make“Triggers when a control goal is reached in Reportei.”

Gives you a signal the moment a control goal you set in Reportei is reached, which is the right time to share good news with the client or the team.

How it fires
instant: Reportei calls Make through a webhook as soon as the goal is reached.
When to use it
a campaign hits its lead target and you want a congratulation message in the client's channel, or a milestone on their timeline with Add Milestone to Timeline.
Watch out
it only covers goals set up as control goals in Reportei, so a metric without a goal will never start the scenario.
Reportei3Watch Goal Not Achieved

Watch Goal Not Achieved

Instant trigger

In Make“Triggers when a control goal period ends without being achieved.”

Warns you when a control goal period closes without the target being hit, so a miss turns into an action instead of a surprise during the next client call.

How it fires
instant: Reportei calls Make through a webhook as soon as the goal period ends short.
When to use it
you want the account manager to get a task in your CRM, or the miss logged on the client timeline, whenever a target slips.
Watch out
it reacts when the period ends, not while the numbers are trending down, so it will not act as an early warning.
Reportei4Watch New Dashboard Created

Watch New Dashboard Created

Instant trigger

In Make“Triggers when a new dashboard is created in Reportei.”

Lets the rest of your stack know that a new dashboard exists in Reportei, so links and access can be shared without anyone chasing the account team.

How it fires
instant: Reportei calls Make through a webhook as soon as the dashboard is created.
When to use it
each new dashboard should be announced in the client's shared channel or added to a list of deliverables in a spreadsheet.
Watch out
dashboards created by Create a Dashboard may start it as well, so test with Run once before mixing the two in one setup.
Reportei5Watch New Report Generated

Watch New Report Generated

Instant trigger

In Make“Triggers when a new report is created in Reportei.”

Hands each freshly created Reportei report to the next step of your process, whether that is an approval, a message to the client or an entry in a tracker.

How it fires
instant: Reportei calls Make through a webhook as soon as the report is created.
When to use it
a senior team member reviews every report before it goes out, and you want the review task created without a reminder.
Watch out
reports built by Create a Report may start it too, so avoid a setup where this trigger leads to Create a Report.
Reportei6Watch Report Viewed

Watch Report Viewed

Instant trigger

In Make“Triggers when a client see a report”

Tells you when a client actually opens a report, which is the most useful signal for timing a follow-up call or message.

How it fires
instant: Reportei calls Make through a webhook as soon as the client views the report.
When to use it
the account manager gets a ping in the team chat, or your CRM records the view on the client record, so the next conversation starts from data the client just saw.
Watch out
each view can start a run and use operations, so test with Run once to see what a single view sends before you build on it.
Reportei7Watch Timeline New Milestone

Watch Timeline New Milestone

Instant trigger

In Make“Triggers when a new milestone is added to the timeline.”

Picks up every new milestone added to a Reportei timeline, so the events you record for a client can travel to other tools and stay in sync.

How it fires
instant: Reportei calls Make through a webhook as soon as the milestone is added.
When to use it
a launch or a budget change is logged on the timeline and you want the same note in your project board or the client's shared channel.
Watch out
Add Milestone to Timeline creates milestones too, so do not chain the two: the new milestone could start the scenario again.
Modules

What Make can do in Reportei

Reportei gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Reportei1

Add Milestone to Timeline

Action

In Make“Adds a new event to the timeline in Reportei.”

Writes a new event on a Reportei timeline for you, so context such as a campaign launch or a missed goal sits right next to the numbers the client reads.

When to use it
another app records something that explains a change in results, like a new ad budget in your project tool.
Watch out
keep it away from scenarios started by Watch Timeline New Milestone, since the milestone it writes could start that trigger again.
Reportei2

Create a Dashboard

Action

In Make“Creates a new dashboard in Reportei.”

Builds a new Reportei dashboard from your scenario, so a new client or a new project gets its space without anyone opening Reportei to click through the setup.

When to use it
a deal is marked as won in your CRM and the dashboard should be ready before the kickoff call.
Watch out
run a test with Run once and check the result in Reportei before switching the scenario on.
Reportei3

Create a Report

Action

In Make“Creates a new report in Reportei.”

Produces a new Reportei report from Make, which saves the manual step of starting one each time a client or a campaign needs it.

When to use it
a campaign ends in your ad or project tool and the wrap-up report should exist right away for the account manager to finish.
Watch out
a report created here may also start Watch New Report Generated, so check that no scenario sends it back to this module.
Reportei4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Reportei API with the connection you already set up, which is how you cover a need the three ready-made actions do not handle.

When to use it
you need to read or change something in Reportei that has no module of its own, such as finding an existing item before acting on it.
Watch out
you write the request yourself, so keep the Reportei API documentation open while you build it.
Need help

Need help automating Reportei with Make?

A person reads every message.

FAQ

Reportei and Make: common questions

01Is the Reportei Make integration free?
Yes, on the Make side. Reportei is a standard app, so its modules work on the Free plan, like the 3000+ other standard apps. The Free plan limits you to 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans remove the cap on active scenarios and allow longer runs. You still need your own active Reportei account, which is billed by Reportei, not by Make.
02What do you need to connect Reportei to Make?
You need an active Reportei account and an API token. In Reportei, go to Settings, then API Tokens, click Generate new token and copy it. In Make, add a Reportei module, click Create a connection, give it a name if you want and paste the token. Because every Reportei trigger is instant, Make first asks you to click Create a webhook, and the connection is created inside that step. After that, every Reportei module can reuse the same connection.
03Do Reportei triggers in Make work in real time?
Yes. All 7 Reportei triggers are instant: Reportei calls Make through a webhook as soon as the event happens, whether that is a goal reached or missed, a new report or dashboard, a report viewed by a client, an automation run or a new timeline milestone. You do not rely on the 15 minute default schedule that polling triggers use. Two conditions apply: the scenario is switched on, and the webhook was created from the trigger module, or no call will arrive.
04What if a Reportei module is missing in Make?
It depends on what you need, and Make an API Call is usually the answer. It calls any endpoint of the Reportei API with the connection you already have, so you can cover actions or lookups the 4 listed actions leave out. There is no search module for Reportei in Make, which is the most common gap. Also note that the Reportei documentation in Make is marked as AI-generated, so confirm any important detail with Reportei before relying on it.
05Should you use Make or n8n for Reportei?
It depends on the tool you already work in. On Make, Reportei comes with 11 modules, 7 of them instant triggers, plus Make an API Call for anything else, and the whole setup happens in a visual editor with a guided connection. The same app often exists on n8n too, so check the node there before choosing. The comparison worth doing is practical: which modules you need, where the rest of your automations already run, and which editor your team is comfortable with.
Same platform

Other docs you might need on this stack.

Browse all integrations