Resources · Make integration

The Good API Make integrationAutomate The Good API with Make.

Could a sale or a signed deal plant trees for you, without anyone clicking a button? The Good API Make integration gives you 6 action modules, including Plant Trees and Rescue Plastic Bottles. This page shows how to connect your account and build a first scenario around them.

Try the The Good API integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does The Good API Make integration let you automate?

The Good API Make integration lets a Make scenario (the automation you build, a chain of steps) call The Good API for you. Each step is a module, one brick of the scenario. Here all 6 modules are actions: they act when the scenario reaches them, and something else has to start the scenario.

An impact gesture tied to each sale. Start the scenario from your shop or payment app, then add Plant Trees so every new order leads to a request to The Good API. Your customers do nothing, and nobody on the team has to remember it.

A cleanup commitment tied to your support work. When a ticket is closed in your helpdesk, Rescue Plastic Bottles can run in the same scenario. The name of the module says what it asks for; the rest depends on your The Good API account.

A report that fills itself. Get Total Trees Planted and Get Total Rescued Plastic Bottles bring your running totals back into Make, and Get Public Dashboard Link hands you a page to share. Drop those values into a spreadsheet row or a newsletter draft.

What Make does not give you here: triggers. The Good API cannot wake a scenario up on its own, so the start always comes from another app or from the schedule. Make also marks its documentation for this app as limited, so field details are thin. If you are still weighing the tool itself, the Make review covers it, and n8n vs Make puts it next to n8n. For a guided start, see Make training.

Connect

How do you connect The Good API to Make?

  1. 01

    Add a The Good API module

    In your scenario, click the +, search for The Good API and pick any of its modules. The module opens with an empty connection box: click Create a connection. A connection is your account linked to Make once, then reused by all 6 modules.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps when a client or a second account has its own. Then authorize Make on The Good API page that opens, or paste the key your The Good API account gives you, depending on what the window asks for.

  3. 03

    Save and check the module

    Click Save. Back in the module, the connection now shows its name and Make can fill the lists it knows how to read. If the box stays empty or shows an error, open the connection again and check the key or the authorization.

First scenario

Your first scenario with The Good API

GoalWhen a new order lands in your shop app, Make runs Plant Trees in The Good API, then fetches your updated count with Get Total Trees Planted.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. The first module comes from your shop or payment app, since The Good API has no trigger of its own.

  2. 02

    Add Plant Trees

    Click the + to the right of the first module, search for The Good API and choose Plant Trees. Click Create a connection if this is your first The Good API module.

  3. 03

    Fill in the fields

    Complete the fields the module shows. Where a value should come from the order, map it from the first module instead of typing it, so each run uses the data of that order.

  4. 04

    Read the new total

    Add Get Total Trees Planted after Plant Trees. Its output is a bundle (one item passed to the next module) that you can send on to a sheet or a message later.

  5. 05

    Test with Run once

    Click Run once and create a test order. Each module shows the bundles it received; open them to confirm what The Good API sent back before going live.

  6. 06

    Schedule and switch on

    On the first module, set the schedule, every 15 minutes by default for a new scenario, then switch the scenario on. Each module run is an operation, the unit Make counts on your plan.

Modules

What The Good API modules do in Make

The Good API gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

The Good API2

Get Total Rescued Plastic Bottles

ActionIn the docs only

Brings your bottle count back into Make as data, ready to write into a spreadsheet, a report or a message instead of copying it from a dashboard by hand.

When to use it
right after Rescue Plastic Bottles, when you want the updated total in the same run.
Watch out
it reads a figure and changes nothing; if the total looks off, check the Rescue Plastic Bottles step before blaming this one.
The Good API3

Get Total Trees Planted

ActionIn the docs only

As its name says, returns the number of trees your account has planted so far, so a scenario can quote it in a Slack post, a CRM field or a thank-you email to a customer.

When to use it
after Plant Trees, or alone in a scenario that only feeds a report.
Watch out
Make lists no fields for this module, so test it with Run once to see which value arrives and how it is labeled.
The Good API4

Make an API Call

ActionIn the docs only

Opens the whole The Good API to your scenario: any endpoint of its API can be called with the same connection you already created, even when no ready-made module covers it.

When to use it
when the five named modules stop short of what you need, for example an operation none of their names covers.
Watch out
you write the request yourself, so keep The Good API's own API reference open beside the editor.
The Good API5

Plant Trees

ActionIn the docs only

Going by its name, turns an event in your business into a tree-planting request sent to The Good API, the core gesture this app exists for, with no manual step between the sale and the request.

When to use it
after a trigger from another app, such as a paid invoice or a signed contract, so each one leads to a planting.
Watch out
no module in the list reverses it, so test on a dummy event before you switch the scenario on.
The Good API6

Rescue Plastic Bottles

ActionIn the docs only

Sends a bottle-rescue request to The Good API each time the scenario reaches it, which lets a closed ticket, a returned package or a new subscriber carry a visible cleanup gesture.

When to use it
when plastic, rather than trees, fits the story your brand tells.
Watch out
every run counts as an operation on your Make plan and as a real request on The Good API side, so make sure the trigger before it only reacts to the events that should count.
Need help

Need help automating The Good API with Make?

A person reads every message.

FAQ

The Good API and Make: common questions

01Is The Good API Make integration free?
Yes, on the Make side. The Good API is a standard app, so it works from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and lift the active scenario cap. Make counts usage in operations, one per module run, so each Plant Trees call uses one. What The Good API itself charges is a separate question this page does not cover.
02What do you need to connect The Good API to Make?
A The Good API account and a Make account. Make's documentation lists no specific prerequisite for this app. You add any The Good API module, click Create a connection, optionally name it, then either authorize Make on The Good API page or paste the key your account provides, and click Save. The connection is created once and shared by all 6 modules, so a second scenario reuses it without asking again. Keep in mind that Make marks this app's documentation as limited, so if a step looks different from this description, trust what the connection window shows.
03Can The Good API start a Make scenario in real time?
No. The Good API has no trigger module in Make, only 6 actions, so it never starts a scenario itself. You have two ways around that. Open the scenario with a trigger from another app, for example your shop, CRM or form tool, and place the The Good API modules after it. If that trigger is instant, meaning the other app calls Make by webhook, the whole chain runs as soon as the event happens. Otherwise, use the schedule on the first module: a new scenario runs every 15 minutes by default, with 1 minute as the floor on paid plans.
04What if a The Good API module you need is missing in Make?
Use Make an API Call. It sits in the same list as the other modules and reaches any endpoint of The Good API with the connection you already set up, so nothing new to authorize. You will need The Good API's own API reference to write the request, because Make's documentation for this app is marked limited and does not describe the endpoints. If the gap is on the trigger side, no module can fill it: start the scenario from another app or from the schedule instead.
05Should you use Make or n8n for The Good API?
It depends on where the rest of your automations already live. In Make, The Good API offers 6 action modules, Make an API Call included, and it is available from the Free plan, so you can test a first scenario at no cost on the Make side. Many apps also have an n8n node, but that is worth checking for The Good API before you plan anything there. Neither tool is ranked here. Pick the one your team already uses for the apps that will trigger the scenario, since that is where the start of the flow will sit.
Same platform

Other docs you might need on this stack.

Browse all integrations