Resources · Make integration

LionWheel Delivery Make integrationAutomate LionWheel Delivery with Make.

Tired of typing every new delivery into LionWheel by hand? The LionWheel Delivery Make integration gives you 4 action modules to create deliveries and read them back. This page shows how to link your account and build a first scenario step by step.

Try the LionWheel Delivery integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the LionWheel Delivery Make integration let you automate?

The LionWheel Delivery Make integration links your LionWheel account to Make, a visual tool where you build a scenario: an automation made of modules, each one a single brick that acts on one app. Here you get 4 action modules, so LionWheel receives or hands over delivery data while another app, or a schedule, starts the flow.

Deliveries created from incoming orders. When an order lands in your shop, form or spreadsheet, that app starts the scenario and the Create Delivery module opens the matching delivery in LionWheel. Nobody retypes the address, and each order produces one delivery.

A delivery list sent where your team works. Put Get Deliveries on a schedule and pass what it returns to a sheet, a chat or a report tool. By default Make runs a new scenario every 15 minutes, and you can change that clock.

One delivery looked up on demand. A support ticket or a form holds a delivery reference; Get Delivery reads that one record so the next module can reply with the details. For anything the three named modules do not cover, Make an API Call reaches the LionWheel API with the same connection.

Know the limits before you start. This app has no trigger, so LionWheel never starts a scenario on its own, and the Make documentation for it is marked as AI-generated, so check important details with LionWheel. The same app can also exist on n8n; the n8n vs Make comparison sets the two side by side, and our Make review covers the editor itself.

Connect

How do you connect LionWheel Delivery to Make?

  1. 01

    Get your API key

    The connection needs an active LionWheel Delivery account and an API key. According to the documentation, the key is issued once you complete the payment for the LionWheel extension, so sort that out inside LionWheel first.

  2. 02

    Add a module and create the connection

    In your scenario, add any LionWheel Delivery module and click Create a connection. A connection is your LionWheel account linked to Make once, then reused by all four modules. The Connection name field is optional.

  3. 03

    Paste the key and save

    Enter the credentials you copied from LionWheel Delivery, or follow the instructions shown on screen, then save. The module now lets you fill its fields, and every other LionWheel module offers this same connection.

First scenario

Your first scenario with LionWheel Delivery

GoalWhen a new order shows up in another app, Make creates the matching delivery in LionWheel Delivery.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Since LionWheel has no trigger, the first module belongs to the app where your orders arrive.

  2. 02

    Pick the order source

    Search that app by name, choose the module that watches new orders and link its account. Each order it finds becomes a bundle, one item passed on to the next module.

  3. 03

    Add Create Delivery

    Click the + on the right, search LionWheel Delivery and pick Create Delivery. Use the connection from the previous section, then map the order data into the fields the module shows.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Read the bundles each module received, then check in LionWheel that the delivery looks right.

  5. 05

    Schedule and switch on

    Set the clock on the first module (every 15 minutes by default) and switch the scenario on. Each module run on a bundle is one operation, the unit Make counts on your plan.

Modules

What the LionWheel Delivery modules do

LionWheel Delivery gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

LionWheel Delivery1

Create Delivery

ActionIn the docs only

Turns data from another app into a new delivery in LionWheel, which saves your dispatchers from retyping orders. This is the module most scenarios with this app end on.

When to use it
a customer confirms an order in your shop or a form, and the delivery should exist in LionWheel without anyone copying it over.
Watch out
the documentation gives no field list, so read what the module asks for in the editor and run one test before you switch the scenario on.
LionWheel Delivery2

Get Deliveries

ActionIn the docs only

Pulls several deliveries out of LionWheel so you can send them to a sheet, a report or a message. Its name points to a list, so expect more than one bundle when you run it.

When to use it
your team wants an overview of deliveries in the tool it already opens, rather than logging into LionWheel.
Watch out
every bundle that flows into the next module costs an operation there, so keep the modules after it lean.
LionWheel Delivery3

Get Delivery

ActionIn the docs only

Reads one specific delivery, handy when you already know which record you need and want its details in the rest of the scenario. Pick it over Get Deliveries whenever a single reference is at hand.

When to use it
a support ticket mentions a delivery and your reply module needs its current details.
Watch out
the module needs a way to identify the delivery, so map that value from an earlier module instead of typing it in.
LionWheel Delivery4

Make an API Call

ActionIn the docs only

Opens the whole LionWheel API to your scenario, using the connection you already created. It is the fallback when the three named modules do not do what you need.

When to use it
you need an action the listed modules skip, and the LionWheel API documentation describes the endpoint for it.
Watch out
you write the request yourself here, so keep the LionWheel API documentation open and test with Run once before going live.
Need help

Need help automating LionWheel Delivery with Make?

A person reads every message.

FAQ

Questions about LionWheel Delivery and Make

01Is the LionWheel Delivery Make integration free?
Yes, on the Make side. LionWheel Delivery 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 per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Your LionWheel subscription is a separate matter: the API key comes with the LionWheel extension payment, so check that with LionWheel.
02What is required to connect LionWheel Delivery to Make?
An active LionWheel Delivery account and its API key. The documentation says the key is issued once the payment for the LionWheel extension is complete. In Make, add any LionWheel Delivery module, click Create a connection, give it a name if you like, and paste the credentials copied from your LionWheel account. The same connection then serves all four modules, including Make an API Call, so the setup happens only once per account.
03Can LionWheel Delivery start a Make scenario in real time?
No. This app has no trigger module, so LionWheel never starts a scenario on its own. Two ways around it. Open the scenario with a trigger from another app, for example the shop or form where orders arrive, then add Create Delivery. Or put a LionWheel module such as Get Deliveries first and let Make run it on the scenario schedule, every 15 minutes by default, or at least 15 minutes apart on the Free plan.
04What if a LionWheel Delivery module is missing in Make?
Use Make an API Call. It calls any endpoint of the LionWheel API with the connection you already have, so an action that Create Delivery, Get Deliveries and Get Delivery do not cover is still within reach. You write the request yourself, so keep the LionWheel API documentation open. Keep in mind too that the Make documentation for this app is marked as AI-generated: when something behaves unexpectedly, confirm the detail with LionWheel directly.
05Make or n8n for LionWheel Delivery: which one fits?
It depends on your team rather than on the app. In Make, LionWheel Delivery offers 4 modules: create a delivery, read one, read several, and a free API call. Check whether n8n has a node for LionWheel before you compare, then weigh which editor your team already knows, where your other apps are connected, and whether the actions you need are covered. Neither tool is ranked above the other here; the choice comes down to those criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations