Resources · Make integration

Homerunner Make integrationAutomate Homerunner with Make.

What if every paid order turned into a Homerunner shipment on its own? The Homerunner Make integration gives you 28 action modules for shipments, labels, printers and warehouse orders. This page shows you how to connect your account and build a first scenario.

Try the Homerunner integration on MakeSee the 28 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Homerunner Make integration do for you?

The Homerunner Make integration links your Homerunner account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that does one job in one app. Homerunner brings 28 of those bricks, all actions, covering shipments, labels, printers, reports and warehouse orders.

Labels that print themselves. An order confirmed in your shop app starts the scenario, Create a Shipment books the parcel, and Send a Label To a Printer puts the label on the packing desk. Nobody retypes an address.

Cleaner addresses before booking. Validate a Address and Search city by zipcode sit in front of the shipment, so a typo in a web form is caught at the order stage rather than at the door.

Warehouse orders kept in sync. Create an Order sends an order to the warehouse side of Homerunner, and Get Updated Orders, run on a schedule, reports the changes back to a spreadsheet the team already reads.

Two limits to know first. Homerunner has no trigger in Make, so a scenario starts from another app or from a schedule. And Make's own documentation for this app is limited: it lists the modules but explains little about them, so testing each step with Run once matters more here than usual. If you also look at n8n, the n8n vs Make comparison lays out the criteria. To get comfortable with the editor itself, the Make training is a good start, and the Make pricing page explains how operations are counted.

Connect

How do you connect your Homerunner account to Make?

  1. 01

    Add a Homerunner module

    In a scenario, click the + and search for Homerunner. Pick any module, for instance V3 - Get Shipping Products, then click Create a connection. A connection is your Homerunner account linked to Make once, reused by every Homerunner module afterward.

  2. 02

    Name it and authorize Make

    Give the connection a name if you run more than one Homerunner account, which keeps them apart later. Then either sign in on the Homerunner page Make opens, or paste the key Homerunner gives you, depending on what the window asks for.

  3. 03

    Save and check the list

    Click Save. Back in the module, the connection now appears in the list. A quick way to confirm it works: click Run once on a read-only module like Get All Warehouses and look at what comes back.

First scenario

Your first scenario: from shop order to printed label

GoalWhen an order is confirmed in your shop app, Make creates the Homerunner shipment and sends its label to your printer.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since Homerunner has no trigger, this first module comes from your shop app, the one that knows when an order is confirmed.

  2. 02

    Add Create a Shipment

    Click the + on the right of the shop module, search for Homerunner and pick V3 - Create a Shipment. Choose your connection, then map the customer name and address from the order into the fields Make shows.

  3. 03

    Send the label to a printer

    Add PRINTERSERVICE - Send a Label To a Printer after the shipment. Pick the printer from the list Make can read, then map what the shipment module returned so the right label goes out.

  4. 04

    Test with Run once

    Click Run once with a test order. Open each module's bubble to read the bundle it received, that is the data that passed through. Expect a real label on the printer, so warn the packing desk.

  5. 05

    Set the schedule and switch it on

    If your shop module is a scheduled trigger (clock badge), open its clock: a new scenario checks every 15 minutes by default; on paid plans you can go down to 1 minute. If it is instant (lightning badge), it fires as soon as the order arrives. Switch the scenario on.

Modules

What each Homerunner module does

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

Homerunner1

Make an API Call

ActionIn the docs only

This universal module reaches any Homerunner endpoint the other modules leave out, using the connection you already set up, so you are never stuck on a missing feature.

When to use it
a step your shipping flow needs has no dedicated module in the list below.
Watch out
Make's documentation for Homerunner is limited, so the details of each endpoint have to come from Homerunner, not from Make.
Homerunner2

PRINTERSERVICE - Get All Printers

ActionIn the docs only

Get All Printers gives you the printers Homerunner's print service knows about, so you can pick the right one by name instead of guessing an identifier.

When to use it
while building a label flow, to see which printer the packing desk actually uses.
Watch out
if several printers come back, keep only the one you need before the next module, or every module after it runs once per printer.
Homerunner3

PRINTERSERVICE - Send a Label To a Printer

ActionIn the docs only

Here is how a label ends up on paper without anyone opening Homerunner: the module sends it straight to the printer you choose.

When to use it
right after a shipment is created, so the parcel is ready to pack when someone reaches the desk.
Watch out
a test with Run once can send a real label to the printer, and each label sent counts as one operation on your plan.
Homerunner4

V3 - Cancel a Label

ActionIn the docs only

Cancel a Label withdraws a single label you no longer want, for example after a customer corrects the delivery address Whether the rest of the shipment is affected is not documented.

When to use it
a parcel will not leave with that label and your Homerunner records should say so.
Watch out
Make's documentation does not say whether a canceled label can be restored, so check the label you target in the Run once output first.
Homerunner5

V3 - Cancel a Shipment

ActionIn the docs only

When the order itself falls through, Cancel a Shipment stops the whole shipment rather than one label, which saves you a trip into Homerunner.

When to use it
an order is refunded or canceled in your shop and the parcel must not go out.
Watch out
map the shipment from the module that created or found it earlier in the scenario; typing it by hand is how the wrong parcel gets canceled.
Homerunner6

V3 - Create a Consignment

ActionIn the docs only

Create a Consignment registers a consignment in Homerunner from the data you map, without a manual entry.

When to use it
your Homerunner setup handles parcels as consignments and Make should create them from your order data.
Watch out
Make's documentation does not explain how a consignment differs from a shipment in this app, so confirm that in Homerunner before choosing between this module and Create a Shipment.
Homerunner7

V3 - Create a Report

ActionIn the docs only

A Homerunner report can be requested straight from a scenario with this module, so nobody has to export it by hand.

When to use it
the end of a sales campaign or a stock count calls for a shipping summary.
Watch out
the report may not be ready in the same instant; pair it with Get a Report Status, then Get a Report, instead of trying to read it in one step.
Homerunner8

V3 - Create a Shipment

ActionIn the docs only

This is the module that turns an order into a parcel Homerunner can ship: it builds the shipment from the data you map from earlier modules.

When to use it
a new order is confirmed in your shop app and should become a shipment without copy and paste.
Watch out
place Validate a Address or Validate a Shipment in front of it if you want to catch a bad address before the shipment exists.
Homerunner9

V3 - Find a Single Servicepoint

ActionIn the docs only

Find a Single Servicepoint fetches one pickup point, the one your customer already chose, so its details can travel into the shipment.

When to use it
your checkout stores the chosen servicepoint and the scenario needs the full record for that point.
Watch out
to offer several options instead of confirming one, switch to List Servicepoints; this module is built for a single point you can already identify.
Homerunner10

V3 - Get Labels

ActionIn the docs only

Get Labels brings existing labels back into the scenario so you can store them, attach them to an email or pass them on to a printer.

When to use it
a label was created earlier and someone needs it again, say for a reprint after a paper jam.
Watch out
several labels can come back at once, and every module after this one then runs for each of them, which adds operations.
Homerunner11

V3 - Get Shipping Products

ActionIn the docs only

Get Shipping Products pulls the shipping products Homerunner exposes, the choices that sit behind every shipment you book.

When to use it
you are setting up Create a Shipment and want to see the available products before mapping one.
Watch out
Simple Products List sounds like a lighter version of the same thing; Make does not document the difference, so run both once and keep the one whose bundle suits you.
Homerunner12

V3 - Get a Report

ActionIn the docs only

Get a Report hands you the content of a report you asked for earlier, ready to pass to a spreadsheet or email module from another app.

When to use it
as the last step of a reporting flow, once Get a Report Status says the report is done.
Watch out
calling it before the report is finished may return nothing useful, so keep the status check in front of it.
Homerunner13

V3 - Get a Report Status

ActionIn the docs only

Before you fetch a report, Get a Report Status tells you where it stands, so the scenario does not read something half built.

When to use it
between Create a Report and Get a Report in the same scenario.
Watch out
Make's documentation gives no status values for Homerunner, so run the module once and read its bundle to learn what a finished report looks like before you rely on it.
Homerunner14

V3 - Get a Shipment

ActionIn the docs only

Get a Shipment reads one shipment you already know, so a later step can reuse its details without anyone looking it up.

When to use it
a helpdesk ticket mentions a shipment and the reply should carry its details.
Watch out
it works on exactly one shipment; if you only know part of what you are after, Search Shipments is the better pick.
Homerunner15

V3 - List Servicepoints

ActionIn the docs only

List Servicepoints returns a set of pickup points rather than one, handy when the customer still has to choose where to collect a parcel.

When to use it
you want to send collection options in a message or a form handled by another app.
Watch out
the points can arrive as separate bundles, and every module placed after this one runs for each, so keep only what you show.
Homerunner16

V3 - Search Shipments

ActionIn the docs only

Search Shipments looks through your Homerunner shipments and returns the ones that match, whether that is zero, one or many.

When to use it
you know part of what you are looking for but not the exact shipment, for instance before answering a complaint.
Watch out
plan for an empty result; when nothing matches, the modules after it have nothing to work on and the run simply stops there.
Homerunner17

V3 - Search city by zipcode

ActionIn the docs only

Search city by zipcode fills in the city from a postal code, which removes a common source of typos in addresses typed by customers.

When to use it
a form gives you only the zipcode and the shipment also needs the city.
Watch out
a zipcode may match more than one city, so read the Run once result and decide which answer the scenario keeps.
Homerunner18

V3 - Simple Products List

ActionIn the docs only

Simple Products List gives you a lighter list of products than Get Shipping Products, at least as its name suggests, which keeps the scenario easy to read.

When to use it
you only need product names to show or store, not every detail.
Watch out
Make's documentation does not describe the difference between the two modules, so compare their bundles with Run once before settling on one.
Homerunner19

V3 - Track a Consigment

ActionIn the docs only

Track a Consigment follows a consignment after it leaves, so its status can travel to wherever your team already works.

When to use it
you create consignments with Create a Consignment and want their progress in a spreadsheet or chat app.
Watch out
the module keeps Make's spelling, consigment with one missing n, so search for it exactly that way in the module list.
Homerunner20

V3 - Track a Shipment

ActionIn the docs only

Customers ask where their parcel is, and Track a Shipment gives the scenario Homerunner's answer so the reply is not a guess.

When to use it
a customer message in your helpdesk app mentions an order and the answer should include the tracking status.
Watch out
Homerunner has no trigger, so tracking only happens when something starts the scenario, either a schedule or another app's trigger.
Homerunner21

V3 - Validate a Address

ActionIn the docs only

Validate a Address checks a delivery address before anything is booked, so a typo gets caught at the order stage.

When to use it
addresses come from a free-text form and you want a check in front of Create a Shipment.
Watch out
decide in advance what the scenario should do when the check fails, for example stop and warn a colleague through a chat app.
Homerunner22

V3 - Validate a Shipment

ActionIn the docs only

Validate a Shipment tests a complete shipment before it becomes real, one step beyond checking the address alone.

When to use it
you map many values into Create a Shipment and want Homerunner to review them first.
Watch out
Make's documentation does not list the checks it runs, so read its answer with Run once on a few test orders to learn what it flags.
Homerunner23

WMS - Cancel an Order

ActionIn the docs only

Cancel an Order stops an order on the warehouse side of Homerunner (WMS stands for warehouse management system), so stock is not prepared for nothing.

When to use it
a customer cancels after the order already reached the warehouse.
Watch out
it is separate from V3 - Cancel a Shipment; when both a warehouse order and a shipment exist, decide which ones the scenario has to cancel.
Homerunner24

WMS - Create an Order

ActionIn the docs only

Create an Order hands a new order to the warehouse, so nobody has to type it a second time in Homerunner.

When to use it
your shop confirms a payment and the order should reach the warehouse without waiting for someone.
Watch out
if you run several warehouses, pick one first with Suggest a Warehouse or from the answer of Get All Warehouses, then map it into this module.
Homerunner25

WMS - Get All Orders

ActionIn the docs only

Get All Orders pulls the whole list of warehouse orders into the scenario, useful for a spreadsheet your team checks.

When to use it
you want the complete picture, not only what changed recently.
Watch out
a full list means many bundles, and each module after it runs once per order, so Get Updated Orders is likely the lighter choice for routine syncing.
Homerunner26

WMS - Get All Warehouses

ActionIn the docs only

Get All Warehouses lists the warehouses Homerunner knows, so you choose one by name rather than from memory.

When to use it
you are setting up Create an Order and need to see the warehouse options.
Watch out
this list rarely belongs in a live scenario; run it once while building, note the warehouse you need, then remove the module to save operations.
Homerunner27

WMS - Get Updated Orders

ActionIn the docs only

Get Updated Orders picks up warehouse orders that changed, which lets a scheduled scenario report those changes without pulling every order.

When to use it
your shop or your team should hear about order changes coming from the warehouse.
Watch out
Make's documentation does not say what the updates are measured against, so check with Run once which orders come back before you switch the scenario on.
Homerunner28

WMS - Suggest a Warehouse

ActionIn the docs only

Suggest a Warehouse lets Homerunner propose a warehouse for an order, instead of you fixing one in the scenario for good.

When to use it
you run several warehouses and the right one depends on the order.
Watch out
the documentation gives no rule behind the suggestion, so keep a person checking the answers until they match what your team would pick.
Need help

Need help automating Homerunner with Make?

A person reads every message.

FAQ

Homerunner and Make: common questions

01Is the Homerunner Make integration free?
Yes, Homerunner is a standard app in Make, so it works on the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Every module run on one bundle counts as one operation. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, allow unlimited active scenarios and 40 minutes of execution. Your Homerunner subscription itself is a separate matter.
02What do you need to connect Homerunner to Make?
A Homerunner account and access to its settings. Make's documentation lists no prerequisite for this app and gives no dedicated steps, so the generic connection flow applies: add any Homerunner module, click Create a connection, optionally name it, then either authorize Make on the Homerunner page or paste the key Homerunner provides, and click Save. The connection is then reused by all 28 modules. If the window asks for something you cannot find, look in your Homerunner account, since Make's own page on this app is limited.
03Can a Homerunner scenario react in real time?
No, not from Homerunner itself, because the app has no trigger module in Make, neither scheduled nor instant. You still have two ways to start a scenario. The first is to begin with a trigger from another app, such as your shop confirming an order, and then call Homerunner modules. The second is to set a schedule on the first module, every 15 minutes by default, and open with a module like Get Updated Orders. On paid plans the schedule can go down to 1 minute.
04What if a Homerunner module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Homerunner API through the same connection, so a feature without its own module is still within reach. The catch is documentation: Make says openly that its Homerunner guide is incomplete for lack of public information, so the endpoint details have to come from Homerunner. Test every call with Run once and read the bundle before the scenario goes live. If that is still not enough, the team can look at the flow with you.
05Should you use Make or n8n for Homerunner?
It depends on how you like to work. On Make, Homerunner comes with 28 ready modules plus Make an API Call, a visual editor and plans that count operations. Many apps also have an n8n node, so check whether one exists for Homerunner before comparing, and look at what each tool offers for the exact steps of your shipping flow. The honest test is to build the same small scenario in both and keep the one your team maintains with less effort.
Same platform

Other docs you might need on this stack.

Browse all integrations