Resources · Make integration

STEL Order Make integrationAutomate STEL Order with Make.

Can STEL Order feed the rest of your tools without anyone copying data by hand? The STEL Order Make integration gives you 86 modules, 11 of them triggers. This guide is for teams that run jobs, quotes and invoices in STEL Order, and it walks you from the connection to a first live scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the STEL Order Make integration do?

The STEL Order Make integration links your STEL Order account to Make so that clients, quotes, orders, invoices and field work move on their own between STEL Order and your other apps. You build a scenario (the automation itself, a chain of modules) once, and Make runs it for you on the schedule you pick.

Turn a reported problem into a planned job. A service company logs an incident, Watch Incidents picks it up on the next check, and Create a Work Order opens the job so the technician sees it in STEL Order without a second entry.

Keep sales paperwork moving. When a sales order lands, Watch Sales Orders passes it on, and Create Sales Delivery Note prepares the delivery note that follows. The same logic works from estimates to orders with Create Sales Orders.

Send billing data where your accountant looks. Watch Ordinary Invoices and Watch Ordinary Invoice Receipts hand each new document to a spreadsheet or an accounting tool, and Get Tax Lines fetches the tax detail when you need it.

Know the limits before you start. Make's own documentation for STEL Order is thin: it lists the modules but describes none of them, so this page reads each module from its name. All 11 triggers are scheduled, which means Make checks STEL Order at an interval rather than being called the moment something changes. When a listed module falls short, Make an API Call reaches the STEL Order API with the same connection.

If you are still weighing platforms, the n8n vs Make comparison lays out the differences, and our Make training covers scenario building step by step. For hands-on help, see the Make agency.

Connect

How do you connect STEL Order to Make?

  1. 01

    Add a STEL Order module

    In a new scenario, click the big +, type STEL Order and pick any of its modules, for example Watch Clients. Make then asks for a connection, which is your STEL Order account linked to Make once and reused by every STEL Order module afterward.

  2. 02

    Create the connection

    Click Create a connection. You can give it a name, which helps when a company runs several STEL Order accounts. Make then shows either an authorization page from STEL Order or a field for the key STEL Order gives you, depending on the method the app uses.

  3. 03

    Authorize and save

    Approve access on the STEL Order page, or paste your key, then click Save. The module is now linked: Make can read the records it offers in its lists, and any other STEL Order module in the same scenario picks the connection from a dropdown.

First scenario

Your first scenario: turn each incident into a work order

GoalWhen an incident is logged in STEL Order, Make opens a matching work order so the job is ready to plan.

  1. 01

    Create the scenario

    Open the Scenarios page, click Create a new scenario, then click the + in the middle of the canvas to place your first module.

  2. 02

    Add Watch Incidents

    Search STEL Order, choose Watch Incidents and select your connection. This trigger is scheduled: it starts the scenario whenever Make finds incidents on its check.

  3. 03

    Add Create a Work Order

    Click the + on the right of the trigger and pick Create a Work Order. Map what the job needs from the incident bundle, the item passed from one module to the next.

  4. 04

    Test with Run once

    Log a test incident in STEL Order, then click Run once. Open the bubbles above each module to read the bundles they received, and check that the work order appears in STEL Order.

  5. 05

    Schedule and switch it on

    Click the clock on Watch Incidents to set the interval, every 15 minutes by default, then flip the scenario switch on. From then on, each check that finds an incident creates a work order.

Triggers

What can start a STEL Order scenario?

11 modules start a scenario when something happens in STEL Order. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by STEL Order as soon as it happens.

STEL Order1Watch Clients

Watch Clients

triggerIn the docs only

Watch Clients gets your scenario moving from the client list in STEL Order, so a customer record can reach your mailing tool or CRM without being typed twice. Make's documentation gives no description, so this reading comes from the module name.

How it fires
scheduled. Make checks STEL Order on the scenario's schedule, every 15 minutes by default.
When to use it
a new customer is added by the office and the sales team wants that contact in their own tool too.
Watch out
test with Run once first and read the bundles, to see which clients the module returns before you rely on it.
STEL Order2Watch Events

Watch Events

triggerIn the docs only

Watch Events lets calendar entries from STEL Order drive a scenario, which is handy for pushing appointments into a team chat or a shared agenda. The module name is the only guide here, because Make's documentation does not describe it.

How it fires
scheduled. Make polls STEL Order at the interval set on the scenario's clock.
When to use it
a site visit is booked in STEL Order and the technician should get a message about it.
Watch out
an event booked just after a check waits for the next one, so do not promise instant alerts to your team.
STEL Order3Watch Incidents

Watch Incidents

triggerIn the docs only

Watch Incidents gives support and maintenance teams a way to react when an issue is recorded in STEL Order, by launching whatever comes next: a work order, an alert, a ticket elsewhere. The type is read from the module name.

How it fires
scheduled. Make looks at STEL Order each time the scenario's schedule comes around.
When to use it
a customer reports a broken boiler and the job needs to be opened without anyone rekeying it.
Watch out
if the next module creates records in STEL Order, make sure it does not create incidents, or the scenario feeds itself.
STEL Order4Watch Ordinary Invoice Receipts

Watch Ordinary Invoice Receipts

triggerIn the docs only

Watch Ordinary Invoice Receipts lets you act on the receipts recorded against your standard invoices, for example to update a cash tracking sheet as money is registered. Its behavior is inferred from the name, since the documentation stays silent.

How it fires
scheduled. Make queries STEL Order according to the scenario's schedule.
When to use it
the finance lead wants a line in a spreadsheet each time a receipt is entered in STEL Order.
Watch out
receipts and invoices are two different triggers; pick this one when the payment matters, not the billing.
STEL Order5Watch Ordinary Invoices

Watch Ordinary Invoices

triggerIn the docs only

Watch Ordinary Invoices hands each standard invoice from STEL Order to the rest of your stack, so bookkeeping or reporting tools stay in step with billing. Make's documentation describes nothing, so the name is what this note works from.

How it fires
scheduled. Make checks STEL Order on every scheduled run of the scenario.
When to use it
your accountant works from a shared folder or tool and needs every invoice there without an export by hand.
Watch out
refund invoices have their own modules; this trigger is about ordinary invoices only.
STEL Order6Watch Products

Watch Products

triggerIn the docs only

Watch Products keeps your catalog in STEL Order as the reference for other tools, by starting a scenario from its product records. A web shop or a price sheet can then follow what the back office maintains. The type comes from the name.

How it fires
scheduled. Make checks STEL Order when the scenario's clock says so.
When to use it
a new item is added to the catalog and your online store should list it too.
Watch out
run it once and inspect the bundles to confirm which product changes it picks up before you sync prices.
STEL Order7Watch Sales Delivery Note

Watch Sales Delivery Note

triggerIn the docs only

Watch Sales Delivery Note reacts to the delivery notes issued with your sales, which is the moment goods actually leave. That makes it a good starting point for shipping or customer messages. Make's documentation offers no description, so the name guides this reading.

How it fires
scheduled. Make checks STEL Order at each interval of the scenario's schedule.
When to use it
the customer should get a heads up once their order has been prepared for delivery.
Watch out
pair it with Create Sales Delivery Note only in separate scenarios, never in one that creates what it watches.
STEL Order8Watch Sales Estimate

Watch Sales Estimate

triggerIn the docs only

Watch Sales Estimate brings each sales quote from STEL Order into a scenario, so a follow up can start as soon as Make sees it. Sales teams use this kind of trigger to feed a pipeline or a reminder list. The type is deduced from the module name.

How it fires
scheduled. Make polls STEL Order on the scenario's schedule, not the instant the quote is saved.
When to use it
a rep sends a quote and wants a task in their CRM to call the prospect back.
Watch out
work estimates are a separate trigger, for jobs rather than product sales.
STEL Order9Watch Sales Orders

Watch Sales Orders

triggerIn the docs only

Watch Sales Orders starts a scenario from confirmed sales orders in STEL Order, the natural point to kick off preparation, purchasing or a thank you email. Make's documentation does not describe it, so this reading relies on the module name.

How it fires
scheduled. Make checks STEL Order whenever the scenario's schedule runs.
When to use it
an order comes in and the warehouse team needs a line in their picking sheet.
Watch out
if a later step updates the same order with Update Sales Orders, check with Run once that the update does not bring it back into the next check.
STEL Order10Watch Work Estimates

Watch Work Estimates

triggerIn the docs only

Watch Work Estimates follows the quotes you prepare for jobs and services in STEL Order, so installers and maintenance firms can react as soon as Make sees a new one. The note is read from the name, because the documentation says nothing more.

How it fires
scheduled. Make queries STEL Order on each run of the scenario's schedule.
When to use it
a quote for an air conditioning install goes out and the manager wants it logged in a follow up board.
Watch out
it covers work estimates only; product quotes go through Watch Sales Estimate.
STEL Order11Watch Work Orders

Watch Work Orders

triggerIn the docs only

Watch Work Orders is the starting point for everything that happens after a job is planned in STEL Order: a message to the technician, a line in a planning sheet, a reminder to the client. Its behavior is inferred from its name.

How it fires
scheduled. Make checks STEL Order at the pace of the scenario's schedule.
When to use it
a dispatcher assigns a job and the field team wants it in their group chat.
Watch out
do not chain it to Create a Work Order in the same scenario, or each run creates the next trigger.
Modules

What can Make do in STEL Order?

STEL Order gives you 75 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

STEL Order1

Create Ordinary Invoices

ActionIn the docs only

Create Ordinary Invoices issues a standard invoice in STEL Order from data that starts elsewhere, so billing no longer depends on someone retyping a job or an online sale.

When to use it
a payment platform confirms a sale and the invoice should exist in STEL Order right after.
Watch out
an invoice is a legal document, so test with Run once on a test client before switching the scenario on.
STEL Order2

Create Potential Client

ActionIn the docs only

Create Potential Client drops a prospect into STEL Order the moment someone shows interest, so sales can follow up from the same tool they already quote from.

When to use it
a web form collects a quote request and the lead should wait in STEL Order, not in an inbox.
Watch out
it adds a prospect, not a client; use Create a Client once the deal is real.
STEL Order3

Create Product

ActionIn the docs only

Create Product adds a catalog item to STEL Order from another source, which saves a double entry when products are first defined in a supplier sheet or a shop.

When to use it
a buyer adds a new reference in a shared spreadsheet and the catalog in STEL Order should follow.
Watch out
run a search with List Products first if the item might already exist, or you end up with duplicates.
STEL Order4

Create Purchase Invoice

ActionIn the docs only

Create Purchase Invoice records a supplier bill in STEL Order, so what you owe sits next to what you sell without manual entry from a PDF or an email.

When to use it
supplier bills arrive in a dedicated mailbox or folder and another module has already read their details.
Watch out
match the supplier with Get a Supplier or List Suppliers before creating, so the bill lands on the right record.
STEL Order5

Create Refund Invoices

ActionIn the docs only

Create Refund Invoices produces the corrective invoice in STEL Order when money goes back to a customer, keeping your books aligned with what the payment tool already did.

When to use it
a refund is approved in your shop or payment platform and accounting needs the matching document.
Watch out
a refund cannot be quietly undone, so add a filter that only lets approved refunds through.
STEL Order6

Create Sales Delivery Note

ActionIn the docs only

Create Sales Delivery Note prepares the delivery paperwork in STEL Order as soon as goods are ready to go, so the driver and the customer have a document without the office stepping in.

When to use it
a sales order is confirmed and the warehouse ships the same day it is prepared.
Watch out
keep it out of any scenario that starts from Watch Sales Delivery Note.
STEL Order7

Create Sales Estimates

ActionIn the docs only

Create Sales Estimates turns a request into a proper quote in STEL Order, ready to be reviewed and sent, which shortens the gap between a lead and a priced offer.

When to use it
a configurator or form collects the products a prospect wants and a draft quote should follow.
Watch out
quotes for jobs and labor belong to Create Work Estimates instead.
STEL Order8

Create Sales Orders

ActionIn the docs only

Create Sales Orders places a confirmed order in STEL Order from an outside channel, so an online sale or a signed quote enters the same flow as orders taken by phone.

When to use it
a customer checks out in your online store and preparation should start in STEL Order.
Watch out
if the order comes from a quote already in STEL Order, check the bundles so it is not created twice.
STEL Order9

Create Work Estimates

ActionIn the docs only

Create Work Estimates drafts a quote for a job in STEL Order, the kind installers and repair firms send before sending someone on site, straight from the request that triggered it.

When to use it
a visit report or a booking form describes the job and the estimate should be ready for the manager to price.
Watch out
product sales go through Create Sales Estimates, not this module.
STEL Order10

Create a Client

ActionIn the docs only

Create a Client adds a full customer record in STEL Order, which every quote, order and invoice then hangs from. Automating it keeps names and addresses consistent across tools.

When to use it
a deal is marked won in your CRM and the customer must exist in STEL Order before the first invoice.
Watch out
search with List Clients first; creating the same client twice splits their history.
STEL Order11

Create a Service

ActionIn the docs only

Create a Service adds a billable service to STEL Order, the counterpart of a product for labor, visits or subscriptions, so your quotes can pick it without manual setup.

When to use it
operations define a new maintenance package in a shared sheet and sales should be able to quote it.
Watch out
physical items go through Create Product; this module is for services only.
STEL Order12

Create a Work Delivery Note

ActionIn the docs only

Create a Work Delivery Note records in STEL Order what was done on a job, the document a client signs when the technician leaves, without the office typing it from paper.

When to use it
a technician fills a mobile form at the end of an intervention and the note should appear in STEL Order.
Watch out
link it to the right work order in the mapping, so the note documents the right job.
STEL Order13

Create a Work Order

ActionIn the docs only

Create a Work Order opens a job in STEL Order that a technician can be assigned to, which is the step that turns a request into planned field work.

When to use it
an incident, a booking or an accepted estimate should become a job without a dispatcher copying it.
Watch out
never place it after Watch Work Orders in the same scenario, or the scenario keeps feeding itself.
STEL Order14

Create an Address

ActionIn the docs only

Create an Address adds a location in STEL Order, useful when a client has several sites and each job or delivery must go to the right one.

When to use it
a customer with many stores sends a new site through a form and technicians need it on file.
Watch out
check with List Addresses whether the site is already recorded before adding it again.
STEL Order15

Create an Asset

ActionIn the docs only

Create an Asset registers equipment in STEL Order, such as a machine you install or maintain for a client, so later incidents and jobs can point to it.

When to use it
an installation is finished and the equipment should be on file for future maintenance.
Watch out
map the client correctly, because an asset attached to the wrong account is hard to spot later.
STEL Order16

Create an Event

ActionIn the docs only

Create an Event puts an entry in the STEL Order calendar, so appointments booked in another tool show up where the team plans its day.

When to use it
a client books a slot through an online booking page and the visit should appear in STEL Order.
Watch out
use List Calendars or Get a Calendar first if your account has several calendars, to target the right one.
STEL Order17

Create an Incidence

ActionIn the docs only

Create an Incidence logs a customer issue in STEL Order from wherever it was reported, so every problem ends up in one queue your team already works from.

When to use it
a support form or a shared inbox receives a complaint and it should become an incident.
Watch out
do not run it in a scenario started by Watch Incidents, or each new incident creates another.
STEL Order18

Get Document State by ID

ActionIn the docs only

Get Document State by ID returns the status that goes with a known state ID, so a raw code in a bundle becomes something a person can read in a report or a message.

When to use it
a document arrives with only a state ID and your message to the client should say where it stands.
Watch out
you need the ID first, often from List Document States.
STEL Order19

Get Incident

ActionIn the docs only

Get Incident reads one incident from STEL Order when you already know which one, which fills in the detail a trigger or another app only referenced.

When to use it
a message in your support tool mentions an incident and the scenario needs its full record to reply.
Watch out
to browse several incidents, List Incidents is the module to pick instead.
STEL Order20

Get Ordinary Invoice

ActionIn the docs only

Get Ordinary Invoice fetches a single standard invoice from STEL Order, the right move when a scenario knows which invoice it is about and needs its content.

When to use it
a payment notice references an invoice and you want its detail before updating your cash sheet.
Watch out
it returns one invoice; List Ordinary Invoices is for a batch.
STEL Order21

Get Sales Order

ActionIn the docs only

Get Sales Order pulls one sales order from STEL Order, giving later modules the full content of an order that was only named in a message or a spreadsheet row.

When to use it
a carrier updates a shipment and the scenario needs the matching order to inform the customer.
Watch out
if you do not know which order yet, start with List Sales Orders.
STEL Order22

Get Stock Movements

ActionIn the docs only

Get Stock Movements retrieves the stock movements STEL Order records, so you can follow what goes in and out of your warehouses from a report or a dashboard.

When to use it
a purchasing manager wants stock activity copied to a spreadsheet after each delivery note.
Watch out
the documentation does not say how many movements come back per call, so check the bundles with Run once.
STEL Order23

Get Tax Lines

ActionIn the docs only

Get Tax Lines reads the tax detail STEL Order keeps, which accountants need when invoices travel to another bookkeeping tool with the right rates.

When to use it
an invoice goes to your accounting software and the tax breakdown must match what STEL Order computed.
Watch out
run it once and look at the output, since the documentation does not describe what the lines contain.
STEL Order24

Get Work Estimate

ActionIn the docs only

Get Work Estimate brings back one job quote from STEL Order so the scenario can reuse its content, for a reminder, a task or a copy sent to a partner.

When to use it
a client replies to a quote email and you want the matching estimate before creating the job.
Watch out
for several estimates at once, List Work Estimates fits better.
STEL Order25

Get a Calendar

ActionIn the docs only

Get a Calendar reads one calendar from STEL Order, which helps when events must be placed or checked in a specific team's agenda rather than any agenda.

When to use it
each technician has a calendar and the scenario must confirm which one a booking belongs to.
Watch out
List Calendars gives you the full set when you do not have the calendar's reference yet.
STEL Order26

Get a Client

ActionIn the docs only

Get a Client pulls a single customer record from STEL Order, so the next modules have the name and details they need to write, bill or schedule correctly.

When to use it
an invoice trigger gives you the client reference and your welcome email needs their details.
Watch out
it needs to know which client; search with List Clients when you only have a name.
STEL Order27

Get a Product

ActionIn the docs only

Get a Product returns one catalog item from STEL Order, a handy lookup when another tool only carries a reference and you need the rest of the product sheet.

When to use it
an order in your shop names a product and the scenario wants the price kept in STEL Order.
Watch out
services are a separate kind of record and are not read by this module.
STEL Order28

Get a Supplier

ActionIn the docs only

Get a Supplier reads one vendor record in STEL Order, so purchase documents or payment files can carry the right supplier details without a manual lookup.

When to use it
a bill arrives and you need to confirm the supplier before creating the purchase invoice.
Watch out
List Suppliers is the better start when you only know part of the name.
STEL Order29

Get an Address

ActionIn the docs only

Get an Address fetches one saved location from STEL Order, so a route planner, a carrier or a technician message gets the exact site instead of the head office.

When to use it
a work order points to a client site and the dispatch message should include where to go.
Watch out
clients with many sites may need List Addresses first to find the right one.
STEL Order30

List Addresses

SearchIn the docs only

List Addresses returns the saved locations in STEL Order as separate bundles, a good base for syncing sites to a map or checking what already exists.

When to use it
before Create an Address, to avoid adding a site the office already recorded.
Watch out
a search can return zero, one or many bundles, and every following module runs once per bundle, which counts operations.
STEL Order31

List Assets

SearchIn the docs only

List Assets gives you the equipment registered in STEL Order, one bundle per asset, which is the raw material for a maintenance plan or an inventory export.

When to use it
a service manager wants all installed machines in a spreadsheet to plan inspections.
Watch out
each asset returned triggers the next modules once, so a large fleet uses operations quickly.
STEL Order32

List Assets Images

SearchIn the docs only

List Assets Images brings back the pictures attached to equipment in STEL Order, so photos taken on site can be archived or shared outside the app.

When to use it
a client asks for the photos of their installed units and you want them copied to a shared folder.
Watch out
the Free plan caps files at 5 MB, so large photos may need a paid plan.
STEL Order33

List Calendars

SearchIn the docs only

List Calendars shows every calendar set up in STEL Order, one bundle each, which is what you need to pick the right agenda before writing events into it.

When to use it
you are building a booking scenario and want to know which calendars the team uses.
Watch out
once you know the calendar, Get a Calendar is lighter than listing them all each run.
STEL Order34

List Clients

SearchIn the docs only

List Clients returns customers from STEL Order as a series of bundles, the base for a dedupe check, a mailing export or a sync with a CRM.

When to use it
before Create a Client, to see whether the person already exists.
Watch out
when nothing matches, the search returns no bundle and the modules after it do not run, so plan that branch with a filter.
STEL Order35

List Document States

SearchIn the docs only

List Document States returns the statuses STEL Order uses for its documents, which lets you translate state IDs and build filters on real values.

When to use it
you want a filter that only lets accepted quotes through and need to know which state means accepted.
Watch out
these values rarely change, so run it once while building rather than in every scenario run.
STEL Order36

List Employees

SearchIn the docs only

List Employees gives you the team members registered in STEL Order, one bundle each, useful to route a job or a message to the right person.

When to use it
a scenario assigns incoming jobs and needs the list of technicians to choose from.
Watch out
employee data is personal, so only send it to tools your team is allowed to use.
STEL Order37

List Events

SearchIn the docs only

List Events returns entries from the STEL Order calendar as bundles, handy for a recap message or a copy of the agenda in another tool.

When to use it
the field team wants tomorrow's visits posted in their group chat.
Watch out
to start a scenario from new events, Watch Events is the trigger; List Events is a lookup you place later in the flow.
STEL Order38

List Expenses

SearchIn the docs only

List Expenses pulls the expenses recorded in STEL Order into your scenario, so cost reporting can happen in a spreadsheet or a finance tool without an export.

When to use it
the owner wants a running cost sheet next to the sales figures already synced.
Watch out
if you also track investments, List Expenses and Investments may be the better choice.
STEL Order39

List Expenses and Investments

SearchIn the docs only

List Expenses and Investments returns both day to day costs and larger purchases from STEL Order, giving a fuller picture of spending than expenses alone.

When to use it
your accountant wants equipment purchases and running costs in one export.
Watch out
do not combine it with List Expenses in the same report, or the same costs appear twice.
STEL Order40

List Incidents

SearchIn the docs only

List Incidents returns the incidents recorded in STEL Order, one bundle per issue, the base for a support dashboard or a review of open problems.

When to use it
a manager wants every incident for a client copied to a shared report before a meeting with them.
Watch out
each incident returned runs the next modules once, so filter early to keep operations under control.
STEL Order41

List Item Images

SearchIn the docs only

List Item Images pulls the pictures attached to your STEL Order items into the scenario, so a later module can reuse them in a catalog, a web shop sync or a shared folder. Each image arrives as its own bundle, the unit of data Make passes from one module to the next.

When to use it
a product changes and you want its visuals to follow it into another tool.
Watch out
an item with no image returns zero bundles, so the modules after it simply do not run.
STEL Order42

List Ordinary Invoice Receipts

SearchIn the docs only

List Ordinary Invoice Receipts gives you the receipts recorded against your standard sales invoices, which is how you see what has actually been collected rather than just billed. Every receipt comes out as a separate bundle you can map into a sheet or a report.

When to use it
finance wants a cash-in view built outside STEL Order.
Watch out
to react to each new receipt as it is recorded, Watch Ordinary Invoice Receipts is the better starting point.
STEL Order43

List Ordinary Invoices

SearchIn the docs only

List Ordinary Invoices returns your regular sales invoices as a batch, ready to be copied into accounting, a dashboard or a follow-up list for unpaid bills. Think of it as a search: the result can be empty, a single invoice or many.

When to use it
you need the whole set at a given moment, not only the latest arrival.
Watch out
every invoice returned makes the next modules run once more, and each run counts as an operation on your Make plan.
STEL Order44

List Payment Options

SearchIn the docs only

List Payment Options reads the payment methods set up in your STEL Order account, so your scenario can match a method name coming from another tool with the one STEL Order knows. It gives the scenario valid values to pick from.

When to use it
you create invoices or orders from outside and must pick a valid payment method.
Watch out
place it early in the scenario so it runs once, not again for every document you create.
STEL Order45

List Potential Clients

SearchIn the docs only

List Potential Clients brings back your leads, the prospects stored in STEL Order before they become customers, so a sales team can work them in a CRM, a mailing tool or a call list. Each prospect travels as one bundle.

When to use it
you want a clean export of the pipeline or a check before adding a new lead.
Watch out
once a prospect is converted, look for it with List Clients instead.
STEL Order46

List Product Components

SearchIn the docs only

List Product Components shows the parts that make up a composite product, which helps anyone who sells kits or assembled goods keep a bill of materials in sync elsewhere. Make hands you each component as a bundle you can map.

When to use it
a production planner or a supplier file needs the breakdown of a product.
Watch out
a simple product without components gives an empty result, which is normal and not an error.
STEL Order47

List Product Warehouse

SearchIn the docs only

List Product Warehouse tells your scenario where a product sits across your warehouses, which is the building block for stock alerts or a multi-site inventory sheet.

When to use it
you need stock by location, not just a product record.
Watch out
the Make documentation for STEL Order is limited, so click Run once and read the bundles before relying on what this module returns.
STEL Order48

List Products

SearchIn the docs only

List Products exports your product catalog from STEL Order into the scenario, handy for feeding a price list, an online store or a spreadsheet the sales team actually opens. Each product is a separate bundle.

When to use it
you want the full catalog at once, for a sync or a check.
Watch out
a large catalog means many bundles and as many operations downstream; Watch Products only picks up the new ones.
STEL Order49

List Purchase Delivery Notes

SearchIn the docs only

List Purchase Delivery Notes collects the delivery notes from your suppliers, the paperwork that proves goods reached you, so receiving can be checked against orders in another tool. Every note becomes one bundle.

When to use it
a buyer wants to compare what arrived with what was ordered.
Watch out
this module does not wait for new notes on its own; it runs when the scenario reaches it.
STEL Order50

List Purchase Invoice Receipts

SearchIn the docs only

List Purchase Invoice Receipts shows the payments you have logged against supplier invoices, which is what treasury needs to track money going out. Each payment arrives in the scenario as a bundle you can send to a sheet or a finance tool.

When to use it
you build a cash-out report or reconcile supplier payments.
Watch out
the sales side lives in a different module, List Ordinary Invoice Receipts; do not mix the two.
STEL Order51

List Purchase Invoices

SearchIn the docs only

List Purchase Invoices retrieves the invoices your suppliers sent you, stored in STEL Order, so an accountant can review them or push them into a bookkeeping tool. The search may return nothing, one bill or a whole batch.

When to use it
you prepare a payables review or an export for your accountant.
Watch out
to add a new supplier bill instead of reading existing ones, use Create Purchase Invoice from the first batch of modules.
STEL Order52

List Purchase Orders

SearchIn the docs only

List Purchase Orders reads the orders you placed with suppliers, which lets a scenario chase late deliveries or share open orders with the warehouse team. One bundle per order flows to the next module.

When to use it
purchasing wants a live list of what is still expected.
Watch out
there is no watch module for purchase orders in this app, so pair this search with the scenario schedule to check for changes.
STEL Order53

List Refund Invoice Receipts

SearchIn the docs only

List Refund Invoice Receipts lists the money movements tied to credit notes, so you can confirm a customer refund was actually paid out. Each record reaches Make as one bundle you can log or notify on.

When to use it
support or finance needs proof that a refund went through.
Watch out
the documentation is thin for this app; test with Run once before mapping the result into anything important.
STEL Order54

List Refund Invoices

SearchIn the docs only

List Refund Invoices brings your credit notes, the invoices that cancel or reduce an earlier sale, into the scenario for reporting or for an accounting sync. Returns and disputes become easy to track outside STEL Order.

When to use it
you want every refund visible next to regular sales in one report.
Watch out
to issue a new credit note, reach for Create Refund Invoices, not this search.
STEL Order55

List Sales Delivery Notes

SearchIn the docs only

List Sales Delivery Notes pulls the delivery notes sent to your customers, useful for proving shipment or for turning deliveries into invoices elsewhere. Each note travels as a bundle to the modules that follow.

When to use it
logistics or billing needs the set of notes at a given point.
Watch out
if you only care about newly created notes, Watch Sales Delivery Note avoids handling the old ones again.
STEL Order56

List Sales Estimates

SearchIn the docs only

List Sales Estimates returns the quotes you sent to customers, which lets a sales manager spot open estimates and follow up before they go cold. You can route each quote to a CRM task or a reminder.

When to use it
you review pending quotes as a batch rather than one at a time.
Watch out
an empty result stops the rest of the scenario for that run, so do not read it as a failure.
STEL Order57

List Sales Orders

SearchIn the docs only

List Sales Orders gets the customer orders stored in STEL Order into Make, so fulfilment, stock or a shared dashboard can work from the same data. Every order appears as one bundle.

When to use it
you need a snapshot of orders, for instance to rebuild a report.
Watch out
for a single known order, Get Sales Order returns just that one and saves operations.
STEL Order58

List Services

SearchIn the docs only

List Services reads the services you bill, as opposed to physical products, so a quoting form or a website can show the same offer as STEL Order. The catalog of services lands in your scenario one bundle at a time.

When to use it
a technician tool or booking page needs your service list.
Watch out
products live in List Products; a service search will not return them.
STEL Order59

List Suppliers

SearchIn the docs only

List Suppliers exports your supplier directory, so purchasing contacts stay aligned between STEL Order and a shared address book, a sheet or a procurement tool. Each vendor becomes one bundle.

When to use it
you clean up vendor data or feed another system with it.
Watch out
when the scenario already knows which supplier it wants, Get a Supplier is lighter than listing them all.
STEL Order60

List Warehouses

SearchIn the docs only

List Warehouses tells Make which storage locations exist in your account, your reference list of sites. Useful as a first step when a scenario has to choose the right site.

When to use it
you manage several warehouses and route data by location.
Watch out
place it before any loop over products, so it runs once and not for every item.
STEL Order61

List Work Delivery Notes

SearchIn the docs only

List Work Delivery Notes retrieves the documents that confirm work done on site, the proof a field service company needs before billing. Each note arrives as a bundle ready for an invoice step or an archive.

When to use it
you close jobs in batch and want every signed-off intervention.
Watch out
these are service documents, not shipments; sales deliveries sit in List Sales Delivery Notes.
STEL Order62

List Work Estimates

SearchIn the docs only

List Work Estimates returns the quotes prepared for jobs or interventions, so a team lead can see which proposals still wait for a customer answer. One bundle per estimate goes to the next module.

When to use it
you chase unsigned service quotes from a task tool or a chat.
Watch out
Watch Work Estimates fits better when only freshly created quotes matter.
STEL Order63

List Work Orders

SearchIn the docs only

List Work Orders brings the jobs assigned to your technicians into Make, which opens the door to a planning board, a daily digest in chat or a status sheet. Each work order is a separate bundle.

When to use it
dispatch needs the full list of open jobs at once.
Watch out
many open jobs mean many bundles, and every module after this one runs for each of them.
STEL Order64

Make an API Call

ActionIn the docs only

Make an API Call reaches any endpoint of the STEL Order API from your scenario, reusing the connection you already created. It fills the gaps when none of the 86 listed modules does what you need.

When to use it
a record type or an action is missing from the module list.
Watch out
you have to know the endpoint and its parameters yourself, and the Make documentation for this app is limited.
STEL Order65

Retrieve Events for Reminders

ActionIn the docs only

Retrieve Events for Reminders fetches calendar events so a scenario can turn them into reminders sent through email, SMS or chat. The name points to that use; the Make documentation gives no further detail, so check the output first.

When to use it
you want customers or staff nudged before an appointment stored in STEL Order.
Watch out
click Run once and read the bundles before wiring a message step to them.
STEL Order66

Update Potential Client

ActionIn the docs only

Update Potential Client changes the details of an existing lead in STEL Order, so a form reply or a CRM update keeps the prospect record current without retyping. It acts on one prospect per run of the module.

When to use it
new information about a lead arrives from another tool.
Watch out
the module needs to know which prospect to edit; map it from List Potential Clients or from the step that created it.
STEL Order67

Update Sales Orders

ActionIn the docs only

Update Sales Orders edits a customer order that already exists, so status changes from a shop, a carrier or a warehouse flow back into STEL Order. One order is updated per bundle it receives.

When to use it
the order moves forward in another system and STEL Order should reflect it.
Watch out
a wrong mapping overwrites the order; test with Run once on a sample order first.
STEL Order68

Update Work Delivery Notes

ActionIn the docs only

Update Work Delivery Notes corrects or completes a work delivery note after the job, for instance once a technician app sends the final details. You edit the note in place instead of creating a second one.

When to use it
field data arrives after the note was created.
Watch out
point the module at the right note, usually taken from List Work Delivery Notes earlier in the scenario.
STEL Order69

Update Work Estimates

ActionIn the docs only

Update Work Estimates revises a service quote already in STEL Order, which avoids creating duplicates when the scope of a job changes. The customer keeps a single estimate that stays up to date.

When to use it
a request form or a sales call changes what goes into the quote.
Watch out
use Create Work Estimates for a brand new quote; this module only edits one that exists.
STEL Order70

Update a Client

ActionIn the docs only

Update a Client keeps customer records in STEL Order in step with your other tools: a new address from a form, a new contact from a CRM, fixed in one pass. The module edits one client per bundle.

When to use it
customer data is maintained elsewhere and STEL Order must follow.
Watch out
find the client first with Get a Client or List Clients so the change lands on the right record.
STEL Order71

Update a Product

ActionIn the docs only

Update a Product pushes changes to an existing product, such as a new price or description coming from a supplier file or a store. Your STEL Order catalog stays aligned without manual edits.

When to use it
product data is mastered in another tool.
Watch out
a bad mapping overwrites real data, so check the mapping on one product with Run once before letting the scenario loose.
STEL Order72

Update a Product Category

ActionIn the docs only

Update a Product Category renames or adjusts a category in your catalog, which matters when STEL Order shares its structure with a web shop or a reporting sheet. One category changes per bundle received.

When to use it
you reorganise how products are grouped and want every tool to agree.
Watch out
map the exact category from an earlier step and test with Run once first.
STEL Order73

Update a Service

ActionIn the docs only

Update a Service edits a service you already offer, so a rate change or a new label is reflected in STEL Order and in the quotes built from it. It works on one service at a time.

When to use it
your service list is maintained in a sheet or another app.
Watch out
this module handles services only; physical items go through Update a Product.
STEL Order74

Update an Event

ActionIn the docs only

Update an Event moves or edits an appointment in the STEL Order calendar, so a rescheduling made in a booking tool or a shared calendar shows up for your team.

When to use it
a customer changes a slot from outside STEL Order.
Watch out
map the event you want to change, typically from List Events or Watch Events.
STEL Order75

Update an Incident

ActionIn the docs only

Update an Incident updates a support or after-sales incident, so progress logged in a helpdesk or a chat lands in STEL Order too. Customers and technicians look at the same status.

When to use it
incidents are handled in another tool but must stay current in STEL Order.
Watch out
map the incident to change, for instance from List Incidents, or the update lands on the wrong ticket.
Need help

Need help automating STEL Order with Make?

A person reads every message.

FAQ

STEL Order and Make: common questions

01Is the STEL Order Make integration free?
Yes, STEL Order is a standard app in Make, so you can use it from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between 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, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one per module run on one bundle. Your STEL Order subscription is a separate matter this page does not cover.
02What do you need to connect STEL Order to Make?
A STEL Order account and a Make account are enough to begin, since Make's documentation lists no other prerequisite. The connection follows the generic Make flow: add a STEL Order module, click Create a connection, optionally name it, then either authorize Make on the STEL Order page or paste the key STEL Order gives you, and click Save. The documentation gives no official steps specific to STEL Order, so if something fails, reconnect with the account that owns the data you want to automate.
03Do STEL Order triggers in Make work in real time?
No. All 11 STEL Order triggers are scheduled, and none is instant. Make checks STEL Order on the schedule you set on the first module, every 15 minutes by default, and each check picks up what it finds. On the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute. If you need a faster reaction, lower the interval on a paid plan. Make's list has no instant STEL Order trigger to rely on.
04What if a STEL Order module is missing in Make?
Use Make an API Call. STEL Order has this module in Make, and it lets a scenario call any endpoint of the STEL Order API with the same connection you already created, which covers what the 86 listed modules do not. Be aware that Make's documentation for STEL Order is limited: it names the modules without describing them, so test each module with Run once and read the bundles before building on it. The Make troubleshooting guide can help when a run fails.
05Make or n8n for STEL Order?
It depends on what you already run. On Make, STEL Order has 86 modules, 11 scheduled triggers, 41 actions and 34 searches, plus Make an API Call for the rest. This page does not confirm whether n8n offers a STEL Order node, so check that before choosing. Then compare the two on the modules your process needs, and keep your automations in the tool your team already knows. The n8n vs Make comparison, linked higher on this page, sets the two side by side.