Resources · Make integration

RO app Make integrationAutomate RO app with Make.

Can Make create and update RO app orders, clients and leads for you? Yes. The RO app Make integration offers 42 modules, 20 actions and 22 searches, with no code. This guide is for teams that work in RO app every day: connect your API key, build a first scenario, then pick the right module.

Try the RO app integration on MakeSee the 42 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the RO app Make integration automate?

The RO app Make integration links your RO app account to Make, a visual tool where you build a scenario (the automation itself) out of modules (one brick each). You get 42 modules: 20 actions that create or change clients, orders, leads, tasks and products, and 22 searches that read them back. An API key is all it takes, no code.

Three setups show the range. Leads that arrive with their context: a form in another app feeds Create a Lead Entity, then Create a Lead Comment stores the original request right next to the lead. Orders that follow a customer's approval: Search Orders finds the order, Add an Item to Estimate or Order appends the approved line, and Update Order Status moves it to the next stage. Payments logged once: when your payment tool confirms a payment, Create a Payment Record writes it into RO app and Create an Invoice Comment leaves a note for whoever handles accounting.

What Make does not do here: none of the 42 modules is a trigger, so nothing inside RO app can start a scenario by itself. The scenario starts from another app or from its own schedule. RO app also flags its module documentation as AI-generated, so confirm important details with RO app directly.

Before you commit, the Make review walks through the editor, Make pricing explains how operations add up, and n8n vs Make helps if n8n is also on your shortlist.

Connect

How do you connect RO app to Make?

  1. 01

    Copy your API key in RO app

    In RO app, open Settings in the left menu, go to the Integrations section and select the API tab. Copy the API key shown on screen and keep it at hand for the next step.

  2. 02

    Create the connection in Make

    In your scenario, add any RO app module and click Create a connection. A connection is your RO app account linked to Make once, then reused by every RO app module. You can type a label in Connection name if you like.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen, and confirm. From then on the module fields fill with the clients, orders and statuses Make can read from your account.

First scenario

Build your first scenario: web form to RO app lead

GoalWhen someone fills in a form in another app, Make creates a lead in RO app and adds the request as a comment.

  1. 01

    Start from the form app

    On the Scenarios page, create a new scenario and click the +. Add the trigger of the form tool you use: RO app has no trigger, so another app opens the flow.

  2. 02

    Add Create a Lead Entity

    Click the + on the right of the form module, search for RO app and pick Create a Lead Entity. Click Create a connection, then map the name and contact details from the form.

  3. 03

    Attach the request with a comment

    Add Create a Lead Comment after it. Map the lead produced by the previous module and paste the message field of the form, so the sales rep reads the request without leaving RO app.

  4. 04

    Test with Run once

    Send a test entry through the form, then click Run once. Open each module's bubble to read the bundle it received, and check in RO app that the lead and its comment appeared.

  5. 05

    Set the schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Then switch the scenario on.

Modules

What each RO app module does

RO app gives you 42 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

RO app1

Add an Item to Estimate or Order

ActionIn the docs only

Appends a new line to an estimate or an order that already exists in RO app, so an extra product or service lands on the right document without anyone retyping it.

When to use it
a customer approves an additional service by email and the order has to show it before invoicing.
Watch out
the target document must already exist, so place Search Orders or Search Order By Id in front of this module.
RO app2

Create Task

ActionIn the docs only

Gives someone on your team a new task inside RO app, so follow-up work sits where staff already look instead of getting lost in a chat thread.

When to use it
a callback request comes in through your website and one person needs to own it.
Watch out
every bundle (one item passed between modules) that reaches this module produces one more task, so test with Run once before you switch the scenario on.
RO app3

Create a Asset

ActionIn the docs only

Adds an asset record to RO app from data another app sends along, which keeps your asset list complete without manual entry.

When to use it
an intake form in a separate tool describes a device or piece of equipment a client brings in, and you want it on file right away.
Watch out
if the same asset may already be on file, run Search Assets first, or you end up with duplicates.
RO app4

Create a Client

ActionIn the docs only

Opens a fresh client file in RO app, so a new buyer exists in your system the moment they show up somewhere else.

When to use it
someone signs up in your booking tool or online store and you want their details waiting in RO app before they call.
Watch out
returning customers would get a second file; check with Search Clients first and only create when the search comes back empty.
RO app5

Create a Lead Comment

ActionIn the docs only

Pins a written note to a lead in RO app, which keeps the history of a prospect in one place rather than spread across inboxes.

When to use it
right after Create a Lead Entity, to store the original message a prospect typed into your contact form.
Watch out
the module needs to know which lead to comment on, so map the lead from a previous module or from Search Leads.
RO app6

Create a Lead Entity

ActionIn the docs only

Turns an inbound request into a proper lead in RO app, ready for your sales follow-up, without a person copying details over.

When to use it
a quote request lands through a web form, an ad form or a chat tool and should appear in RO app as a prospect.
Watch out
the same person can submit twice; a Search Leads step placed before this one tells you whether they are already in the pipeline.
RO app7

Create a Order

ActionIn the docs only

Opens a new order in RO app from the details another tool collected, so the job is ready to be handled the moment the request is confirmed.

When to use it
a customer books a service online and you want the order created in RO app with their client file attached.
Watch out
an order usually belongs to a client, so find or create the client earlier in the scenario and map it in.
RO app8

Create a Payment Record

ActionIn the docs only

Logs a payment in RO app, so the money side of your records matches what your payment tool already knows.

When to use it
a card payment is confirmed by your online checkout and the matching amount has to be recorded in RO app.
Watch out
money records deserve care, so check the amount and the target invoice with Run once on a test entry before switching the scenario on.
RO app9

Create a Posting

ActionIn the docs only

Writes a posting entry into RO app from data coming out of another module, which spares someone a manual entry each time.

When to use it
another system you rely on records an event that RO app should reflect as a posting, and you want both sides to agree.
Watch out
the RO app documentation gives no detail on posting fields; open the module after connecting and read the list Make displays before mapping anything.
RO app10

Create a Product

ActionIn the docs only

Adds an item to your RO app product catalog, so a new reference you sell appears there without double entry.

When to use it
your team adds a reference in a spreadsheet or a supplier tool and wants it available in RO app as well.
Watch out
run Search Products before it when the reference may already exist; two products with the same name make later searches ambiguous.
RO app11

Create an Invoice Comment

ActionIn the docs only

Attaches a note to an invoice in RO app, which gives accounting context right where the numbers are.

When to use it
a payment arrives through your checkout and you want the invoice to mention the reference of that transaction.
Watch out
you must point the module at one invoice, so get it first from Search Invoices or Search Invoice By Id and map it.
RO app12

Create an Order Comment

ActionIn the docs only

Leaves a comment on an order in RO app, so the people handling it see news from outside without switching tools.

When to use it
a customer replies to a support email with extra information about a job in progress, and the technician should read it on the order.
Watch out
the comment goes to one order only; if Search Orders returned several, each one gets a copy, so use Search Order By Id when you know the exact order.
RO app13

Make an API Call

ActionIn the docs only

Calls any endpoint of the RO app API from your scenario, reusing the same connection, when the dedicated modules do not cover what you need.

When to use it
a record type or an action you see in RO app has no dedicated module here.
Watch out
you write the request yourself, so keep the RO app API documentation open and test the call with Run once before relying on it.
RO app14

Search Asset By Id

SearchIn the docs only

Fetches one precise asset when you already hold its RO app identifier, and returns its full record to the next module.

When to use it
an order or a message from another tool carries an asset ID and you need the rest of that asset's details.
Watch out
this module expects an ID, not a name; to look up an asset by other criteria, Search Assets fits better.
RO app15

Search Assets

SearchIn the docs only

Looks through the assets stored in RO app and hands back every match as its own bundle, ready for the next module.

When to use it
before Create a Asset, to check whether a device or piece of equipment is already registered.
Watch out
a search can return zero, one or many results, and each result runs the following modules again, which costs one operation per module each time.
RO app16

Search Cashbox Transactions

SearchIn the docs only

Reads the transactions recorded in your RO app cashbox, so you can reuse them elsewhere without exporting anything by hand.

When to use it
your accountant wants cashbox movements copied into a spreadsheet or an accounting tool when a period is closed.
Watch out
a broad search can return a long list, and every returned transaction counts toward your operations, so narrow the search as much as the module allows.
RO app17

Search Client By Id

SearchIn the docs only

Retrieves a single client file from RO app with its identifier, the fastest way to get complete details when the ID is known.

When to use it
an order returned by a search only carries the client's ID, and you need the phone number or email to contact them.
Watch out
without a valid ID the module finds nothing; for a lookup by name or email, use Search Clients.
RO app18

Search Clients

SearchIn the docs only

Finds client files in RO app that match your criteria, which is how a scenario tells a new customer from a returning one.

When to use it
just before Create a Client, so a customer who books again is matched to the existing file.
Watch out
an empty result is normal for a new customer; plan what the scenario does in that case, or the next module simply receives nothing.
RO app19

Search Employees

SearchIn the docs only

Lists the employees registered in RO app, useful whenever a scenario has to assign work to a real person on your team.

When to use it
before Create Task, to pick the staff member who should own the follow-up and map them into the task.
Watch out
every employee returned becomes a separate bundle, so a scenario that should assign one task can end up creating one per person.
RO app20

Search Invoice By Id

SearchIn the docs only

Pulls one invoice out of RO app from its identifier, with the details you need for a payment or a reminder.

When to use it
your payment tool returns the RO app invoice ID and you want the full invoice before logging the payment.
Watch out
a mistyped or missing ID stops the module; map the ID from a previous module rather than typing it.
RO app21

Search Invoices

SearchIn the docs only

Brings back the invoices in RO app that match what you ask for, so they can feed a report, a reminder or another tool.

When to use it
you want unpaid invoices sent to a spreadsheet the finance lead reviews.
Watch out
each invoice found is its own bundle and the modules after it run once per invoice; check the count with Run once before switching the scenario on.
RO app22

Search Leads

SearchIn the docs only

Checks the leads already stored in RO app, which prevents the same prospect from being entered twice by an automation.

When to use it
in front of Create a Lead Entity, when your web forms may receive the same person more than once.
Watch out
the search itself changes nothing in RO app; you still need a module after it that acts on what it found.
RO app23

Search Locations

SearchIn the docs only

Returns the locations set up in your RO app account, so a scenario can route work to the right site.

When to use it
your business runs several branches and a new order must be opened at the one closest to the customer.
Watch out
with a single location the module brings little; it earns its place when several sites exist and the choice must be mapped.
RO app24

Search Order By Id

SearchIn the docs only

Opens one specific order from its RO app identifier and passes its full details down the scenario.

When to use it
a customer's reply contains the order number stored in another tool and you need the current state of that job.
Watch out
the module wants the identifier RO app stores; map it from a previous module and confirm with Run once that the right order comes back.
RO app25

Search Order Custom Fields

SearchIn the docs only

Reveals the custom fields defined for orders in your RO app account, so you know what extra data a scenario can fill or read.

When to use it
while building a scenario that creates orders, when your team relies on fields you added yourselves.
Watch out
this module describes fields, it does not return order values; pair it with Search Orders to read what each order holds.
RO app26

Search Order Statuses

SearchIn the docs only

Lists the statuses an order can take in your RO app setup, which gives you the exact value to use when moving an order along.

When to use it
before Update Order Status, so the scenario sets a status that really exists in your account.
Watch out
statuses are specific to each account; a scenario copied from another RO app account needs this step checked again.
RO app27

Search Order Types

SearchIn the docs only

Reads the order types configured in RO app, so new orders created by Make land in the right category.

When to use it
your booking form offers several kinds of service and each should open a different order type.
Watch out
read the result with Run once and map the exact type value, since a type name typed by hand may not match the one RO app stores.
RO app28

Search Orders

SearchIn the docs only

Finds the orders in RO app that match your criteria and sends each one to the next module as a separate bundle.

When to use it
you want every order waiting on a customer to receive a follow-up message through your email or messaging app.
Watch out
a wide search multiplies operations fast, since every module after it runs once per order returned.
RO app29

Search Product By Id

SearchIn the docs only

Gets the full record of one product in RO app when its identifier is already known, handy to check details before using them.

When to use it
an order line carries a product ID and you need the product's name or details for a customer email.
Watch out
for a lookup by name or reference, Search Products is the module to pick; this one only works with an ID.
RO app30

Search Products

SearchIn the docs only

Scans your RO app product catalog and returns the matching products, one bundle each, for the modules that follow.

When to use it
a supplier sends a new price list and you want to know which references already exist before updating them.
Watch out
no match means nothing reaches the next module, so decide whether the scenario should then create the product.
RO app31

Search Sales

SearchIn the docs only

Reads the sales recorded in RO app, so revenue data can travel to reporting or accounting tools without an export.

When to use it
a manager wants sales pushed into a dashboard spreadsheet after each closing of the register.
Watch out
sales can be numerous; a search without limits can spend a large share of your plan's operations in one run.
RO app32

Search Service By Id

SearchIn the docs only

Retrieves one service from RO app by its identifier, with the details needed to quote it or add it to an order.

When to use it
your booking tool stores the RO app service ID and you want the service details before adding the line.
Watch out
the ID has to come from RO app itself; a name typed by a customer will not match here, Search Services handles that.
RO app33

Search Services

SearchIn the docs only

Looks up the services you offer in RO app and returns every match, which lets a scenario turn a customer's choice into the right service.

When to use it
a customer picks a service on your website and the order in RO app should include that exact service.
Watch out
similar service names can return several results; test with Run once and tighten the search until only one comes back.
RO app34

Search Task By Id

SearchIn the docs only

Loads a single task from RO app with its identifier, so the scenario knows its current details before acting on it.

When to use it
a message in your team chat references a task ID and you want to post the task's details back in the thread.
Watch out
the module stops when the ID does not exist; when you only know what the task is about, go through Search Tasks instead.
RO app35

Search Tasks

SearchIn the docs only

Lists the tasks stored in RO app that match your search, giving a scenario the open work to report on or update.

When to use it
you want every open task sent to a shared channel so nothing is forgotten at the end of a shift.
Watch out
each task returned triggers the next modules separately; one message per task can flood a channel, so test first with Run once.
RO app36

Update Lead Entity

ActionIn the docs only

Changes the details of a lead already stored in RO app, so the prospect's record reflects what you learned elsewhere.

When to use it
a prospect answers a follow-up email with a new phone number and the lead should carry it.
Watch out
the module edits the lead you point it to, so find it first with Search Leads and map it rather than guessing.
RO app37

Update Order Status

ActionIn the docs only

Moves an order to another status in RO app, which keeps your pipeline accurate when progress happens outside RO app.

When to use it
a customer approves a quote through an e-signature tool and the order should move forward on its own.
Watch out
the status must be one that exists in your account; read the valid values once with Search Order Statuses.
RO app38

Update Task

ActionIn the docs only

Edits an existing RO app task, so its details stay in line with what happens in the other tools your team uses.

When to use it
a customer reschedules through your booking tool and the related task should reflect the change.
Watch out
map the task from Search Tasks or Search Task By Id; an update sent to the wrong task silently overwrites someone else's work.
RO app39

Update a Product

ActionIn the docs only

Modifies a product already listed in RO app, which keeps prices and details consistent with your master source.

When to use it
your supplier spreadsheet changes and the matching RO app product should follow without anyone editing it by hand.
Watch out
the change applies to live data, so run Search Products first and test on a single product with Run once.
RO app40

Update an Estimate or Order

ActionIn the docs only

Changes an estimate or an order that is already open in RO app, so the document stays right when the customer's request evolves.

When to use it
a customer updates their contact details or request in your form tool and the open estimate should reflect it.
Watch out
to add a line rather than change the document itself, Add an Item to Estimate or Order is the better fit.
RO app41

Update the Asset

ActionIn the docs only

Changes an asset that already exists in RO app with data mapped from earlier modules, so your team works from current information instead of a stale entry.

When to use it
an item comes back from a customer or changes hands in another tool, and its RO app record should follow without retyping.
Watch out
put Search Assets or Search Asset By Id in front to target the right record; a search can return several bundles, and each one costs its own update and operation.
RO app42

Update the Client

ActionIn the docs only

Edits a client already on file in RO app with details coming from a form, a CRM or a spreadsheet, so nobody copies them by hand.

When to use it
a customer sends new contact details through another app, and their RO app card should match before the next order.
Watch out
for a new person, Create a Client is the right module; for an existing one, find the record first with Search Clients or Search Client By Id, then check with Run once which client changed.
Need help

Need help automating RO app with Make?

A person reads every message.

FAQ

RO app and Make: common questions

01Is the RO app Make integration free?
Yes, on the Make side. RO app is a standard app, so its modules work 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 (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in operations each month. You still need your own RO app subscription, which RO app prices separately on its own pricing page.
02What do you need to connect RO app to Make?
An active employee account in RO app with access to the API, and the unique API key tied to it. To find the key, open Settings in the left menu of RO app, then the Integrations section and the API tab, and copy the key shown. In Make, add any RO app module, click Create a connection, optionally name it, and paste the key. That single connection then serves every RO app module in your scenarios.
03Does RO app react in real time in a Make scenario?
No. RO app has no trigger among its modules, neither scheduled nor instant, so an event in RO app cannot start a scenario by itself. You start the scenario another way: with the trigger of another app, such as a form or a payment tool, or with the scenario's own schedule. A new scenario runs every 15 minutes by default, 1 minute at best on paid plans, and each run can then use the RO app search modules to pick up new records.
04What if the RO app module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the RO app API from your scenario with the same connection, so an action without a dedicated module stays within reach. You write the request yourself, with the RO app API documentation open. Keep in mind that RO app marks its module documentation as AI-generated and possibly inaccurate, so test each new call with Run once and confirm important details with RO app before relying on them.
05Should you use Make or n8n with RO app?
It depends on the tool your team already builds in. On Make, RO app comes with 42 modules, 20 actions and 22 searches, plus Make an API Call for the rest, and all of it runs from the Free plan. Many apps also have an n8n node, so check whether RO app has one before you compare the two. Then weigh the modules you actually need against what each tool offers, and pick the one your team is comfortable maintaining.
Same platform

Other docs you might need on this stack.

Browse all integrations