Resources · Make integration

Rentman Make integrationAutomate Rentman with Make.

Can Make keep Rentman fed without anyone retyping data? The Rentman Make integration gives you 26 modules: 18 actions and 8 searches on contacts, projects, costs, appointments and equipment. This guide shows how to link your account and build a first scenario.

Try the Rentman integration on MakeSee the 26 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Rentman Make integration let you automate?

The Rentman Make integration links your Rentman account to Make, a visual tool where you chain apps into a scenario (the automation you build, one brick at a time). Once connected, Make can create contacts and appointments, fetch projects, invoices and equipment, and update or delete records, without a line of code.

Every new lead lands in Rentman. A form or a CRM in another app collects a request, then Create a Contact adds the company to Rentman and Create a request for Rentals opens the matching project request, so the planner starts from a record instead of an email.

Project data reaches the rest of your stack. List Projects/Requests pulls your projects, List Project's Items returns their costs, quotes, crew or equipment, and the next module writes them to a sheet or a reporting tool your finance team already reads.

Crew calendars stay in step. Create an Appointment, Update an Appointment and List Personal/Crew Appointments let a scenario mirror bookings made elsewhere, and Get an Invoice fetches an invoice by its ID when accounting asks for it.

One limit shapes everything: Rentman has no trigger module in Make, so it cannot start a scenario on its own. Another app starts it, or the schedule does. Make's documentation page for Rentman also warns that it is AI-generated and may contain mistakes, so check important details with Rentman. Before committing, the Make review covers the tool in depth, the n8n vs Make comparison helps if you are weighing both, and Make troubleshooting helps when a run fails.

Connect

How do you connect your Rentman account to Make?

  1. 01

    Copy your API token in Rentman

    In Rentman, open Configuration in the settings panel, then Account and Integrations. If the API field is off, click Connect. Then click Show token and copy the API token that appears.

  2. 02

    Add a Rentman module in Make

    In your scenario, add any Rentman module and click Create a connection. A connection is your Rentman account linked to Make once, then reused by every Rentman module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the token and save

    Paste the API token you copied into the connection window, or follow the on-screen instructions, then save. Make now reads your Rentman data, and the module fields can offer the objects it finds instead of asking you to type them.

First scenario

Your first scenario: a Rentman contact for every new request

GoalWhen someone submits a request in your form app, Make creates the matching contact in Rentman.

  1. 01

    Create the scenario

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

  2. 02

    Add Create a Contact

    Click the + on the right of that first module, search for Rentman and pick Create a Contact. Pick your connection, or create it with the API token as shown above.

  3. 03

    Map the request data

    Fill the contact fields by mapping values from the first module: click a field and pick the name or company it received. Each request is a bundle, one item passed from one module to the next.

  4. 04

    Test with Run once

    Submit a test request, then click Run once. Make runs the scenario one time and shows the bundles each module received. Check that the new contact appears in Rentman.

  5. 05

    Schedule and switch it on

    If your form app's module is a scheduled trigger, open its clock to set the schedule, every 15 minutes by default; an instant trigger (lightning badge) fires as soon as a request comes in. Then switch the scenario on. Each module run on a bundle counts as one operation.

Modules

What each Rentman module does

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

Rentman1

Create a Contact

Action

In Make“Creates a new contact.”

Turns a name collected somewhere else into a proper Rentman contact, so nobody copies details by hand before a project can start.

When to use it
a quote request arrives through your website form and the sender needs a record in Rentman before planning begins.
Watch out
the module always creates a new record, so run List Contacts/Persons/Crew first if the company might already exist, or you will collect duplicates.
Rentman2

Create an Appointment

Action

In Make“Creates an appointment.”

Puts an appointment into Rentman from data another app provides, which keeps the planning view complete without double entry.

When to use it
a site visit gets booked in a scheduling tool and the crew planner should see it in Rentman as well.
Watch out
a scenario that runs again on the same booking creates it twice, so test with Run once before switching it on.
Rentman3

Create a request for Rentals

Action

In Make“Creates a new project request or an equipment request.”

Opens a new project request or an equipment request in Rentman, which gives your team a record to qualify instead of an email to forward.

When to use it
right after Create a Contact, when a lead asks for gear for an event and the requester should already exist as a contact.
Watch out
decide which of the two request types you need before mapping, because the module handles both.
Rentman4

Delete a Contact/Person

Action

In Make“Deletes contact or contact person by their ID.”

Removes a contact, or a contact person inside a company, using its ID. Handy for keeping Rentman in line with a cleaned-up CRM.

When to use it
a company gets deleted from your main CRM after a merge and should disappear from Rentman too.
Watch out
a deletion cannot be undone from Make, so check the ID with Get a Contact/Person during tests and run it on a test record first.
Rentman5

Delete a Cost

Action

In Make“Deletes the cost by its ID.”

Erases one cost line from Rentman by its ID, so figures cancelled in another system stop inflating a project.

When to use it
an expense gets rejected in your accounting tool and the matching cost should leave the project in Rentman.
Watch out
nothing brings the cost back afterwards; feed this module an ID you have confirmed with Get a Cost, never a guess.
Rentman6

Delete an Appointment

Action

In Make“Deletes selected appointment.”

Cancels an appointment in Rentman so the crew calendar no longer shows something that will not happen.

When to use it
a client cancels a visit in your booking tool and the slot should free up in Rentman as well.
Watch out
the removal is final; if a scenario ever maps the wrong ID, the wrong appointment disappears, so read the bundles in Run once before activating.
Rentman7

Get a Contact/Person

Action

In Make“Retrieves contact or contact person by their ID.”

Fetches one contact or contact person from Rentman when you already hold its ID, giving later modules its full details to work with.

When to use it
a project record points to a client and the next step, an email or a sheet row, needs that client's details.
Watch out
this module expects an ID, not a name; to find someone by other criteria, start with List Contacts/Persons/Crew.
Rentman8

Get a Contract

Action

In Make“Retrieves a contract by its ID.”

Pulls a single contract out of Rentman by its ID, ready to be copied, archived or sent to another tool.

When to use it
a deal closes in your CRM and the signed contract data should reach your document storage or accounting app.
Watch out
the ID usually comes from List Project's Items or List Contracts/Cost/Invoices earlier in the scenario, so place one of them before this module.
Rentman9

Get a Cost

Action

In Make“Retrieves the cost by its ID.”

Reads one cost line by its ID, which lets a scenario check an amount before acting on it.

When to use it
before Update a Cost or Delete a Cost, to confirm you are touching the right line and see its current values.
Watch out
each call is one operation, so fetching costs one by one across many projects adds up quickly on your plan; a list module may be enough.
Rentman10

Get an Appointment

Action

In Make“Retrieves the appointment by its ID.”

Returns the details of one Rentman appointment from its ID, so a later module can reuse them without anyone opening Rentman.

When to use it
a reminder needs to go out to a client and must quote the appointment exactly as planned in Rentman.
Watch out
without the ID in hand, run List Personal/Crew Appointments first and pick the one you need from its results.
Rentman11

Get an Equipment

Action

In Make“Retrieves equipment or equipment set by its ID.”

Looks up one piece of equipment, or an equipment set, by its ID and hands its details to the next module.

When to use it
a rental quote in another tool refers to an item and you want its Rentman details copied into that quote.
Watch out
sets and single items share this module, so check in the Run once output which kind the ID points to.
Rentman12

Get an Invoice

Action

In Make“Retrieves invoice by its ID.”

Brings back one Rentman invoice by its ID, which is how accounting data leaves Rentman without an export.

When to use it
your bookkeeping tool needs the invoice record once a project wraps up, and retyping it is where mistakes creep in.
Watch out
the module reads a single invoice; to handle several, first return them with List Contracts/Cost/Invoices or List Project's Items.
Rentman13

Get a Project

Action

In Make“Retrieves project by its ID.”

Collects everything Rentman holds about one project, identified by its ID, so the next modules can report or notify from it.

When to use it
a message to the client or to your crew should mention the project as it currently stands in Rentman.
Watch out
the ID must already be known; List Projects/Requests is the usual way to get it inside the same scenario.
Rentman14

Get a Stock Location

Action

In Make“Gets a Stock Location.”

Reads one stock location from Rentman, useful when a warehouse or depot has to appear in a message or a document.

When to use it
a pickup notice sent to a client needs to name the location the gear leaves from.
Watch out
if you do not know which location you need, List Stock Locations returns them all first, and you pass the right one along.
Rentman15

Make an API Call

Action

In Make“Performs arbitrary authorized API call.”

Reaches any endpoint of the Rentman API through the connection you already set up, covering whatever the listed modules leave out.

When to use it
you need an object or an operation that none of the listed modules offers, and the Rentman API documentation shows it.
Watch out
this module assumes you read the API documentation; you write the request yourself, so nothing guides you field by field.
Rentman16

Update a Contact/Person

Action

In Make“Updates contact or contact person by their ID.”

Changes the details of an existing contact or contact person, identified by ID, so Rentman keeps up when a client moves or switches email.

When to use it
someone updates a phone number in your CRM and Rentman should carry the new one without a manual edit.
Watch out
map only the fields you mean to change and test with Run once, and read the result in Rentman before switching the scenario on.
Rentman17

Update a Cost

Action

In Make“Updates the cost by its ID. The function "Erase" is not supported.”

Edits a cost line already in Rentman, found by its ID, so a revised amount from another tool lands on the right project.

When to use it
a supplier revises a price and the finance sheet that tracks it should push the change into Rentman.
Watch out
Make's Erase function is not supported on this module, so plan to overwrite values rather than rely on it.
Rentman18

Update an Appointment

Action

In Make“Updates selected appointment. The function 'erase' is not supported.”

Moves or edits an appointment that already exists in Rentman, keeping the crew planning honest when plans change elsewhere.

When to use it
a client reschedules in your booking app and the matching Rentman appointment should follow.
Watch out
the Erase function is not supported here either; you also need the appointment ID, often from List Personal/Crew Appointments.
Rentman19

List Contacts/Persons/Crew

Search

In Make“Lists all contacts, contact persons or crew members.”

Returns your contacts, contact persons or crew members, each one as its own bundle that later modules process in turn.

When to use it
before creating a contact, to check whether the company already exists, or to send your crew roster to a spreadsheet.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle, so operations climb with the size of the list.
Rentman20

List Contracts/Cost/Invoices

Search

In Make“Lists all contracts.”

Brings back your Rentman contracts as a series of bundles, which is the starting point for any report on signed business.

When to use it
an accountant wants every contract in a shared sheet instead of asking the planner for exports.
Watch out
the directory describes this search as listing all contracts, so expect a long result and check with Run once how many bundles come back.
Rentman21

List Equipment

Search

In Make“Lists all equipment or equipment sets.”

Lists your equipment or your equipment sets, giving a scenario the full catalog to copy, compare or publish.

When to use it
your website or a shared sheet shows what you rent out and should match the Rentman catalog.
Watch out
every item becomes a bundle, and each module after this search runs once per bundle, which costs operations on a large catalog.
Rentman22

List Equipment's Items

Search

In Make“Lists equipment's stock movement, repairs, or serial numbers.”

Digs into one piece of equipment and returns its stock movements, its repairs or its serial numbers, depending on what you ask for.

When to use it
the workshop logs repairs in a sheet and wants the Rentman repair history next to it.
Watch out
the ID of the equipment has to come first, usually from List Equipment, and each returned entry is a bundle that costs operations downstream.
Rentman23

List Personal/Crew Appointments

Search

In Make“Lists personal or crew appointments.”

Pulls personal or crew appointments out of Rentman so another calendar or a message can show who is booked.

When to use it
a team lead wants crew appointments copied into a shared calendar that freelancers can open.
Watch out
check in the Run once output that you got the kind you expected; each returned appointment is a bundle that costs operations downstream.
Rentman24

List Project's Items

Search

In Make“Lists project's contracts, costs, subprojects, quotes, vehicles, crew, or equipment.”

Opens up one project and returns its contracts, costs, subprojects, quotes, vehicles, crew or equipment, whichever you choose.

When to use it
a project manager wants the quotes of a project, or its vehicle list, in a document without rebuilding it by hand.
Watch out
this search works inside a project you already identified, so place List Projects/Requests or Get a Project before it in the flow.
Rentman25

List Projects/Requests

Search

In Make“Lists all projects or project requests.”

Returns your projects or your project requests, one bundle each, which is where most reporting scenarios on Rentman begin.

When to use it
as the first Rentman module of a scheduled scenario that feeds a dashboard or a sales sheet with every open request.
Watch out
since Rentman has no trigger, this search plus the schedule is how a scenario notices new requests, and each run reads the list again.
Rentman26

List Stock Locations

Search

In Make“Lists Stock Locations.”

Gives back the stock locations defined in Rentman, so a scenario knows every depot without hard-coding names.

When to use it
a form or a sheet offers a choice of depots and should stay in line with the list in Rentman.
Watch out
the result is a set of bundles; to handle one location only, pass its reference to Get a Stock Location instead.
Need help

Need help automating Rentman with Make?

A person reads every message.

FAQ

Rentman and Make: common questions

01Is the Rentman Make integration free?
Yes, Rentman is a standard app in Make, available from the Free plan. The Free plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution at most, 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 each month, one per module run on a bundle. You still need your own Rentman subscription.
02What do you need to connect Rentman to Make?
You need an active Rentman account and its API token. In Rentman, open Configuration in the settings panel, then Account and Integrations, click Connect in the API field if it is off, then Show token, and copy it. In Make, add any Rentman module, click Create a connection, give it a name if you like, and paste the token. The connection is created once and every Rentman module in your scenarios reuses it, so the setup is a one-time job per account.
03Can the Rentman Make integration start a scenario in real time?
No. Rentman has no trigger module in Make, scheduled or instant, so Rentman itself never starts a scenario. Two workarounds exist. Start the scenario with a trigger from another app, such as your form tool, and let Rentman modules act after it. Or open the scenario with a Rentman search like List Projects/Requests and run it on a schedule: every 15 minutes by default, 15 minutes at least on the Free plan and 1 minute on paid plans. Each scheduled run reads the list again and counts operations.
04What if a Rentman module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Rentman API with the same connection, so it covers objects and actions the listed modules do not. You write the request yourself from the Rentman API documentation. Also keep in mind that Make's documentation page for Rentman says it is AI-generated and may contain mistakes, so confirm anything important with Rentman directly before building on it. Two known quirks: Update a Cost and Update an Appointment do not support the Erase function.
05Should you pick Make or n8n for Rentman?
It depends on the tool your team already runs. On the Make side, Rentman comes with 26 ready modules, 18 actions and 8 searches, plus Make an API Call for the rest, all behind a single API token connection. What Make lacks for Rentman is a trigger, so every scenario starts from a schedule or another app. Before choosing, check whether the other tool offers what your scenario needs for Rentman, and compare the two on that basis rather than on reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations