Resources · Make integration

Octopus Energy Make integrationAutomate Octopus Energy with Make.

Want your energy data to land where you actually read it? The Octopus Energy Make integration gives you 5 modules: 3 actions and 2 searches. This guide is for people who know their Octopus account and are new to Make. You will link your API key and build a first working scenario.

Try the Octopus Energy integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Octopus Energy Make integration do for you?

The Octopus Energy Make integration lets a Make scenario read data from your Octopus Energy account: products and their tariffs, tariff components, and the consumption recorded by your smart meter. A scenario is the automation you build in Make, a chain of modules where each module is one brick, like an action or a search. Nothing to code: you pick modules and fill in fields.

A consumption log you never have to export. Get Consumption returns your meter readings split into half-hour periods, in kWh for electricity. Add a spreadsheet module after it and every run appends fresh rows, ready for a chart or a review with your team.

A clear picture of the tariffs on offer. List Products returns the energy products Octopus publishes, then Get a Product opens one of them with all its tariffs for a given point in time. Useful when you manage several sites and want to compare offers without clicking through the website.

The detail behind a price. List Tariff Components breaks a tariff down for a given product, GSP and tariff code, so a finance lead can see what makes up the price.

Know the limits before you start. Octopus Energy has no trigger in Make, so a scenario starts on a schedule or on another app's event. Half-hourly consumption only exists for smart meters; an older meter gives back an empty result. Make an API Call covers the rest of the Octopus API with the same connection. The Make review helps you judge the tool as a whole, the Make pricing page explains how operations are counted, and if you also look at n8n, the n8n vs Make comparison sets the criteria side by side.

Connect

How do you connect your Octopus Energy account to Make?

  1. 01

    Copy your API key from Octopus

    Log in to your Octopus Energy account, open the dashboard and click the Developer tab. Your API key sits on that screen. Copy it; Make needs it once to create the connection, which is your Octopus account linked to Make.

  2. 02

    Add a module and create the connection

    In a Make scenario, add any Octopus Energy module and click Create a connection. The Connection name field is optional, but a clear name like the site or the account holder helps when you run several accounts.

  3. 03

    Paste the key and confirm

    Paste the API key into the credentials field, or follow the instructions Make shows on screen, then save. Every Octopus Energy module in your scenarios reuses this connection, so you only do it once per account.

First scenario

Build your first scenario with Octopus Energy

GoalEach time the scenario runs on its schedule, Make lists the Octopus Energy products and opens each one with its full tariff details.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Search for Octopus Energy and pick List Products as your first module.

  2. 02

    Link your account

    Click Create a connection and paste the API key from the Developer tab. Once linked, the module shows the fields it needs and you fill them in.

  3. 03

    Add Get a Product

    Click the + on the right of List Products and add Get a Product. Map the product returned by the first module into it, so each product in the list gets opened with its tariffs.

  4. 04

    Test with Run once

    Click Run once. Each bubble shows the bundles it received; a bundle is one item passing from one module to the next, here one product. Check that the tariffs look right.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default; set the rhythm you need, then switch the scenario on. Each module run counts as one operation on your plan.

Modules

What the Octopus Energy modules do

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

Octopus Energy1

Get a Product

Action

In Make“Retrieve the details of a product (including all its tariffs) for a particular point in time.”

You get one Octopus Energy product in full, with every tariff attached to it, as it stood at the point in time you ask for. One product in, one detailed bundle out.

When to use it
right after List Products, when you want the tariff detail of each product the search found.
Watch out
it answers for a point in time, so the tariffs you read describe that moment and may differ from another date.
Octopus Energy2

Get Consumption

Action

In Make“Return a list of consumption values for half-hour periods for a given meter-point and meter. Unit of measurement: Electricity meters: kWh SMETS1 Secure gas meters: kWh SMETS2 gas meters: m^3 Warning Half-hourly consumption data is only available for smart meters. Requests for consumption data for non-smart meters will return an empty response payload.”

This one hands you your meter's usage cut into half-hour periods, for a given meter point and meter. Electricity comes back in kWh, SMETS1 Secure gas meters in kWh and SMETS2 gas meters in m^3.

When to use it
to feed a spreadsheet or a dashboard with real consumption instead of exporting it by hand.
Watch out
half-hourly data exists only for smart meters. A non-smart meter gives an empty response, not an error, so the scenario looks fine while nothing arrives.
Octopus Energy3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any endpoint of the Octopus Energy API from your scenario, using the connection you already created. It is your way out when none of the four named modules does what you need.

When to use it
you found an endpoint in the Octopus documentation that the other modules do not cover.
Watch out
here you write the request yourself, so read the Octopus API documentation first to know what to ask for.
Octopus Energy4

List Products

Search

In Make“Return a list of energy products. By default, results will be public energy products but if the authenticated organisations will also see products available to their organisation. Authentication: public and authenticated.”

A list of Octopus energy products, each as its own bundle, so the next module can process them one by one. By default you see the public products; an authenticated organisation also sees the products reserved to it.

When to use it
as the first module of a scenario that compares offers, before Get a Product.
Watch out
a search can return many products, and every module after it runs once per product, which adds operations.
Octopus Energy5

List Tariff Components

Search

In Make“List the tariff components for a given product, GSP and tariff code”

See what a tariff is made of: the module returns the tariff components for the product, GSP and tariff code you give it. Handy to explain a price component by component.

When to use it
once you know the product and tariff code, for example from Get a Product, and want the breakdown behind the price.
Watch out
the module needs all three values, so gather the product, GSP and tariff code before you add it.
Need help

Need help automating Octopus Energy with Make?

A person reads every message.

FAQ

Octopus Energy and Make: common questions

01Is the Octopus Energy Make integration free?
Yes, Octopus Energy is a standard app in Make, so it works from the Free plan. The Free plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the minimum interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations per month, one per module run. Your Octopus Energy account itself is a separate matter.
02What do you need to connect Octopus Energy to Make?
An active Octopus Energy account and its API key. You find the key on your Octopus dashboard, under the Developer tab, and copy it. In Make, add any Octopus Energy module, click Create a connection, give it a name if you like, and paste the key. The connection is saved and reused by every Octopus Energy module, so the step happens once per account. If you manage several accounts, create one connection per account and name each one clearly to avoid mixing their data.
03Can an Octopus Energy scenario run in real time?
No, because Octopus Energy has no trigger in Make: nothing in the app calls Make when something happens. You start the scenario another way. The simplest is the schedule on the first module, every 15 minutes by default, with a minimum of 15 minutes on the Free plan and 1 minute on paid plans. The other option is to open the scenario with a trigger from another app, then add the Octopus Energy module you need right after it, for example Get Consumption.
04What if the Octopus Energy module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Octopus Energy API with the connection you already have, so you do not need a second setup. You write the request yourself, based on the Octopus API documentation. Also note that Make labels this app's documentation as AI-generated from the official Octopus Energy documentation and asks you to verify important information, so when a detail matters, check it against Octopus directly. For consumption, remember that only smart meters return half-hourly data.
05Should you use Make or n8n for Octopus Energy?
It depends on the tool you already use and how you like to build. In Make, Octopus Energy offers 5 modules, including Make an API Call for anything the other four do not cover, and it runs from the Free plan. The same app often has a node in n8n as well, so check what that node offers before you pick. Compare the modules you actually need, how the connection works and how each tool counts usage. The comparison page linked above lays out those criteria without taking sides.
Same platform

Other docs you might need on this stack.

Browse all integrations