Resources · Make integration

Skai Make integrationAutomate Skai with Make.

Tired of exporting the same Skai report by hand? The Skai Make integration gives you 4 action modules that run reports and download their results. This guide is for marketing and ops teams, and it walks you from the connection to a first working scenario.

Try the Skai integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Skai Make integration do for you?

The Skai Make integration links your Skai account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that does a single job. With Skai, those bricks run reports and fetch their files, so the numbers you need reach the rest of your tools without a manual export.

A report that runs itself. If your team already built a report in the Skai interface, Run an Existing Report launches it by its ID. Put Make's schedule in front and the run starts on its own, then Download a Report File collects the results so another module can send them onward.

A custom pull of analysis data. Need a dataset that no saved report covers? Configure and Run a Report fetches data from the Skai analysis grids, so a scenario can build the report and run it in one step.

Anything else the API allows. Make an API Call reaches any endpoint of the Skai API with the same connection. It is the way out when the three report modules stop short.

Know the edges before you start. Skai has no trigger module in Make, so a scenario starts from Make's own schedule or from another app. The Skai documentation page on Make also warns that it was generated with AI, so check anything important against Skai. For the bigger picture, read our Make review, or compare both tools in n8n vs Make. Teams that prefer help can talk to our Make agency.

Connect

How do you connect your Skai account to Make?

  1. 01

    Open the connection window

    Log in to Make, add any Skai module to your scenario and click Create a connection. A connection is your Skai account linked to Make once; every Skai module of the scenario reuses it afterwards.

  2. 02

    Name it so you can find it

    The Connection name field is optional, yet worth filling. A clear name such as the client or the Skai server helps a lot when several people or several accounts share the same Make organization.

  3. 03

    Paste your Skai credentials

    Enter the credentials copied from Skai: the Client ID, the Refresh Token and the Server ID. The first two appear on the Skai login page once you generate a refresh token; the Server ID sits under Administration > About Skai > Server ID.

First scenario

Your first scenario: run a Skai report and grab the results

GoalWhen Make's schedule fires, Skai runs a saved report and Make downloads the results file.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Search for Skai and pick Run an Existing Report as the first module.

  2. 02

    Link your account and choose the report

    Click Create a connection and paste your Skai credentials. Then enter the ID of a report that already exists in the Skai interface.

  3. 03

    Add the download

    Click the + on the right of the first module and add Download a Report File. It finds a run by its ID: after a first Run once, look at what the previous module returned and map the run identifier from there, rather than typing it.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received; a bundle is one item passing between modules, here the report run and then its file.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, and change it to fit how often your team needs fresh numbers. Then switch the scenario on.

Modules

What the Skai modules do

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

Skai1

Configure and Run a Report

Action

In Make“Fetch any dataset available in the Skai analysis grids.”

Builds a report on the spot and runs it, pulling whatever dataset the Skai analysis grids offer. You get fresh data without first saving a report inside Skai.

When to use it
pick it over Run an Existing Report when the view you need does not exist yet, or when the scenario itself should decide what to fetch.
Watch out
each run counts as an operation, one execution of a module that Make bills against your plan.
Skai2

Download a Report File

Action

In Make“Downloads the results of a report run, by its ID.”

Hands you the results of a report run as a file, found by its run ID, ready to be emailed, stored or parsed by the next module.

When to use it
right after one of the two report modules, once a run has produced something worth sending to a drive or a spreadsheet.
Watch out
it needs the ID of a run, so map it from the module that started the run rather than typing it by hand.
Skai3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the whole Skai API to your scenario: you call any endpoint you want, signed with the connection you already set up, with no second login to manage.

When to use it
when neither report module covers your need and the Skai API documentation shows an endpoint that does.
Watch out
you write the request yourself, so keep the Skai API documentation open while you build it.
Skai4

Run an Existing Report

Action

In Make“Trigger a run of an existing report, previously created in the Skai interface, by report ID.”

Starts a fresh run of a report your team already designed in the Skai interface, using its report ID, so the saved setup stays the single reference.

When to use it
the report exists and people trust it; the scenario only has to launch it at the right moment and pass the run along.
Watch out
the report must be created in Skai first, since this module runs it and does not build it.
Need help

Need help automating Skai with Make?

A person reads every message.

FAQ

Skai and Make: common questions

01Is the Skai Make integration free?
Yes, on the Make side. Skai is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and allow unlimited active scenarios. You still need your own active Skai account, which Skai sells separately.
02What do you need to connect Skai to Make?
An active Skai account with valid API credentials. From the Skai login page you generate a refresh token, then copy the Client ID and the Refresh Token shown on screen. The Server ID lives under Administration, About Skai. If Skai asks for a callback URI, use the Make address given in its documentation. Paste the three values in the Create a connection window of any Skai module and the connection is shared by all of them.
03Can a Skai scenario start in real time?
No, Skai offers no trigger module in Make, scheduled or instant. The simplest start is Make's own schedule on the first module, every 15 minutes by default, which you can change to suit your reporting needs. Another option is to open the scenario with a trigger from a different app, for instance a form submission or a new row in a sheet, and let the Skai report modules follow it.
04What if a Skai module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Skai API with the connection you already created, so you are not limited to the three report modules. You write the request yourself, which asks for a look at the Skai API documentation. Keep in mind that the Make documentation for Skai says it was generated with AI and may contain mistakes, so confirm key details with Skai before you rely on them.
05Should you use Make or n8n for Skai?
It depends on the tool your team already works in. Make gives you 4 Skai modules, including the generic Make an API Call, and a visual editor where you test each run with Run once. The same app often has an n8n node too, so check what it covers before choosing. A fair criterion is where your other automations already run, since the team then learns a single editor and keeps every connection in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations