Resources · Zapier integration

Geckoboard Zapier integrationAutomate Geckoboard with Zapier.

The Geckoboard Zapier integration only writes: 0 triggers, 4 actions and 0 searches. Another app starts the work, and Geckoboard receives the record or the new widget value, so the office screen stays current without anyone copying figures.

See the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

Your dashboard is only as fresh as the last person who updated it

Connecting Geckoboard to Zapier means another app does the updating for you. A Zap (an automation built on Zapier) waits for an event elsewhere, then pushes a row of data or a single value into Geckoboard. The screen on the wall changes on its own, and nobody exports a spreadsheet at the end of the day.

Three results people usually build first:

A growing dataset. Each new deal, signup or order becomes a line through Add Record to Dataset, and the Geckoboard widgets reading that dataset redraw with it. It is the action Zapier puts forward for this app, and the one worth starting with.

A headline number. [LEGACY] Update Custom Number Widget replaces the figure on one push widget: open tickets, revenue booked, people on site.

A status line or a gauge. [LEGACY] Update Custom Text Widget writes a short message on screen, and [LEGACY] Update Custom Gauge Widget moves a needle between a minimum and a maximum you set in the step.

Now the part the app page skips. Zapier cannot listen to Geckoboard at all: there is no trigger, so nothing that happens on a dashboard can start a Zap. It cannot read a dataset back or look a record up either, because the app has no search. And it does not create the dataset for you, which has to exist in Geckoboard before the first run.

If you are still weighing tools, the Geckoboard Make integration covers the same app on another platform, and Make vs Zapier sets the two side by side.

Vocabulary

Zapier words, in one minute

Seven words come back on every line of this page. Here they are in plain English.

Zap
The automation itself: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Geckoboard has none, so the trigger always comes from another tool.
Action
The step that does the work once the Zap has started. Here, every Geckoboard step is an action that writes to a dashboard.
Task
What Zapier bills: one action that completed successfully. Your plan's allowance is a count of those.
Polling vs instant
A polling trigger is checked on a timer for new items. An instant trigger is reported by the app the moment the event happens.
Filter
A step that lets the Zap carry on only when the incoming data meets your condition, and stops it otherwise.
Connection
Your Geckoboard account linked to Zapier once, then reused by every step that writes to it.
Cost

What it really costs

Geckoboard is not a premium app, so it runs on the free plan. The trigger never costs a task, and checking for new data is free however often it happens.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap sizeOne trigger and one action
  • Premium appNo

Each Geckoboard action that succeeds counts as one task; one that fails is not counted. A Zap pushing to a dataset and to a number widget uses two per run. The free plan gives 100 tasks a month but only two-step Zaps, so adding a filter or a second action calls for a paid plan. Size the allowance against how often the source app produces events. Also keep in mind that a few apps and a few actions take more than one task when they complete.

Connect

Connect Geckoboard to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. You need a Geckoboard account first, plus edit rights on any dashboard you did not create yourself.

  2. 02

    Pick Geckoboard

    Type Geckoboard in the search box of the dialog, select it, then click Add connection. Geckoboard then asks you to sign in, so keep the login of the right account at hand.

  3. 03

    Sign in and allow access

    Log in to Geckoboard and grant Zapier access to the account. The connection now shows in the list, and every Geckoboard step of every Zap can reuse it.

First Zap

Your first Zap: won deals on the sales screen

GoalEvery HubSpot deal that reaches the won stage becomes a record in a Geckoboard dataset, and the sales dashboard updates by itself.

  1. 01

    Create the dataset in Geckoboard

    Before Zapier, set up the dataset the records will land in. Zapier does not create it, and the action asks for its Dataset ID.

  2. 02

    Build: set the trigger

    Start a Zap, choose HubSpot and its New Deal event. Test it: Zapier brings back the three most recent deals, so you map from a real one.

  3. 03

    Add the filter

    Add a Filter step. Pick the stage field, a text rule, and the won value you spotted in the test result. Deals at any other stage stop here.

  4. 04

    Add Record to Dataset

    Add the Geckoboard action, select your connection, fill Dataset ID and Update type, then map each dataset column to a HubSpot value.

  5. 05

    Test, then publish

    Run the action once and check the new row in Geckoboard. When it looks right, click Publish. The filter makes this a multi-step Zap, so a paid plan is required.

Actions

The four Geckoboard actions

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

1

Add Record to Dataset

Action

In Zapier“Adds a record to a Dataset”

Appends one line to a Geckoboard dataset each time the Zap runs, and every widget built on that dataset picks it up.

When to use it
you want trends, totals or tables, not just today's single figure.
Watch out
the dataset has to be created in Geckoboard first, and both Dataset ID and Update type are required.
2

[LEGACY] Update Custom Gauge Widget

Action

In Zapier“Send new values to a Custom Gauge Widget”

Moves the needle of a gauge between a left-hand minimum and a right-hand maximum that you supply in the same step.

When to use it
progress toward a monthly target, where the floor and the goal rarely change.
Watch out
Current value, Minimum value, Maximum value and Widget key are all required on every run.
3

[LEGACY] Update Custom Number Widget

Action

In Zapier“Send new values to a Custom Number Widget”

Sends a fresh figure to one push widget, replacing what it showed before.

When to use it
a support lead wants the count of open tickets on the team TV.
Watch out
it needs the Widget key from the widget's configuration screen.
4

[LEGACY] Update Custom Text Widget

Action

In Zapier“Send new values to a Custom Text Widget”

Puts a short message on a push widget, written from values the earlier steps carried.

When to use it
showing the name of the last customer who signed, or a release status the whole floor should see.
Watch out
Message and Widget key are both mandatory, and Zapier tags the action as legacy.
When it breaks

When it breaks

Zapier attaches no help article to Geckoboard, and no rate limit specific to the app is documented.

So what goes wrong comes from how Zapier itself behaves. These are the cases worth knowing before the dashboard goes up on the wall.

  • Old data never shows up

    A Zap only reacts to what happens after you switch it on. Deals closed last quarter will not reach the dataset; loading that backlog is a separate job.

  • A bulk import gets held back

    When the source app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those items instead of pushing them all.

  • The same item does not count twice

    On a polling trigger, Zapier remembers what it has already seen, so one deal starts the Zap once. Only new items reach the dataset.

  • A failed push costs nothing

    If Geckoboard rejects the action, say because a Widget key is wrong, no task is billed. The figure on screen simply stays where it was.
Need help

Need help automating Geckoboard with Zapier?

A person reads every message.

FAQ

Geckoboard Zapier integration: FAQ

01Is the Geckoboard Zapier integration free?
Yes, Geckoboard is not a premium app, so it works on the free Zapier plan. That plan gives 100 tasks a month and unlimited Zaps, but each Zap is capped at two steps: one trigger and one action. A Zap that only adds a record to a dataset fits. One that filters the incoming data first, or updates two widgets at once, becomes multi-step and needs a paid plan. No price is quoted here, since Zapier changes its grid often.
02How many tasks does a Geckoboard Zap use?
One task per Geckoboard action that succeeds. The trigger in the other app costs nothing, and neither do the checks Zapier runs looking for new data. If a single run pushes a record to a dataset and also refreshes a number widget, that run counts two tasks. An action Geckoboard rejects is not counted at all. On the free plan the allowance is 100 tasks a month, which is worth sizing against how often the source app produces events.
03Does Geckoboard update in real time with Zapier?
It depends on the trigger, because Geckoboard has none of its own. The Zap starts in another app. If that trigger is instant, the app reports the event straight away and Geckoboard gets the value with no wait, whatever your plan. If it is a polling trigger, Zapier checks on a timer: every 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. A lightning bolt in the editor marks an instant trigger.
04What does it take to connect Geckoboard to Zapier?
A Geckoboard account, and edit access to any dashboard or dataset you did not create yourself. In Zapier you open the Apps page, click + Add connection, pick Geckoboard, then sign in and grant access in the tab that opens. Before building the steps, have two things ready from Geckoboard: the dataset you plan to fill, since its Dataset ID is required, and the Widget key of each push widget you intend to update.
05Where is the Geckoboard Widget key?
In the configuration screen of the push widget itself, inside Geckoboard. All three legacy actions require it: the number, text and gauge widget updates. Without the right key, Zapier cannot tell which widget should receive the value, and the action fails. A failed action does not cost a task, but the figure on screen will not move either. Keep one key per widget and check it when a Zap stops changing the display.
06What if the Geckoboard action needed is not in Zapier?
Then it is not available through this integration. Zapier offers four actions and nothing else: add a record to a dataset, and update a custom number, text or gauge widget. There is no trigger, so a change on a dashboard cannot start anything. There is no search, so a Zap cannot read a dataset back. Creating a dataset also happens in Geckoboard, by hand, before the Zap runs. Anything beyond those four writes is out of reach here.
07Zapier, Make or n8n for Geckoboard?
Judge on three criteria rather than on a ranking. First, the operations: on Zapier, Geckoboard is write-only, with four actions and no trigger or search, so check that the other platform covers the operation your workflow needs. Second, cost: Zapier bills one task per successful action and its free plan stops at two-step Zaps. Third, where your source data already lives, since the trigger always comes from another app and that app must be supported too.
Same platform

Other docs you might need on this stack.

Browse all integrations