Resources · Make integration

Geckoboard Make integrationAutomate Geckoboard with Make.

Tired of pasting numbers into Geckoboard by hand? The Geckoboard Make integration gives you 4 action modules that create datasets and push records into them. This guide is for ops and sales leads who own a dashboard, and it walks you from the API key to a live first scenario.

Try the Geckoboard integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Geckoboard Make integration do for your dashboards?

The Geckoboard Make integration lets Make write data into your Geckoboard datasets, the tables your widgets read from. You build a scenario (the automation itself, a chain of modules), and each module is one brick of it. Data from another app goes in, and your dashboard updates without anyone touching a spreadsheet.

A sales leaderboard that fills itself. When a deal is marked won in your CRM, Send One Record to Dataset adds a row to the dataset behind your leaderboard. Each item Make passes along is called a bundle: here, one deal.

A support queue view built from a batch. If your help desk hands Make a whole list of tickets, Send Multiple Records to Dataset pushes them together instead of one by one. Before either of these, Create Dataset makes sure the target table exists, and simply returns it when it already does.

A clean slate for a retired metric. Delete Dataset removes a dataset you no longer report on, so old tables stop cluttering the account.

Know the limits before you start. Geckoboard has no trigger in Make, so something else has to start the scenario. There is no search module either, so Make writes to Geckoboard but does not read your figures back, and there is no Make an API Call module to fill gaps. For a broader look at the tool, the Make review helps, and Make pricing explains how operations are counted. The same app often has an n8n node too; n8n vs Make lays out the differences.

Connect

How do you connect Geckoboard to Make?

  1. 01

    Copy your API key from Geckoboard

    In Geckoboard, click your initials in the top right corner, then pick Account from the menu. Scroll to the API Key section on the Account Details screen and copy the key shown there.

  2. 02

    Open the connection window in Make

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

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied, confirm, and Make is ready to write to your datasets.

First scenario

Build your first scenario with Geckoboard

GoalWhen a deal is won in your CRM, Make checks the Geckoboard dataset exists and adds the deal to it.

  1. 01

    Start a new scenario

    Go to the Scenarios page, create a new scenario and click the +. Pick the app that holds your deals as the first module, since Geckoboard has no trigger of its own.

  2. 02

    Add Create Dataset

    Click the + on the right of the first module, search Geckoboard and choose Create Dataset. Connect your account, then describe the dataset you want your leaderboard to read.

  3. 03

    Send the deal as a record

    Add Send One Record to Dataset after it. Map the deal values coming from your CRM module into the record, so each won deal becomes one new row in the dataset.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open each module to read the bundles it received, then check your Geckoboard widget to see the new row land.

  5. 05

    Schedule it and switch it on

    Set the schedule on the first module (every 15 minutes by default, and never shorter on the Free plan), then turn the scenario on. From now on, won deals reach the dashboard without you.

Modules

Geckoboard modules in Make

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

Geckoboard1

Create Dataset

Action

In Make“Creates a Dataset with a given schema, or returns it if it already exists.”

This module gives you a Geckoboard dataset built on the schema you describe, and if that dataset already exists it hands back the existing one instead of failing.

When to use it
put it at the start of any scenario that writes records, so the table your widget reads is always there before data arrives.
Watch out
the dataset follows the schema you describe here, so settle that schema before real records start flowing into your widgets.
Geckoboard2

Delete Dataset

Action

In Make“Deletes a Dataset”

Removing a dataset you no longer need is what this module does, which keeps your Geckoboard account free of tables from old reports and abandoned tests.

When to use it
a metric has been retired, or you built a test dataset while setting up your first scenario and want it gone.
Watch out
a delete cannot be undone from Make, so run it on a single dataset with Run once before letting it loose in a live scenario.
Geckoboard3

Send Multiple Records to Dataset

Action

In Make“Sends multiple records to an existing Dataset”

With this module you push a whole set of records into an existing dataset in one go, handy when the previous step already gives you a list rather than a single item.

When to use it
your help desk or spreadsheet returns many rows together and you want them on the dashboard as a batch.
Watch out
the dataset has to exist first, so place Create Dataset earlier in the scenario when you are not sure it is there.
Geckoboard4

Send One Record to Dataset

Action

In Make“Adds a single record to an existing Dataset”

Each run of this module adds exactly one record to a dataset that already exists, so every event in another app turns into one fresh row on your dashboard.

When to use it
a deal is won, an order is paid or a ticket is closed, and you want that single event to add its own row.
Watch out
each run of a module is an operation, the unit Make counts on your plan, so a busy source app spends operations event by event.
Need help

Need help automating Geckoboard with Make?

A person reads every message.

FAQ

Geckoboard and Make: common questions

01Is the Geckoboard Make integration free?
Yes, Geckoboard is a standard app, so its modules work on the Make Free plan. That plan allows 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 (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and allow unlimited active scenarios. You still need your own Geckoboard account.
02What do you need to connect Geckoboard to Make?
An active Geckoboard account and its API key. In Geckoboard, click your initials in the top right, open Account, scroll to the API Key section on the Account Details screen and copy the key. In Make, add a Geckoboard module, click Create a connection, give it a name if you like, and paste the key. That one connection then serves all 4 Geckoboard modules. Once it is saved, you pick it from a list in every new Geckoboard module instead of pasting the key again.
03Can a Geckoboard scenario in Make start on its own?
Not from Geckoboard itself, because the app has no trigger module in Make. You start the scenario another way. The usual route is a trigger from the app that produces the data, such as your CRM or help desk, placed before the Geckoboard modules. The other route is the schedule on the first module, which runs every 15 minutes by default on a new scenario. In both cases Geckoboard is the destination, not the starting point.
04What if a Geckoboard module you need is missing in Make?
It depends on what you need. The integration covers four actions on datasets: create, delete, send one record and send several. It has no search module and no Make an API Call module, so reading data back from Geckoboard is not possible here. If your need goes beyond writing to datasets, look at whether another app in your scenario can do that part, or ask our team to review the setup with you.
05Should you use Make or n8n for the Geckoboard integration?
It depends on the tool your team already runs. On Make, Geckoboard offers 4 no-code action modules, available from the Free plan, and a scenario is built by clicking modules together. The same app often has an n8n node as well, so check that it covers the dataset actions you need before choosing. If your other automations already live in one of the two tools, keeping Geckoboard there is usually the simpler call.
Same platform

Other docs you might need on this stack.

Browse all integrations