Resources · Make integration

Net0 Make integrationAutomate Net0 with Make.

Tired of typing site electricity records into Net0 by hand? The Net0 Make integration gives you 2 action modules, one for site electricity and one open door to the Net0 API. This page shows how to connect your account and build a first scenario that fills Net0 for you.

Try the Net0 integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Net0 Make integration do for you?

The Net0 Make integration links your Net0 account to Make so that data coming from other tools lands in Net0 without copy and paste. You build a scenario, the automation itself, from modules, the bricks of that chain. Net0 brings two of them, both actions: nothing in Net0 starts a scenario on its own.

Site electricity pushed from a spreadsheet. An energy or facilities lead keeps meter figures in a shared sheet. A module from the spreadsheet app picks up each new row, and Create SiteElectricity writes it into Net0 as a new record. Each row travels as one bundle, the item passed from one module to the next.

Figures collected through a form. Site managers fill in a form after reading the meter. The form app starts the scenario and Net0 receives the entry, so nobody retypes it later.

Anything the listed modules skip. Net0 exposes more than site electricity. Make an API Call reaches any endpoint of the Net0 API with the same connection, which covers the gap without leaving Make.

What Make does not do here: react to a change inside Net0, since the app has no trigger. The Net0 documentation on Make also warns that its content is AI-generated and may contain mistakes, so check the details that matter with Net0. If you are weighing tools, read n8n vs Make; to budget your runs, see Make pricing; and to learn the editor properly, a Make training is the next step.

Connect

How do you connect Net0 to Make?

  1. 01

    Copy your Net0 API key

    You need an active Net0 account first. In the Net0 dashboard, open Settings, then the API section, and copy the API key shown on screen. Keep it handy, Make asks for it in a moment.

  2. 02

    Add a Net0 module and create the connection

    In your scenario, add a Net0 module and click Create a connection. A connection is your Net0 account linked to Make once, then reused by every Net0 module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and save

    Paste the API key you copied from Net0, or follow the instructions Make shows on screen, and save. The connection now appears in the module, ready for both Create SiteElectricity and Make an API Call.

First scenario

Your first scenario with Net0 and Make

GoalWhen a new electricity reading shows up in another app, Make records it in Net0 with Create SiteElectricity.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since Net0 has no trigger, this first bubble belongs to the app that holds your readings.

  2. 02

    Pick the starting module

    Search that app by name, choose the module that brings in new items, and create its connection. Fill its fields: once connected, Make lists the sheets or objects it can read.

  3. 03

    Add Create SiteElectricity

    Click the + on the right of the first module, search Net0 and pick Create SiteElectricity. Select your Net0 connection, then map the values from the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Open the Net0 bubble to confirm the record went through before going further.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What the Net0 modules do

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

Net01

Create SiteElectricity

ActionIn the docs only

Going by its name, this action adds a new site electricity record to Net0 from the data your scenario carries,. One bundle in, one record created.

When to use it
a facilities team logs meter figures in a sheet or a form and wants each new entry in Net0 as soon as the scenario runs.
Watch out
the doc lists no fields, so read them in the module. Run twice on one row, a scenario makes two records; filter or mark rows already sent.
Net02

Make an API Call

ActionIn the docs only

Here you get access to any endpoint of the Net0 API from inside the scenario, using the connection you already set up. It fills the gaps left by the single dedicated module, without a second login.

When to use it
the thing you need to read or send in Net0 is not site electricity, and no listed module covers it.
Watch out
you describe the request yourself, so keep the Net0 API documentation open and test with Run once before activating.
Need help

Need help automating Net0 with Make?

A person reads every message.

FAQ

Net0 Make integration: frequent questions

01Is the Net0 Make integration free?
Yes, on the Make side. Net0 is a standard app, available from the Free plan. 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 bring the interval down to 1 minute and lift the cap on active scenarios. Your Net0 account is a separate matter: the documentation asks for an active account, and its cost depends on Net0, not on Make.
02What do you need to connect Net0 to Make?
An active Net0 account and its API key. You find the key in the Net0 dashboard under Settings, then the API section, and you copy it from the screen. In Make, add a Net0 module, click Create a connection, give it a name if you like, and paste the key. That single connection then serves both Net0 modules, Create SiteElectricity and Make an API Call, so you do this step only once.
03Does the Net0 Make integration react in real time?
No, because Net0 has no trigger module on Make. A scenario with Net0 always starts somewhere else: on the schedule you set on the first module, every 15 minutes by default, or on a trigger from another app. If that other app offers an instant trigger, the one it calls through a webhook as soon as something happens, your scenario starts right away and Create SiteElectricity follows in the same run.
04What if a Net0 Make module is missing?
Use Make an API Call. With the same connection, it can reach any endpoint of the Net0 API, which covers what Create SiteElectricity does not. You write the request yourself, so check the Net0 API documentation for the exact endpoint. Keep in mind that the Make documentation for Net0 says its content is AI-generated and may contain mistakes; when a detail matters, confirm it with Net0 directly before you rely on it.
05Should you use Make or n8n for Net0?
It depends on what you already run. On Make, Net0 offers 2 modules: Create SiteElectricity for site electricity records and Make an API Call for everything else, with one connection and access from the Free plan. The same app often has an n8n node too, so check that side before choosing. Pick the tool your team already builds in, and compare how each one handles the Net0 data you need, rather than switching platforms for one app.
Same platform

Other docs you might need on this stack.

Browse all integrations