Resources · Make integration

Keboola Make integrationAutomate Keboola with Make.

What can the Keboola Make integration do for your data team? It gives Make 10 action modules, from loading rows into a table to starting an orchestration. Here you connect your account with a Storage API token, then build a first scenario step by step.

Try the Keboola integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Keboola Make integration let you automate?

The Keboola Make integration links your Keboola project to Make, so a scenario (the automation you build in Make, a chain of modules) can push data into Keboola tables, read them back and launch jobs or orchestrations. Every one of its 10 modules is an action: something else has to start the scenario.

Feed a table from the tools your team already uses. A module (one brick of a scenario) from another app picks up new records, and Upload Data into a Table writes them into Keboola. Add Start an Orchestration right after, and the pipeline that depends on that table runs as soon as the data lands.

Hand fresh results to the rest of the business. Preview Data reads a slice of an existing table, while Export a Table and Get File URLs from a Run ID give you something to pass to the next module, such as a file link for a report or a message.

Keep an eye on the work Keboola is doing. Run a Queue Job launches a job, and Get a Job or Get a Queue Job fetch its details so the scenario can react to what happened.

What Make does not do here: Keboola has no trigger, so Make never hears about a change on its own. The scenario runs on its schedule or starts from another app. The Make documentation for this app is also flagged as AI-generated, so test each module before relying on it. To weigh Make against other tools, read our Make review and the n8n vs Make comparison; if a scenario stalls, Make troubleshooting covers the usual causes.

Connect

How do you connect Keboola to Make?

  1. 01

    Create a token in Keboola

    In the Keboola dashboard, open Project Settings, go to the API Tokens page and click Create Token. Set the permissions the token needs, confirm, then copy the Storage API token that appears.

  2. 02

    Add a Keboola module in Make

    In your scenario, add any Keboola module and click Create a connection. A connection is your Keboola account linked to Make once, then reused by every Keboola module you add later.

  3. 03

    Paste the token and save

    Give the connection a clear label in Connection name if you like (it is optional), paste the token you copied, and follow the on-screen instructions. Make then lists the Keboola objects it can read.

First scenario

Your first scenario: load new data and start an orchestration

GoalWhen another app hands Make new records, Make uploads them into a Keboola table, then starts the orchestration that processes them.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Since Keboola has no trigger, pick the first module from the app where your records come from, such as a form or a spreadsheet.

  2. 02

    Add Upload Data into a Table

    Click the + on the right of that first module, search for Keboola and choose Upload Data into a Table. Click Create a connection and paste your Storage API token.

  3. 03

    Choose the table and map the data

    Once the connection exists, Make lists what it can read in your project, so you pick the table instead of typing it. Then map the values from the first module into the fields Make shows you.

  4. 04

    Chain Start an Orchestration

    Add Start an Orchestration with the +, reuse the same connection and select the orchestration that should run on the new data.

  5. 05

    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 passed along, here one record). Check them before going live.

  6. 06

    Schedule it and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest interval.

Modules

What can the Keboola modules do?

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

Keboola1

Export a Table

Action

In Make“Exports an existing table.”

Get a whole existing Keboola table out of storage and into your scenario, so the next module can send it, archive it or share it with someone outside the data team.

When to use it
a report or a partner needs the full table, not a sample, after a job has refreshed it.
Watch out
each execution counts as one operation (what Make counts on your plan), so run it when the table has actually changed.
Keboola2

Get a Job

Action

In Make“Retrieves an existing job.”

Pull the details of a job that already exists in Keboola, so your scenario knows what happened to it before deciding on the next step, like alerting someone or moving on.

When to use it
you have a job reference from an earlier module and want its status inside Make.
Watch out
it reads an existing job and starts nothing; to launch work, reach for Run a Queue Job or Start an Orchestration.
Keboola3

Get a Queue Job

Action

In Make“Retrieves an existing queue job.”

Read back a queue job that is already in Keboola, which makes it the natural companion to Run a Queue Job when you want to follow the job you just launched.

When to use it
a scenario starts a queue job and then needs its details to notify a channel or log the result.
Watch out
Make lists it apart from Get a Job, so match the module to the kind of job you hold before mapping the reference.
Keboola4

Get File URLs from a Run ID

Action

In Make“Retrieves file URLs from a run ID.”

Turn a run ID into the file URLs that belong to that run, ready to hand to an email, a chat message or a storage app in the following module.

When to use it
a run has produced files and a colleague needs links to them rather than a login to Keboola.
Watch out
the module needs a run ID to work from, so map it from an earlier module; run the scenario once and read the bundle to see what comes back.
Keboola5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any endpoint of the Keboola API from your scenario, with the connection you already set up, when none of the nine ready-made modules covers what you need.

When to use it
a task exists in the Keboola API but has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Keboola API reference open, and check that your token permissions cover the endpoint you call.
Keboola6

Preview Data

Action

In Make“Previews data in an existing table.”

See a preview of the data sitting in an existing table, handy when a scenario only needs a look at the content rather than a full export of it.

When to use it
you want to check what a table holds before triggering a heavier step, or drop a quick excerpt into a message.
Watch out
a preview is not the full table; when the whole dataset matters, Export a Table or Unload Data Asynchronously is the better pick.
Keboola7

Run a Queue Job

Action

In Make“Runs a new queue job.”

Launch a new queue job in Keboola straight from Make, so work that someone used to start by hand now begins when the scenario reaches this module.

When to use it
an event in another tool, a new file or a validated form, should kick off processing in Keboola.
Watch out
every scenario run starts a fresh job, so test with Run once before switching the scenario on and letting the schedule repeat it.
Keboola8

Start an Orchestration

Action

In Make“Starts a new orchestration.”

Fire an orchestration, the sequence of steps your Keboola project already defines, from a Make scenario, without opening the Keboola dashboard to press start.

When to use it
right after Upload Data into a Table, so the pipeline that depends on that table runs on the new rows.
Watch out
the module starts a new orchestration each time it executes, so place it after any filter that should stop the run.
Keboola9

Unload Data Asynchronously

Action

In Make“Unloads data asynchronously.”

Ask Keboola to unload data asynchronously, which, going by its name, means Keboola handles the unload on its side instead of holding your scenario.

When to use it
you need data out of storage and prefer not to hold the scenario on one large export.
Watch out
the doc describes this module in a single line; test it with Run once and read the bundle it returns before you build the next steps on it.
Keboola10

Upload Data into a Table

Action

In Make“Uploads data into a table.”

Write data coming from other apps into a Keboola table, which is how records collected by forms, shops or spreadsheets end up where your data team works.

When to use it
new records land in a tool your team uses and belong in a Keboola table for processing.
Watch out
each bundle that reaches this module costs one operation, so group records upstream when a source sends many at once.
Need help

Need help automating Keboola with Make?

A person reads every message.

FAQ

Keboola and Make: common questions

01Is the Keboola Make integration free?
Yes, Keboola is a standard app, available from the Make Free plan. The Free plan keeps two scenarios active, runs them at most every 15 minutes, allows 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring a 1 minute interval, unlimited active scenarios and 40 minutes of execution, with usage counted in operations per month. Your Keboola subscription is separate and runs through Keboola itself.
02What do you need to connect Keboola to Make?
Two things: an active Keboola account and a valid Storage API token. You create the token in the Keboola dashboard under Project Settings, then the API Tokens page and the Create Token button, where you also set its permissions. In Make, add any Keboola module, click Create a connection, optionally name it, and paste the token. The connection is then reused by every Keboola module in your scenarios, so this setup happens once.
03Does the Keboola Make integration react in real time?
No. Keboola has no trigger in Make, neither scheduled nor instant, so Make is never alerted when something changes in your project. You start the scenario another way: with the schedule on the first module, every 15 minutes by default and down to 1 minute on paid plans, or with a trigger from another app, such as a form or a store, that hands data to the Keboola modules placed after it.
04What if a Keboola module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Keboola API with the connection you already have, so a task without a dedicated module is still possible, as long as your token permissions allow it. You write the request yourself, which asks for a look at the Keboola API reference. Also note that the Make documentation for this app is marked as AI-generated and may contain mistakes, so verify important details with Keboola directly.
05Should you use Make or n8n for Keboola?
It depends on how you like to work. Make gives Keboola 10 ready-made action modules plus a visual editor where each step shows the bundles it received, which suits a team that wants to assemble a flow quickly and test it with Run once. Keboola may also have a node in n8n; compare the modules each tool offers for your exact task before choosing. The two tools are not ranked here, and the comparison page linked above lays out the differences.
Same platform

Other docs you might need on this stack.

Browse all integrations