Resources · Make integration

SeekTable Make integrationAutomate SeekTable with Make.

Can Make send your SeekTable reports out without you opening the app? The SeekTable Make integration gives you 10 modules: 2 scheduled triggers, 6 actions and 2 searches. This guide is for analysts and ops leads, and it walks you from the connection to a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SeekTable Make integration do for you?

The SeekTable Make integration links your SeekTable account to Make so that new cubes and reports can start an automation, and so that reports can be exported, fetched or emailed without a manual click. In Make, that automation is called a scenario: a chain of modules, where each module is one brick, such as a trigger, an action or a search.

A report that reaches the right inbox. Watch Reports spots a report added in SeekTable, and Share a Report by Email sends it to the address you pick. A sales manager gets the new pipeline pivot without asking for it.

Fresh data pushed in from another tool. Upload a CSV File takes a CSV produced by another app in the scenario, for example an export from your CRM or your billing tool, and sends it to SeekTable so your cubes rely on current figures.

An inventory of your analytics. List Cubes and List Reports return everything your account holds, one item per cube or report, which you can write into a sheet to see what exists before a cleanup. Get a Report and Get a Cube then read the details of a single one by its ID.

What Make does not do here: both triggers are scheduled, so Make checks SeekTable on the scenario's schedule instead of hearing about changes instantly. For anything the listed modules miss, Make an API Call reaches the rest of the SeekTable API. If you are still weighing tools, read the n8n vs Make comparison, check Make pricing, or follow the Make training to build faster.

Connect

How do you connect SeekTable to Make?

  1. 01

    Copy your API key in SeekTable

    In SeekTable, open Manage Account, click Get API Key and copy the key shown in the dialog. You need an active SeekTable account for this; the key is what lets Make act on your cubes and reports.

  2. 02

    Add a SeekTable module in Make

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

  3. 03

    Paste the key and save

    Paste the API key you copied into the connection window and confirm. Make then lists your cubes and reports in the module fields, which is the quickest sign that the link works before you go further.

First scenario

Your first scenario: email every new SeekTable report

GoalWhen a report is added in SeekTable, Make shares it by email with the person who needs it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for SeekTable and pick Watch Reports as the first module, the one that starts everything.

  2. 02

    Link your account

    Click Create a connection and paste your SeekTable API key. Once saved, the module can read your reports, and every SeekTable module you add later reuses the same connection.

  3. 03

    Add the email step

    Click the + to the right of Watch Reports and add Share a Report by Email. Map the report coming from the trigger, then type the email address that should receive it.

  4. 04

    Test with Run once

    Click Run once, then add a report in SeekTable. Open the bubble above each module to read the bundles it received: a bundle is one item passing from one module to the next, here one report.

  5. 05

    Schedule and switch on

    Open the clock on Watch Reports: a new scenario checks every 15 minutes by default, and the Free plan cannot go lower. Pick your interval and switch the scenario on so it keeps working without you.

Triggers

What starts a SeekTable scenario?

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

SeekTable1Watch Cubes

Watch Cubes

Scheduled trigger

In Make“Triggers when a new cube has been added.”

Watch Cubes gives your scenario a starting point each time someone adds a new cube in SeekTable, and hands that cube to the next module as a bundle you can map.

How it fires
it is a scheduled trigger, so Make checks the app on the scenario's schedule. A new cube shows up at the next check, not the second it is created.
When to use it
a data lead wants to hear about every new data source a colleague sets up, or wants to log each new cube in a shared tracking sheet.
Watch out
every cube it hands on uses operations in each module after it, so test with Run once before you chain several steps.
SeekTable2Watch Reports

Watch Reports

Scheduled trigger

In Make“Triggers when a new report has been added.”

Watch Reports is the trigger to reach for when a freshly saved report should lead to something: an email, a message, a line in a log. Every new report arrives in Make as its own bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and picks up the reports added since the last check.
When to use it
a finance analyst saves a new margin report and the controller should receive it without anyone forwarding it by hand.
Watch out
a report reaches Make at the next check, so one that is needed urgently is faster to share by hand.
Modules

What can the SeekTable modules do?

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

SeekTable1

Generate a Report

Action

In Make“Allows you to export saved report 'as-is' (identical to the Export initiated from the web interface).”

Generate a Report exports a saved report exactly as it looks, the same result you would get from the Export button in the SeekTable web interface, so the file can travel to the next module.

When to use it
you want the exported report attached to a message or dropped into a shared folder by another app.
Watch out
it exports what the report already shows; change the report in SeekTable first if you need other columns.
SeekTable2

Get a Cube

Action

In Make“Retrieves a single cube by ID.”

Get a Cube fetches the details of one cube when you already know its ID, so later modules can read and reuse its information instead of guessing.

When to use it
right after Watch Cubes or List Cubes, when you need the full picture of a specific data source before logging it or alerting a teammate.
Watch out
it needs a valid cube ID; map it from an earlier module rather than typing it by hand.
SeekTable3

Get a Report

Action

In Make“Retrieves a single report by ID.”

Get a Report brings back a single report by its ID, handy when a scenario holds the ID but not the rest of the report's details.

When to use it
a row in a spreadsheet stores report IDs, and each one must be read before it is shared or exported.
Watch out
this module only reads; to send the report somewhere, chain Generate a Report or Share a Report by Email after it.
SeekTable4

Make an API Call

Action

In Make“Performs an arbitary authorized API call.”

Make an API Call lets you call any endpoint of the SeekTable API from your scenario, using the same connection as the other modules, so nothing needs a second login.

When to use it
the action you need is not among the listed modules, and the SeekTable API documentation shows an endpoint that does it.
Watch out
this is the most technical module of the list; you write the request yourself, so keep the API documentation open next to Make.
SeekTable5

Share a Report by Email

Action

In Make“Shares a selected report to a specified email.”

Share a Report by Email sends a report you select to the email address you specify, which turns a report into something a manager actually receives.

When to use it
a new report was just detected by Watch Reports, or a client asked for their numbers and the address sits in your CRM.
Watch out
the address can come from a previous module; check it during Run once so the report goes to the right person.
SeekTable6

Upload a CSV File

Action

In Make“Uploads a CSV file.”

Upload a CSV File sends a CSV into SeekTable from your scenario, so data exported by another tool lands in your analytics without a manual upload.

When to use it
your shop, CRM or accounting app produces a CSV export and SeekTable should work from that data.
Watch out
on the Free plan, Make handles files up to 5 MB, so check the size of a large export before you run the scenario.
SeekTable7

List Cubes

Search

In Make“Lists all cubes.”

List Cubes returns every cube in your SeekTable account, one bundle per cube, which gives you a full inventory to sort or archive elsewhere.

When to use it
before a cleanup, to write each cube into a sheet and spot the data sources nobody uses anymore.
Watch out
as a search, it can return zero, one or many cubes, and each one flowing on uses operations in the modules after it.
SeekTable8

List Reports

Search

In Make“Lists all reports.”

List Reports gives back all your saved reports as separate bundles, so a scenario can act on each of them in turn.

When to use it
you want to email a batch of reports after a board meeting, or build a catalog of reports for a new team member.
Watch out
every report flows on as its own bundle, so an email module placed after it sends one message per report; test with Run once first.
Need help

Need help automating SeekTable with Make?

A person reads every message.

FAQ

SeekTable and Make: common questions

01Is the SeekTable Make integration free?
Yes, SeekTable is a standard app in Make, 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 (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and lift the active scenario cap. You still need your own active SeekTable account, whose subscription is handled on the SeekTable side.
02What do you need to connect SeekTable to Make?
You need an active SeekTable account and its API key. In SeekTable, go to Manage Account, click Get API Key and copy the value from the dialog. In Make, add a SeekTable module, click Create a connection, give it a name if you like, and paste the key. The connection is then reused by every SeekTable module in your scenarios, so you do this step only once per account. If you manage several SeekTable accounts, create one connection per account and name each one clearly.
03Do SeekTable triggers in Make fire in real time?
No. Watch Cubes and Watch Reports are both scheduled triggers: Make checks SeekTable on the scenario's schedule, every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans can go down to 1 minute. There is no instant trigger for SeekTable in Make, so a new cube or report is picked up at the next check rather than the moment it appears. For most reporting needs, that delay is fine; pick a shorter interval only if people are waiting on the result.
04What if a SeekTable module is missing in Make?
It depends on what you need. The SeekTable app includes Make an API Call, which reaches any endpoint of the SeekTable API with the connection you already set up. If the SeekTable API offers the action, you can build it with that module. Keep in mind the plan limits too: on the Free plan, a run stops after 5 minutes and files are capped at 5 MB, which matters when you upload large CSV exports.
05Should you use Make or n8n for SeekTable?
It depends on your criteria. Make gives you 10 ready SeekTable modules, a visual editor and a connection built around your API key. n8n often offers a node for the same app, so check whether one exists for SeekTable and which operations it covers before you choose. Compare on the modules you actually need, on how your team likes to build, and on the plans each tool offers, rather than on reputation.