Resources · Make integration

remberg Make integrationAutomate remberg with Make.

Can Make keep remberg in sync with the rest of your tools? The remberg Make integration gives you 53 modules: 45 actions and 8 searches over tickets, work orders, assets, contacts and files. This page shows service teams how to connect an account and build a first scenario.

Try the remberg integration on MakeSee the 53 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the remberg Make integration let you automate?

The remberg Make integration links your remberg account to Make, a tool where you build a scenario: an automation made of modules, each one brick that acts on one app. With remberg, those bricks create, read, update, search and delete tickets, work orders, assets, parts, contacts, organizations and files, without writing code.

Won deals become customer accounts. When your CRM marks an opportunity as won, a scenario runs Search organizations to avoid a duplicate, then Create an organization and Create a contact, so the service team inherits a complete record.

Field reports reach the office on their own. A scheduled scenario runs Search work orders to list the jobs, Download a file pulls each report out of remberg, and another app sends it to the customer or files it in a shared drive.

Support requests stop living in inboxes. A message from a web form or a mailbox feeds Create a ticket, and Update a ticket adds details as the case moves on.

Two limits to know before you start. remberg has no trigger module in Make: something else has to start the scenario, either a schedule or another app. It also has no Make an API Call module, so what the 53 modules don't cover stays out of reach from this app. If you are still choosing a platform, the Make review and the n8n vs Make comparison set out the differences; many apps also exist as n8n nodes. Stuck on a run? The Make troubleshooting guide covers the common errors.

Connect

How do you connect your remberg account to Make?

  1. 01

    Create an API key in remberg

    In remberg, open Settings, then Security and API. Click Add API Key, give the key a name you will recognize later, and copy the key shown on screen. You need an active remberg account for this.

  2. 02

    Add a remberg module to a scenario

    In Make, place any remberg module in your scenario and click Create a connection. A connection is your remberg account linked to Make once, then reused by every remberg module you add afterwards.

  3. 03

    Paste the key and save

    Optionally fill Connection name with something explicit, such as the remberg environment it points to. Paste the API key you copied, or follow the instructions Make displays, then confirm to finish the connection.

First scenario

Build your first remberg scenario in Make

GoalWhen a customer sends a request through another app, Make opens a matching ticket in remberg.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since remberg has no trigger, this first module belongs to the app where requests arrive, such as your form tool.

  2. 02

    Add Create a ticket

    Click the + on the right of the first module, search for remberg and pick Create a ticket. Select your connection, or click Create a connection if this is your first remberg module.

  3. 03

    Map the request data

    Fill the fields Make shows for the ticket by mapping values from the first module. Each bundle, one item passed from module to module, here one request, becomes one ticket.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bubbles above each module to read the bundles they received, then check in remberg that the ticket looks right.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What can remberg do in a Make scenario?

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

remberg1

Create a contact

ActionIn the docs only

Adds a new person to remberg from data another app hands over, so the customer's contact details land where your service team already works.

When to use it
a new customer signs up in your CRM or online shop and the field team needs the contact before the first visit.
Watch out
run Search contacts first when the person may already exist, otherwise each run adds a duplicate.
remberg2

Create a folder

ActionIn the docs only

Opens a fresh folder in remberg's file space, giving each new project or customer a tidy place for its documents from the start.

When to use it
right after Create an organization, so the new account gets its own folder before the first report shows up.
Watch out
name folders consistently, because Search files is how later scenarios will find what sits inside them.
remberg3

Create a part

ActionIn the docs only

Registers a spare part in remberg, so the catalogue your technicians consult grows without anyone retyping supplier data by hand.

When to use it
your purchasing tool or a shared spreadsheet receives a new reference and the part should appear in remberg as well.
Watch out
check with Search parts first, since running the scenario again on the same row creates the part a second time.
remberg4

Create a ticket

ActionIn the docs only

Opens a service ticket in remberg from an email, a form entry or a chat message, so no customer request stays stuck in someone's inbox.

When to use it
a customer reports a breakdown through your website form and support must pick it up in remberg.
Watch out
test with Run once on a single request, because every bundle reaching this module becomes one ticket.
remberg5

Create a work order

ActionIn the docs only

Turns a need into a planned job in remberg: a work order your technicians see and can act on, created without copying anything by hand.

When to use it
a ticket has been qualified and someone has to go on site, or a planning sheet lists a maintenance visit to book.
Watch out
place a Get or Search module before it, so the scenario works with the exact record rather than a guessed name.
remberg6

Create an asset

ActionIn the docs only

Adds a machine or a piece of installed equipment to remberg, so the installed base follows your sales instead of lagging behind them.

When to use it
an order ships in your ERP and the delivered unit should exist in remberg before the first service call.
Watch out
run Search assets beforehand when the same unit might already be recorded, to avoid ending up with a twin.
remberg7

Create an asset type

ActionIn the docs only

Defines a new kind of equipment in remberg, for example a product line your company has just launched, so assets of that kind can be filed consistently.

When to use it
a new model enters your product database and its catalogue entry should reach remberg with it.
Watch out
types change rarely, so keep this module in its own scenario rather than running it on every order.
remberg8

Create an organization

ActionIn the docs only

Creates a customer company in remberg, so your service team finds the new client there on its first day, with no manual entry.

When to use it
a deal is won in the CRM and the account must exist in remberg before the kickoff meeting.
Watch out
use Search organizations first, because company names often come back from a CRM with slightly different spellings.
remberg9

Delete a contact

ActionIn the docs only

Removes a person from remberg, which keeps the list your team calls accurate once someone leaves a customer company.

When to use it
a contact is flagged as gone in your CRM and should disappear from remberg too, without a second manual cleanup.
Watch out
a deletion cannot be undone from Make; test on one known contact with Run once before switching the scenario on.
remberg10

Delete a file or folder

ActionIn the docs only

Clears a file or a whole folder out of remberg, a quick way to remove drafts and outdated documents without clicking through them one by one.

When to use it
a newer version of a manual has been uploaded and the old one should go, so nobody opens it by mistake.
Watch out
aimed at a folder, it removes more than one document; confirm the target with Search files first.
remberg11

Delete a ticket

ActionIn the docs only

Erases a ticket from remberg entirely, which suits requests that should never have been opened in the first place.

When to use it
a spam form submission or a duplicate request slipped into remberg through an earlier scenario and needs to go.
Watch out
closing and deleting are different things; if the history matters, prefer Update a ticket and keep the record.
remberg12

Delete a work order by id

ActionIn the docs only

Removes one work order from remberg using its ID, the unique identifier of that record, so a cancelled job no longer shows up in the planning.

When to use it
the ID already sits in the scenario, for example from a Search work orders step, and the customer has cancelled.
Watch out
an ID is not the reference people quote; with only the reference, pick the by-reference variant instead.
remberg13

Delete a work order by reference

ActionIn the docs only

Does the same cleanup as the ID variant but finds the work order through its reference, which is often the only value other tools keep.

When to use it
a cancellation arrives from your booking or billing tool, and that tool only stores the work order's reference.
Watch out
a wrong reference deletes the wrong job with no undo from Make, so try it with Run once on a test order.
remberg14

Delete an asset by id

ActionIn the docs only

Takes an asset out of remberg through its ID, so equipment that was scrapped or sold stops cluttering searches and lists.

When to use it
a decommissioning is recorded elsewhere and the matching ID is already in the scenario from a Search assets step.
Watch out
the service history of that asset may matter later; agree with your team on which removals to automate.
remberg15

Delete an asset by number

ActionIn the docs only

Removes an asset using its number, the variant to reach for when the other system identifies machines by number rather than by remberg ID.

When to use it
your ERP sends the number of a unit that was returned, and remberg should no longer list it.
Watch out
numbers get mistyped more often than IDs; run Get an asset by number first to confirm the right machine.
remberg16

Delete an asset type by id

ActionIn the docs only

Deletes an equipment category from remberg with its ID, a cleanup move for product lines your company no longer supports.

When to use it
a model is discontinued and a previous step, such as Get an asset type by id, has already identified its type.
Watch out
the doc says nothing about what happens to assets still attached to that type; check them before you delete it.
remberg17

Delete an asset type by label

ActionIn the docs only

Performs the same category cleanup, but reaches the type through the label people read on screen instead of an internal ID.

When to use it
a spreadsheet of retired categories lists labels only, and each row should remove one type from remberg.
Watch out
labels that look alike are easy to confuse, and a single typo can hit the wrong category.
remberg18

Delete an organization by id

ActionIn the docs only

Deletes a customer company from remberg through its ID, useful when an account closes for good or was created twice by mistake.

When to use it
your CRM merges two duplicate companies and the extra one should disappear from remberg as well.
Watch out
contacts, assets or tickets may be tied to that company; decide what happens to them before this module runs.
remberg19

Download a file

ActionIn the docs only

Pulls a file out of remberg into the scenario, ready to be attached to an email or stored in a drive by the next module.

When to use it
a service report is complete and the customer should receive it through your mail tool, without anyone exporting it.
Watch out
on the Free plan, Make handles files up to 5 MB, so heavy manuals may call for a paid plan.
remberg20

Get a contact

ActionIn the docs only

Fetches one contact from remberg so later modules can reuse that person's details without anyone looking them up.

When to use it
a ticket comes in and the confirmation message you send to the customer needs the contact's details.
Watch out
Get targets one precise contact; when you only know part of a name, Search contacts is the better starting point.
remberg21

Get a file by id

ActionIn the docs only

Reads one file's record in remberg by its ID, so the scenario knows exactly which document it is about to handle.

When to use it
an earlier step returned a file ID and the next module needs what remberg holds about that file.
Watch out
if you need the document itself rather than its record, Download a file is the module to add next.
remberg22

Get a form

ActionIn the docs only

Brings one remberg form into the scenario, so what was filled in can feed a report, a spreadsheet or a message.

When to use it
a technician completes a checklist form on site and the office wants the answers copied into its own tracking sheet.
Watch out
you need to know which form to fetch; Search forms helps when the scenario starts without that detail.
remberg23

Get a part by id

ActionIn the docs only

Looks up a single spare part by its ID and passes what remberg holds about it on to the next module.

When to use it
a work order mentions a part and your purchasing spreadsheet should show that part's details next to the order.
Watch out
without the ID, go through Search parts instead, which can return several matching parts.
remberg24

Get a ticket

ActionIn the docs only

Retrieves one ticket, handy when a scenario has to decide what to do based on what remberg currently says about the case.

When to use it
another tool needs the latest ticket details before it sends the customer an update.
Watch out
this reads the ticket, not the messages exchanged on it; for those, add Get a ticket conversation after it.
remberg25

Get a ticket conversation

ActionIn the docs only

Collects the exchange attached to a ticket, so the discussion can be archived, summarised or forwarded outside remberg.

When to use it
a case is solved and the whole thread should be stored in your document tool or passed on for a quality review.
Watch out
long threads carry a lot of data, so read what the module received during Run once before mapping it.
remberg26

Get a work order by id

ActionIn the docs only

Grabs one work order by ID so the scenario can reuse its details in an invoice, a report or a message to the customer.

When to use it
right after Create a work order, to read back what remberg recorded before notifying the technician's manager.
Watch out
if the identifier comes from a person rather than a module, the by-reference variant is usually the safer pick.
remberg27

Get a work order by reference

ActionIn the docs only

Finds a work order through its reference, which suits scenarios fed by tools that never saw remberg's internal IDs.

When to use it
your billing tool stores the work order reference and needs the job's details to prepare an invoice.
Watch out
references are often typed by people, so check a real example with Run once before trusting the mapping.
remberg28

Get an asset by id

ActionIn the docs only

Reads a single asset from remberg by ID and hands its data to the modules that follow, so messages can name the right machine.

When to use it
a ticket points to a machine and your email to the customer should say which one is concerned.
Watch out
place it after a module that actually outputs the ID, such as Search assets.
remberg29

Get an asset by number

ActionIn the docs only

Pulls an asset through its number, the path to take when a customer or a supplier quotes that number rather than an ID.

When to use it
a service request form asks the customer for the machine number, and the scenario must find the matching asset.
Watch out
a number typed with a mistake finds nothing, so test with a real form entry.
remberg30

Get an asset type by id

ActionIn the docs only

Returns one asset type by ID, useful when a scenario must know which family of equipment it is dealing with before acting.

When to use it
before creating an asset, to confirm that the category the scenario will use still exists in remberg.
Watch out
an ID copied by hand from one environment rarely helps; take it from an earlier module's output.
remberg31

Get an asset type by label

ActionIn the docs only

Finds an equipment category by its visible label, so a scenario fed by plain text, like a spreadsheet column, still reaches the right type.

When to use it
a product sheet lists the category name, and the next module needs the matching remberg type.
Watch out
the label must match what remberg shows, spelling included.
remberg32

Get an organization by id

ActionIn the docs only

Loads one customer company from remberg by ID, so its details can travel to your CRM, a report or an invoice.

When to use it
a work order is finished and the billing step needs the customer company attached to it.
Watch out
when all you have is a company name, begin with Search organizations and keep the ID it returns.
remberg33

Search assets

SearchIn the docs only

Lists the assets in remberg that match what you look for, each one coming out as a separate bundle the next module processes in turn.

When to use it
you want every machine of a given customer copied into a spreadsheet for a service contract review.
Watch out
a search can return zero, one or many results, and each result costs operations further down the scenario.
remberg34

Search contacts

SearchIn the docs only

Looks through remberg's contacts and returns the matches, the natural first step before creating a person who might already be there.

When to use it
a new lead arrives from your website, and the scenario should only call Create a contact when nobody matches.
Watch out
several matches mean several bundles; plan what the scenario does when more than one comes back.
remberg35

Search files

SearchIn the docs only

Finds files stored in remberg, so a scenario can locate a report or a manual without knowing its ID in advance.

When to use it
a customer asks for the documentation of their machine and your support tool should fetch it automatically.
Watch out
chain Download a file after it to get the content, and expect one bundle per file found.
remberg36

Search forms

SearchIn the docs only

Returns the remberg forms matching your criteria, a way to gather completed checklists or inspection sheets in a single run.

When to use it
quality needs the forms filled in on site gathered into one shared table for an audit.
Watch out
each form found becomes one bundle, and every module after the search runs once per form.
remberg37

Search organizations

SearchIn the docs only

Scans the customer companies in remberg and returns those that match, the guard against duplicates whenever accounts flow in from a CRM.

When to use it
before Create an organization, to check whether the company that just signed is already a remberg customer.
Watch out
an empty result is normal for a new customer, so the scenario must handle zero bundles gracefully.
remberg38

Search parts

SearchIn the docs only

Looks up spare parts in remberg and returns every match, so stock or purchasing tools can work from the same list as the technicians.

When to use it
a supplier sends a price list and each line should be compared with the parts remberg already knows.
Watch out
a broad search can return many parts and spend operations quickly on the modules that follow.
remberg39

Search tickets

SearchIn the docs only

Pulls the tickets that match your search, handy for reporting or for finding an open case before creating a new one.

When to use it
a customer writes again about the same issue, and the scenario should add to the existing ticket with Update a ticket.
Watch out
zero, one or many tickets can come back; test with Run once and read the bundles.
remberg40

Search work orders

SearchIn the docs only

Returns the work orders that match, so a scenario can feed a planning board, a billing tool or a dashboard from remberg's jobs.

When to use it
your finance team wants finished jobs listed in its invoicing sheet without asking the service desk for an export.
Watch out
each work order found runs the following modules once, which adds operations on your Make plan.
remberg41

Update a contact

ActionIn the docs only

Edits one existing person in remberg instead of creating a duplicate, so the contact stays in step with the rest of your stack and your customer records stay clean.

When to use it
a customer changes phone or role in your CRM and your service team needs the same details in remberg.
Watch out
the module acts on one contact only, so place Search contacts before it when all you hold is a name or an email.
remberg42

Update a file or folder

ActionIn the docs only

Changes a file or a folder in the remberg document area. The doc does not say which properties it edits; going by its name, it targets the item itself, while the content goes through Update a files content.

When to use it
a project folder in remberg should carry the new customer name after a contract changes hands.
Watch out
point it at the right item before you test; a folder holds everything below it, so a wrong pick shifts more than one document.
remberg43

Update a files content

ActionIn the docs only

Replaces the content of a file that already lives in remberg, so the file keeps its place and the people who use it find the fresh version where they expect it.

When to use it
a manual or checklist gets a new revision in another tool and remberg should hold the latest copy.
Watch out
this module swaps content, it does not add a new file; for a brand new document, Upload a file is the right brick.
remberg44

Update a part by id

ActionIn the docs only

Changes a spare part record in remberg when you already know its internal id. Your parts catalog follows the changes made elsewhere without anyone retyping them.

When to use it
a supplier sheet or your ERP updates a part and remberg must reflect it.
Watch out
the id is not the part name; if the earlier modules only give you a label, run Search parts first and map the id it returns.
remberg45

Update a ticket

ActionIn the docs only

Moves a service ticket forward from outside remberg: the scenario writes back what arrives elsewhere while your team keeps working.

When to use it
a message from a customer in your helpdesk or inbox should update the matching ticket in remberg.
Watch out
find the ticket first with Search tickets or Get a ticket, then run the whole chain with Run once on a test ticket.
remberg46

Update a work order by id

ActionIn the docs only

Edits one work order through its technical id, the identifier remberg itself assigns. It fits scenarios where an earlier module already returned that id.

When to use it
right after Create a work order or Search work orders in the same scenario, to complete the order once more data arrives.
Watch out
Make gives two update modules for work orders; this one wants the id, while the reference version accepts the number your team reads on screen.
remberg47

Update a work order by reference

ActionIn the docs only

Updates a work order using its reference, the identifier people quote in emails and on the phone, so an outside tool can change the order without knowing its internal id.

When to use it
a form or a spreadsheet row names the work order by reference and should push a change to it.
Watch out
a typo in the reference means no match; map the value from the previous module rather than typing it by hand.
remberg48

Update an asset by id

ActionIn the docs only

Rewrites the data of one machine or installation in remberg from its internal id, which keeps your installed base accurate after each field visit.

When to use it
an inspection report from another app should refresh the matching asset once the technician closes the job.
Watch out
if your source only knows the asset number, the by number variant saves you an extra search step.
remberg49

Update an asset by number

ActionIn the docs only

Reaches an asset through the number your technicians already use, then saves the changes you map into it. No lookup of an internal id is needed.

When to use it
a spreadsheet or an intake form lists equipment by asset number and each row should update remberg.
Watch out
each row passing through the module is one bundle and costs one operation, so a long sheet adds up on your plan.
remberg50

Update an asset type by id

ActionIn the docs only

Adjusts an asset type, the category that groups similar machines in remberg, when you hold its internal id.

When to use it
your product team renames or reworks a model line and remberg should follow from a scenario.
Watch out
a type sits above many assets; check the result with Run once on a test setup before you switch the scenario on.
remberg51

Update an asset type by label

ActionIn the docs only

Targets an asset type by its label, the readable name you see in remberg, and applies your changes to it. Handy when the source system speaks in model names, not ids.

When to use it
a product sheet or a catalog export refers to model names and drives the updates.
Watch out
two types with close labels are easy to confuse; map the label exactly as the source writes it.
remberg52

Update an organization by id

ActionIn the docs only

Brings a customer company in remberg up to date from its internal id, with the data your scenario maps from another tool.

When to use it
your CRM or billing tool changes a customer record and remberg should mirror it.
Watch out
the id comes from remberg, not from your CRM; Search organizations or an earlier create step gives it to you.
remberg53

Upload a file

ActionIn the docs only

Sends a new file into remberg, so a report, a photo or a signed document lands next to the records your team already uses.

When to use it
a file arrives in another app, an email attachment or a cloud drive, and belongs in remberg.
Watch out
files on the Free plan are capped at 5 MB in Make; heavy scans may need a paid plan, and Update a files content is the choice for a revision.
Need help

Need help automating remberg with Make?

A person reads every message.

FAQ

Questions about the remberg Make integration

01Is the remberg Make integration free?
Yes, remberg is a standard app in Make, so its modules are available from the Free plan onward. The Free plan has its own limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and allow 40 minutes of execution. You still need an active remberg account on the remberg side, and remberg's own pricing is set by remberg, not by Make.
02What do you need to connect remberg to Make?
An active remberg account and an API key. In remberg, go to Settings, Security, API, click Add API Key, name the key and copy it. In Make, add any remberg module to a scenario, click Create a connection, optionally name the connection, and paste the key. That connection is then reused by every remberg module in your scenarios, so the setup happens once. Need another key later? The same path creates one.
03Can remberg start a Make scenario in real time?
No, not on its own: remberg has no trigger module in Make, neither scheduled nor instant. A scenario that works with remberg starts another way. Either a trigger from another app opens the flow, such as a form tool receiving a request, or the scenario runs on its schedule, every 15 minutes by default. On the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute. From there, remberg search and get modules fetch whatever the scenario needs.
04What if a remberg module is missing in Make?
It depends on what you need. The 53 modules cover creating, reading, updating, searching and deleting tickets, work orders, assets, asset types, parts, contacts, organizations, forms and files. remberg has no Make an API Call module, so anything outside that list can't be reached from the remberg app in Make. Make's documentation for remberg is also marked as AI-generated, so check important details with remberg. If a need remains, another app in your stack may cover it, or the team can study the case with you.
05Should you use Make or n8n for remberg?
It depends on your team and your other tools. On Make, remberg comes with 53 ready modules, a connection by API key and a visual editor where you test each step with Run once, which suits people who build automations without code. Many apps also have an n8n node, so check whether remberg has one before you commit. Compare both on the modules you actually need, on how your team prefers to work, and on where your other automations already run.
Same platform

Other docs you might need on this stack.

Browse all integrations