Resources · Make integration

Beeminder Make integrationAutomate Beeminder with Make.

Tired of typing every datapoint by hand? The Beeminder Make integration gives you 6 modules: 1 trigger, 4 actions and 1 search. This guide is for anyone who tracks goals in Beeminder, and it walks you from the API token to a first working scenario.

Try the Beeminder integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Beeminder Make integration let you do?

The Beeminder Make integration links your Beeminder account to Make, a no-code tool where you chain apps together. A datapoint is one entry you log toward a goal, like a number of pages written. Other apps can then add, edit or remove those entries, and new or changed datapoints can kick off work somewhere else. You set it up once with an API token, and it keeps running without you.

Progress logged by the work itself. A writer who tracks drafted articles can start a scenario on the tool where drafts get marked done, then let Create a Datapoint add the entry to the right goal. No more catching up by hand in the Beeminder app.

A datapoint that tells someone. Watch Datapoints picks up new or edited datapoints at each scheduled check. From there, a coach can copy each one into a shared sheet or a message to an accountability partner, using whatever app comes next in the scenario.

Housekeeping on a goal. List Datapoints pulls the entries of a goal so you can review them, then Update a Datapoint or Delete a Datapoint fix the ones that went wrong, such as a duplicate sent by another tool.

What Make does not give you here: the Make documentation for Beeminder names no extra limit and no module beyond these six. For an API endpoint that none of them reaches, Make an API Call reuses the same connection. New to the editor? The Make training starts from zero.

Beeminder also has a node in n8n, covered on the Beeminder n8n integration page. If you are still choosing a platform, the n8n vs Make comparison lays out the differences.

Connect

How do you connect Beeminder to Make?

  1. 01

    Copy your Beeminder API token

    Sign in to Beeminder and open your account settings. Go to the Apps and API section and copy the API token shown on that page. Make will ask for it in a moment, so keep it at hand.

  2. 02

    Add a Beeminder module in Make

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

  3. 03

    Paste the token and save

    Give the connection a name in the Connection name field if you want to recognize it later (this part is optional). Paste the token you copied, or follow the instructions on screen, and save.

First scenario

Your first scenario: log progress from another app

GoalWhen a task is marked done in another app, Make adds a datapoint to your Beeminder goal.

  1. 01

    Create the scenario

    Open the Scenarios page in Make and create a new one. A scenario is the automation you build: a chain of modules, each one a brick that watches, searches or acts. Click the + to place the first one.

  2. 02

    Start on the app where work gets done

    Search the app you already use for tasks, pick its trigger and link your account with Create a connection. Each finished task will reach the next module as a bundle, one item passed along the chain.

  3. 03

    Add Create a Datapoint

    Click the + on the right of the first module, search Beeminder and choose Create a Datapoint. Pick your goal from the list Make offers once the connection exists, then map data from the task module.

  4. 04

    Test with Run once

    Mark a task done, then click Run once. Make runs the scenario a single time and shows the bundles each module received. Check your Beeminder goal: the new datapoint should be there.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go lower. Adjust it if your plan allows, then switch the scenario on.

Triggers

What can start a Beeminder scenario?

1 module starts a scenario when something happens in Beeminder. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Beeminder as soon as it happens.

Beeminder1Watch Datapoints

Watch Datapoints

Scheduled trigger

In Make“Triggers when a new datapoint is created or updated.”

This trigger picks up datapoints on your Beeminder goals as they appear or change, and hands each one to the rest of the scenario. It is the only Beeminder module that can open a scenario, so anything that should react to your own tracking starts here.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a datapoint waits for the next check before anything happens.
When to use it
you want each entry you log copied to a sheet, a journal or a message for someone who keeps you honest.
Watch out
an edited datapoint counts too, so a correction can send the same entry down the scenario a second time.
Modules

What can Make do in Beeminder?

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

Beeminder1

Create a Datapoint

Action

In Make“Adds a new datapoint to a user's goal.”

This action writes a new entry on one of your goals, exactly as if you had typed it in Beeminder. It is the module that turns activity in another tool into visible progress.

When to use it
a finished workout, a sent invoice or a merged pull request in another app should count toward a goal without you opening Beeminder.
Watch out
every run adds one more entry, so test with Run once before letting the schedule loose.
Beeminder2

Delete a Datapoint

Action

In Make“Deletes a specified datapoint.”

Removes one specific datapoint from a goal. Unlike an update, the entry is gone rather than corrected, which matters when the goal should reflect only real entries.

When to use it
another tool pushed a duplicate or a test entry, and you want the scenario to clean it up instead of fixing it by hand.
Watch out
point it at the exact datapoint, usually one returned by List Datapoints, and try it on a spare goal before a real one.
Beeminder3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends a request of your choice to the Beeminder API, signed with the connection you already set up. It is the fallback for anything the five named modules leave out, since any endpoint of the API is within reach.

When to use it
you need a Beeminder feature that has no dedicated module in Make, and you are comfortable reading the Beeminder API documentation.
Watch out
nothing here is prefilled for you, so start with the ready-made modules and only switch when they fall short.
Beeminder4

Update a Datapoint

Action

In Make“Updates the information of a specified datapoint.”

Changes the details of a datapoint that already exists, instead of adding a second one next to it. Your history stays tidy and the goal keeps a single entry for that moment.

When to use it
the source app corrects a figure after the fact, for example a revised word count, and Beeminder should show the corrected version.
Watch out
the module needs to know which datapoint to change, so pair it with List Datapoints or keep the reference from the run that created it.
Beeminder5

List Datapoints

Search

In Make“Returns a list of datapoint objects.”

A search module that returns the datapoints of a goal as a batch of bundles, one per entry. It is how a scenario reads your history before deciding what to do with it.

When to use it
you want to export the entries of a goal to a spreadsheet, or find the one that Update a Datapoint or Delete a Datapoint should act on.
Watch out
each returned bundle runs through the following modules, and every module execution is an operation counted on your Make plan.
Need help

Need help automating Beeminder with Make?

A person reads every message.

FAQ

Beeminder and Make: common questions

01Is the Beeminder Make integration free?
Yes, on the Make side. Beeminder is a standard app, so it works from the Free plan onward, along with 3,000+ other standard apps. The Free plan has limits: 2 active scenarios, at least 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 and Enterprise) bring the interval down to 1 minute and allow unlimited active scenarios. Usage is counted in operations, meaning one execution of one module. Your Beeminder subscription is a separate matter handled by Beeminder.
02What do you need to connect Beeminder to Make?
An active Beeminder account and its API token. You find the token in your Beeminder account settings, under the Apps and API section, and copy it from there. In Make, add any Beeminder module, click Create a connection, optionally name the connection, then paste the token. The connection is created once and every Beeminder module in your scenarios reuses it, so you do not repeat the step for each module. If you later add a module with an instant tag, Make would ask you to create a webhook first, but the Beeminder app currently has none.
03Is the Beeminder Watch Datapoints trigger instant or scheduled?
Scheduled. Watch Datapoints does not receive a push from Beeminder: Make checks the app each time the scenario runs on its schedule. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval possible, while paid plans can go down to 1 minute. In practice, a datapoint logged just after a check waits for the next one before the scenario reacts. If that delay is fine for a report or a notification, the trigger does the job well. The Beeminder app in Make has no instant trigger.
04What if a Beeminder module is missing in Make?
Use Make an API Call. It calls any endpoint of the Beeminder API with the connection you already have, so you do not need a second setup. The five dedicated modules cover datapoints: creating, updating, deleting, listing and watching them. Anything else Beeminder exposes through its API goes through that universal module. The Make documentation for Beeminder names no specific limit to work around; it does warn that its content is AI-generated from the Beeminder documentation, so check important details with Beeminder directly.
05Should you pick Make or n8n for Beeminder?
It depends on where the rest of your automations live. Beeminder is available in both tools, so neither choice locks you out. In Make, you get the six modules described on this page, with a visual editor, the Run once test and a single connection built from your API token. The simplest criterion is practical: build the Beeminder scenario in the platform where the apps that feed your goals are already connected. The n8n version has its own guide, and the comparison page linked above covers the differences between the two platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations