Resources · Make integration

Orderry Make integrationAutomate Orderry with Make.

Can Make keep your Orderry orders, clients and tasks up to date for you? The Orderry Make integration gives you 37 modules: 20 actions that create or update records and 17 searches that look them up. This page shows how to link your account and build a first working scenario.

Try the Orderry integration on MakeSee the 37 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Orderry Make integration do for you?

The Orderry Make integration lets a Make scenario, the automation you build in Make as a chain of modules, write to and read from your Orderry account. Each module is one brick: here, an action that creates or changes an order, a client, a lead or a task, or a search that finds them, all without code.

Orders that open themselves. A request lands in another tool, Make checks whether the person already exists with Search Client, creates them with Create a Client if not, then opens the job with Create an Order. Nobody copies a phone number twice.

Leads that keep their history. When a prospect writes back, Search Leads finds the record and Create a Lead Comment stores the message on it, so the next person who opens the lead sees the whole exchange.

Payments and follow-ups in one pass. Once a payment is confirmed elsewhere, Create a Payment Record logs it in Orderry, Update an Order Status moves the order forward and Create a Task reminds a colleague to call the customer.

What Make does not do here: Orderry has no trigger module, so a scenario cannot start from an event inside Orderry. It starts from another app or from a schedule. When a listed module falls short, Make an API Call reaches the rest of the Orderry API with the same connection. To learn the editor properly, the Make training starts from zero; if you are weighing tools, read n8n vs Make; and when a run fails, Make troubleshooting lists the usual fixes.

Connect

How do you connect Orderry to Make?

  1. 01

    Copy your API key in Orderry

    You need an active Orderry account and its API key. In Orderry, open Settings, click API or API Access in the menu, then copy the key shown on screen. Keep that tab open until the connection is saved.

  2. 02

    Add an Orderry module in Make

    In your scenario, add any Orderry module and click Create a connection. A connection is your Orderry account linked to Make once; every Orderry module in your scenarios reuses it. 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 into the credentials field, or follow the instructions Make shows on screen, and confirm. Make can now list what it reads in your account when you fill the module fields.

First scenario

Build your first scenario with Orderry

GoalWhen a new request arrives in another app, Make creates the client in Orderry and opens an order for them.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Since Orderry has no trigger, the first module comes from the app where requests arrive, such as your form tool.

  2. 02

    Add Create a Client

    Click the + on the right of that first module, search Orderry and pick Create a Client. Choose your connection, then map the name and contact data coming from the previous module.

  3. 03

    Open the order

    Add Create an Order after it and map the client you just created, so the order is attached to the right person. Make lists the Orderry objects it can read once the connection exists.

  4. 04

    Test with Run once

    Click Run once and send a test request. Each module shows the bundles it received, one bundle being one item passed along; open them to confirm the client and the order look right in Orderry.

  5. 05

    Set the schedule and switch it on

    Open the clock on the first module to set Scheduling: a new scenario checks every 15 minutes by default. Then switch the scenario on so it runs without you.

Modules

What each Orderry module does in Make

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

Orderry1

Add an Item to Order or Estimate

ActionIn the docs only

Your existing Orderry order or estimate gets an extra line without anyone retyping it: the module appends an item to a record that is already open.

When to use it
a customer approves an additional part or service by email and the job should reflect it before work continues.
Watch out
it needs to know which order to touch, so put Search Order in front when you only hold a customer name.
Orderry2

Create a Asset

ActionIn the docs only

A new asset appears in Orderry, filled from data another app already holds, so the equipment you track is on file before the first job starts.

When to use it
a customer registers a device through your intake form and you want it recorded against their account right away.
Watch out
the module creates a fresh record each run; run Search Asset first if the same item may already exist.
Orderry3

Create a Client

ActionIn the docs only

Contacts who reach you anywhere become Orderry clients automatically, which spares your front desk from copying names and phone numbers by hand.

When to use it
as the first Orderry step of any scenario that later opens an order, since the order needs a client to belong to.
Watch out
nothing here stops duplicates, so pair it with Search Client and a filter that only lets unknown people through.
Orderry4

Create a Lead Comment

ActionIn the docs only

Every reply a prospect sends can land as a comment on their Orderry lead, giving whoever picks up the lead next the full story in one place.

When to use it
a prospect answers a quote email or chat message and the sales person should see it without switching tools.
Watch out
the comment attaches to an existing lead, so find that lead with Search Leads earlier in the scenario.
Orderry5

Create a Lead Entity

ActionIn the docs only

Fresh inquiries turn into Orderry leads the moment Make receives them, instead of waiting in an inbox until someone has time to enter them.

When to use it
a contact form on your website, an ad form or a chat tool collects a request that is not yet a paying job.
Watch out
a lead is not a client; when the deal is won, your scenario still needs Create a Client or Update a Lead to reflect it.
Orderry6

Create a Payment Record

ActionIn the docs only

Money received outside Orderry gets logged inside it, so your team no longer reconciles a payment tool and the order list by eye.

When to use it
your online payment tool confirms a charge and the matching Orderry order should show it as paid.
Watch out
a payment written twice is hard to spot later; test with Run once on a single bundle before switching the scenario on.
Orderry7

Create a Posting

ActionIn the docs only

This module writes a posting into Orderry from data your scenario already carries, which keeps that record in step with the tool where the event started.

When to use it
another system of yours produces the entry first and Orderry should hold the same line without a second manual input.
Watch out
the documentation gives no detail on what a posting contains, so open the module in Make and read its fields before mapping anything.
Orderry8

Create a Product

ActionIn the docs only

Your Orderry catalog grows from the source you already maintain, so a product added in one place is ready to sell or add to an order in the other.

When to use it
a supplier list or a spreadsheet gets a new reference and your team needs it in Orderry before quoting it.
Watch out
to change an existing reference, use Update a Product; running this module again creates a second product.
Orderry9

Create a Task

ActionIn the docs only

A reminder shows up in Orderry for the right colleague whenever something upstream calls for action, so follow-ups stop depending on memory.

When to use it
an order reaches a status that needs a callback, or a new lead should be contacted by someone on the team.
Watch out
if the task must go to a named person, run Search Employees first to get the right record to assign.
Orderry10

Create an Invoice Comment

ActionIn the docs only

Notes about an invoice, such as a customer query or a payment promise, end up stored on that invoice in Orderry rather than scattered across emails.

When to use it
your accounting inbox receives a message about a bill and the finance person wants it visible on the invoice itself.
Watch out
the comment needs its invoice, so locate it with Search Invoice before this module runs.
Orderry11

Create an Order

ActionIn the docs only

Jobs open in Orderry as soon as the request is confirmed elsewhere, which means the workshop sees new work without anyone keying it in.

When to use it
a booking tool, a form or an online shop confirms a request that should become a job for your team.
Watch out
an order belongs to a client; create or find that client in an earlier module and map it here.
Orderry12

Create an Order Comment

ActionIn the docs only

Updates about a job, from a customer message to a note from a partner, are appended to the Orderry order where technicians actually look.

When to use it
a customer replies with extra details about their request after the order is already open.
Watch out
identify the order first with Search Order; a comment sent without the right order has nowhere useful to land.
Orderry13

Make an API Call

ActionIn the docs only

Anything the Orderry API offers but the listed modules do not can still be reached from your scenario, using the connection you already set up.

When to use it
you need an endpoint no ready-made module covers, and you are comfortable reading the Orderry API documentation to shape the request.
Watch out
this module expects you to write the request yourself; try the dedicated modules first, they are simpler to fill.
Orderry14

Search Asset

SearchIn the docs only

Before touching equipment records, your scenario can find the asset already stored in Orderry and reuse it instead of creating a lookalike.

When to use it
a device comes back for another job and you want the new order to point at the asset you already track.
Watch out
a search returns zero, one or several bundles, and every bundle flows into the next module as its own run.
Orderry15

Search Cashbox Transactions

SearchIn the docs only

Cashbox movements recorded in Orderry become available to the rest of your scenario, ready to copy into a sheet or an accounting tool.

When to use it
your bookkeeper wants cash entries from Orderry in the spreadsheet they already keep for the books.
Watch out
many transactions mean many bundles, and each one downstream costs an operation, the unit Make counts on your plan.
Orderry16

Search Client

SearchIn the docs only

Knowing whether a person is already an Orderry client lets your scenario decide between reusing the record and creating a new one.

When to use it
right before Create a Client or Create an Order, so a returning customer does not end up with two files.
Watch out
when nobody matches, the search returns no bundle and the modules after it do not run; add a filter or a route for that case.
Orderry17

Search Employees

SearchIn the docs only

Your team members in Orderry can be looked up by the scenario, which is how a task or an order ends up assigned to a real person.

When to use it
a new lead should go to a specific salesperson, or a job needs a technician attached before it starts.
Watch out
the search can return several people; narrow it so only the colleague you want reaches the next module.
Orderry18

Search Invoice

SearchIn the docs only

Invoices stored in Orderry become reachable from other tools, so a payment or a customer question can be matched to the right bill.

When to use it
a payment notification arrives and you need the invoice it settles before logging anything.
Watch out
check the bundles in Run once; a loose search can hand back more invoices than the one you meant.
Orderry19

Search Leads

SearchIn the docs only

Existing Orderry leads can be found and reused, which keeps a returning prospect on the same record instead of opening a duplicate.

When to use it
a prospect writes again from a form or chat and the scenario should add to their lead, not start over.
Watch out
each lead found becomes its own bundle; if two match, both go through the rest of the scenario.
Orderry20

Search Locations

SearchIn the docs only

The locations set up in Orderry are listed for your scenario, so new orders or tasks can be tied to the branch that handles them.

When to use it
you run several sites and incoming requests must reach the right one based on data from the form.
Watch out
the result is a list of locations, not a single one; add a filter to keep the site you need.
Orderry21

Search Order

SearchIn the docs only

An order already in Orderry can be located from an outside event, giving later modules the record they need to comment on, update or bill.

When to use it
a customer replies about their job and you want the reply attached to the matching order.
Watch out
without a precise search, several orders can come back, and each would receive the same change.
Orderry22

Search Order Custom Fields

SearchIn the docs only

The custom fields your Orderry account adds to orders are returned to the scenario, so you can see what extra data your setup expects.

When to use it
while building a scenario that creates or updates orders and you need to know which custom fields exist.
Watch out
this reads the field setup, not the values of one order; use Search Order for those.
Orderry23

Search Order Statuses

SearchIn the docs only

The list of statuses your Orderry orders can take comes back to Make, which saves you from guessing the exact value to set.

When to use it
just before Update an Order Status, to pick the status that matches the event in the other app.
Watch out
statuses are specific to your account, so a scenario copied from another Orderry account may need them reselected.
Orderry24

Search Order Types

SearchIn the docs only

Order types defined in Orderry are fetched for the scenario, so each new job is filed under the category your team actually uses.

When to use it
your intake form offers several kinds of request and each should open a different type of order.
Watch out
the search lists types, it does not create one; any new type has to be set up in Orderry first.
Orderry25

Search Product by Id

SearchIn the docs only

One exact Orderry product comes back when you already hold its identifier, with no risk of a close match slipping through.

When to use it
another module or tool gives you a product Id and you need that product's details for an order line.
Watch out
without a valid Id there is nothing to return; use Search Products when you only know the name.
Orderry26

Search Products

SearchIn the docs only

Browsing the Orderry catalog becomes something your scenario can do, handing matching products to whatever comes next.

When to use it
you sync the catalog to a spreadsheet or check whether a reference exists before Create a Product.
Watch out
a broad search yields many bundles, and each later module runs once per product, which adds up in operations.
Orderry27

Search Sales

SearchIn the docs only

Sales recorded in Orderry can feed reporting tools, so the numbers your manager reads come straight from the source.

When to use it
you build a dashboard or a shared sheet that should list Orderry sales alongside other channels.
Watch out
every sale found passes on as a separate bundle; use an aggregator in Make if you want them as one list.
Orderry28

Search Service by Id

SearchIn the docs only

A single Orderry service is fetched directly from its identifier, which is the safest way to reuse the exact service in an order.

When to use it
your booking tool stores the Orderry service Id and the scenario needs its details to fill an order.
Watch out
the module needs the Id itself; when you have only a service name, Search Services is the right choice.
Orderry29

Search Services

SearchIn the docs only

The services you offer in Orderry become searchable from Make, so another tool can show or reuse the same list your team works from.

When to use it
you want to keep a public price list or booking form aligned with the services in Orderry.
Watch out
the results arrive as several bundles; combine them with an aggregator before writing them into one document.
Orderry30

Search Task

SearchIn the docs only

Tasks already open in Orderry can be found by the scenario, so follow-up work is updated rather than created a second time.

When to use it
a customer calls back and the reminder you set earlier should be closed or changed.
Watch out
several tasks can match; keep the search narrow before passing results to Update a Task.
Orderry31

Update a Client

ActionIn the docs only

Client details in Orderry stay current when they change in another tool, which avoids calling a customer on an old number.

When to use it
a customer edits their profile in your booking tool or newsletter form and Orderry should follow.
Watch out
an update overwrites what was there; test on one client with Run once before switching the scenario on.
Orderry32

Update a Lead

ActionIn the docs only

Lead records move forward in Orderry as the conversation progresses elsewhere, so the pipeline reflects where each prospect really is.

When to use it
a prospect books a call or signs a quote in another tool and the lead should show it.
Watch out
find the lead first with Search Leads; this module changes one lead and needs to know which.
Orderry33

Update a Product

ActionIn the docs only

Product changes made in your main source reach Orderry without a manual edit, keeping order lines and quotes consistent.

When to use it
a supplier revises a reference in your spreadsheet and Orderry should carry the corrected data.
Watch out
the module edits a product that exists; pair it with Search Products or Search Product by Id to target it.
Orderry34

Update a Task

ActionIn the docs only

Tasks in Orderry change state when the work is done elsewhere, which keeps your team's to-do list honest.

When to use it
a callback is logged in your phone tool and the matching Orderry task should reflect it.
Watch out
without Search Task earlier in the flow, the module has no task to modify.
Orderry35

Update an Asset

ActionIn the docs only

Asset details stored in Orderry follow the changes captured in other systems, so technicians work from the latest information.

When to use it
a customer reports new details about their device through a form after the asset is already on file.
Watch out
use Search Asset first to pick the right record; updating the wrong asset is hard to notice.
Orderry36

Update an Estimate or Order

ActionIn the docs only

An estimate or order already in Orderry can be edited from the scenario, sparing someone from opening it just to change a detail.

When to use it
the customer confirms a change through email or a form and the job record should match.
Watch out
for moving an order through its workflow, Update an Order Status is the more direct module.
Orderry37

Update an Order Status

ActionIn the docs only

Orders advance in Orderry the moment something happens elsewhere, so status boards reflect payments, approvals or pickups without a click.

When to use it
a payment is confirmed or a customer approves a quote and the order should move to the next stage.
Watch out
the status must exist in your account; Search Order Statuses shows the values you can set.
Need help

Need help automating Orderry with Make?

A person reads every message.

FAQ

Orderry and Make: common questions

01Is the Orderry Make integration free?
Yes, Orderry is a standard app in Make, so its modules work on 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 (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. Your Orderry subscription is separate and depends on Orderry's own pricing.
02What do you need to connect Orderry to Make?
You need an active Orderry account and its API key. In Orderry, go to Settings, open API or API Access in the menu and copy the key displayed. In Make, add any Orderry module, click Create a connection, optionally give it a name, then paste the key or follow the instructions on screen. That single connection is then reused by every Orderry module in your scenarios, so you only do this once per account.
03Can Orderry start a Make scenario in real time?
No, Orderry has no trigger module in Make, so an event inside Orderry cannot start a scenario on its own. You have two ways around it. Start from another app's trigger, such as a form or a booking tool, and then use the Orderry actions. Or start from a schedule: the first module runs every 15 minutes by default, the minimum on the Free plan, and down to 1 minute on paid plans, with a search module such as Search Order reading what changed.
04What if an Orderry module you need is missing in Make?
Use Make an API Call. It is part of the Orderry app in Make and lets a scenario call any endpoint of the Orderry API with the connection you already created. It asks you to write the request yourself, so keep the Orderry API documentation open. Before going there, check the 37 listed modules: many needs are covered by pairing a search with an update, for example Search Order followed by Update an Order Status.
05Should you use Make or n8n for Orderry?
It depends on what you need to confirm first. On the Make side, Orderry comes with 37 modules, 20 actions and 17 searches, no trigger, and Make an API Call for anything else, all available from the Free plan. Before picking n8n, check whether it offers a dedicated Orderry node and what that node covers, since this page does not assess it. Compare both on the modules you actually need and on who will maintain the scenarios.
Same platform

Other docs you might need on this stack.

Browse all integrations