Resources · Make integration

Restdb.io Make integrationAutomate Restdb.io with Make.

What if your Restdb.io database filled itself from the tools your team already uses? The Restdb.io Make integration gives you 19 modules, 15 actions and 4 searches, to write, read and clean documents without code. This page shows how to connect your account and build a first scenario.

Try the Restdb.io integration on MakeSee the 19 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Restdb.io Make integration do for you?

The Restdb.io Make integration links your database to Make, so a scenario (the automation you build in Make, a chain of modules) can create, read, update and delete documents and media objects for you. Each module is one brick of that chain, and your Restdb.io account is linked once through a connection.

A database that stays current on its own. A web form or a shop passes a new entry to the scenario, Create a Document stores it in the right collection, and Send an Email tells the person in charge. Nobody copies anything by hand.

Records that follow the rest of your stack. When a deal moves in your CRM, Update a Document Property changes the status of the matching record, and Delete a Document removes the ones that were cancelled.

Media that stay in order. Create a Media Object keeps attachments next to the records they belong to, List Media Objects shows what exists, and Delete a Media Object tidies up what is no longer used.

One limit shapes every scenario: Restdb.io has no trigger in Make. A scenario therefore starts from another app, or from its own schedule, and then works inside your database. If you need something the listed modules skip, Make an API Call can call any part of the Restdb.io API with the same connection.

New to the editor? The Make training walks through the basics, Make troubleshooting helps when a run fails, and n8n vs Make sets the two tools side by side.

Connect

How do you connect Restdb.io to Make?

  1. 01

    Copy your database URL and API key

    In your Restdb.io dashboard, click Databases and copy the database URL. Then click Manage on that database, open the API tab and copy the key labeled as the full access API key.

  2. 02

    Add a Restdb.io module in Make

    Log in to Make, add any Restdb.io module to your scenario and click Create a connection. The Connection name field is optional: a clear name helps when you run several databases.

  3. 03

    Paste your credentials

    Enter the credentials you copied from Restdb.io, or follow the instructions on screen, and save. Every Restdb.io module of your scenarios can now reuse this connection without asking again.

First scenario

Your first scenario with Restdb.io

GoalWhen another app sends a new entry to Make, Make stores it as a Restdb.io document and emails the person in charge.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since Restdb.io has no trigger, this first module comes from the app that holds the new entries.

  2. 02

    Add Create a Document

    Click the + on the right of the first module, search for Restdb.io and pick Create a Document. Click Create a connection if your account is not linked yet.

  3. 03

    Map the entry

    Choose the collection, then map each value from the previous module into the document. Make shows what it can read in your database once the connection exists.

  4. 04

    Add Send an Email

    Click the + again and add Send an Email. Map the values of the new document into the message, so the reader sees what just arrived.

  5. 05

    Test with Run once

    Click Run once and look at the bundles each module received (a bundle is one item passing from a module to the next). Check the new document in Restdb.io.

  6. 06

    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 one bundle counts as one operation on your plan.

Modules

What each Restdb.io module does

Restdb.io gives you 19 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Restdb.io1

Create a Document

Action

In Make“Creates a new document in a collection.”

Get a new record in your database without typing it: this module writes one document into the collection you choose, filled with data mapped from earlier modules.

When to use it
a web form, a shop or a CRM passes a new entry to the scenario and you want Restdb.io to keep it.
Watch out
every bundle that reaches this module creates one more document, so a search placed before it can multiply the records.
Restdb.io2

Create a Document in Subcollection

Action

In Make“Creates a new document in subcollection.”

Attach a child record to a parent document: the new entry goes into a subcollection, so an order line sits under its order or a comment under its ticket.

When to use it
the data belongs to an existing record rather than standing alone, a case Create a Document does not cover.
Watch out
the parent has to be there first, so fetch it with Get a Document or create it earlier in the same scenario.
Restdb.io3

Create a Media Object

Action

In Make“Creates a new media object.”

Store content coming from another app, such as an email attachment, as a new media object in your Restdb.io database, close to the records that use it.

When to use it
a form upload needs a home in the same database as the customer record it came with.
Watch out
the Free plan of Make handles files up to 5 MB, so keep heavy media in mind before switching the scenario on.
Restdb.io4

Delete a Document

Action

In Make“Deletes an existing document from collection.”

Keep the database free of dead records by removing one document you already know from its collection.

When to use it
a customer cancels in another tool and the matching Restdb.io entry should disappear as well.
Watch out
the scenario deletes whatever document it is pointed at, so test on a throwaway record with Run once before you activate it.
Restdb.io5

Delete a Document by Query

Action

In Make“Deletes an existing document by query.”

Remove a document by describing it with a query instead of naming it, which helps when you know one of its values but not the document itself.

When to use it
another app only gives you an email address or a reference, and Delete a Document would need a record you have not fetched.
Watch out
run the same query through List Collection Documents first, so you see what it points to.
Restdb.io6

Delete a Media Object

Action

In Make“Deletes an existing media object.”

Tidy your database by removing a media object you no longer need once the record it went with is gone.

When to use it
right after Delete a Document, to drop the attachment that belonged to that record.
Watch out
the module removes whatever media object it receives, so try it on a test object with Run once first.
Restdb.io7

Download a Media Object

Action

In Make“Downloads an existing media object.”

Pull the actual content of a media object out of Restdb.io, so another module can attach it to an email or store it in another tool.

When to use it
you need the media itself and not its description, which is the difference with Get a Media Object.
Watch out
the Free plan carries files up to 5 MB and 512 MB of transfer, so large media add up.
Restdb.io8

Get a Document

Action

In Make“Retrieves an existing document.”

Read one document in full when you already know which one you want, and hand its values to the rest of the scenario.

When to use it
before Update a Document, to look at the current values, or to build a message from a stored record.
Watch out
it retrieves a single document; to go through several, List Collection Documents is the module to pick.
Restdb.io9

Get a Media Object

Action

In Make“Retrieves an existing media object.”

See what a media object is before acting on it: the module retrieves its record, and later modules can map its details.

When to use it
you want to check or log a media object without transferring its content, which is the job of Download a Media Object.
Restdb.io10

Get Collection Metadata

Action

In Make“Retrieves metadata of an existing collection.”

Learn how Restdb.io describes one collection, which helps when a scenario has to adapt to the structure it writes into.

When to use it
you set up a new scenario and want to check a collection before mapping values into Create a Document.
Watch out
it reads metadata only and does not bring back the documents themselves.
Restdb.io11

Get Database Metadata

Action

In Make“Retrieves metadata of an existing database.”

Get the big picture of your whole Restdb.io database in one bundle, rather than looking collection by collection.

When to use it
you document a setup, review what exists, or check the database before a scenario starts writing to it.
Watch out
for a single collection, Get Collection Metadata gives a narrower answer.
Restdb.io12

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Call any part of the Restdb.io API from your scenario, with the same connection, when no listed module does what you need.

When to use it
the dedicated modules fall short for your case and you know which API request would solve it.
Watch out
this is the most technical module of the list, so try the dedicated ones before writing a request by hand.
Restdb.io13

Send an Email

Action

In Make“Sends an email.”

Tell someone what just happened by sending an email from the Restdb.io module itself, with no separate mail app in the flow.

When to use it
a new document was created and a sales rep, a manager or a customer should hear about it.
Watch out
each bundle that reaches it sends one email, so place it after a module that outputs a single bundle.
Restdb.io14

Update a Document

Action

In Make“Updates an existing document.”

Rewrite an existing document with fresh values, so the database reflects what just changed in another tool.

When to use it
a deal moves forward in your CRM and the matching Restdb.io record has to follow.
Watch out
when only one value changes, Update a Document Property is the narrower option and touches nothing else.
Restdb.io15

Update a Document Property

Action

In Make“Updates property of the existing document.”

Change a single property of a document, a status or a date for example, and leave everything else as it was.

When to use it
a ticket closes in your help desk and only its status in Restdb.io needs to move.
Watch out
you still need the right document, so find it first with List Collection Documents or Get a Document.
Restdb.io16

Get a Document from Subcollection

Search

In Make“Retrieves a document from a subcollection.”

Fetch one child document from a subcollection, the way you would open a single line under an order.

When to use it
the scenario already knows the parent document and needs one specific entry stored below it.
Watch out
to go through all the entries of that subcollection, List Subcollection Documents is the right module.
Restdb.io17

List Collection Documents

Search

In Make“Lists documents in existing collection.”

Browse the documents of a collection and pass them to the next modules one bundle at a time.

When to use it
a scheduled scenario reviews what is stored and acts on each record, such as a reminder sent with Send an Email.
Watch out
as a search, it can return zero, one or many documents, and each one costs operations in the modules that follow.
Restdb.io18

List Media Objects

Search

In Make“Lists media objects in database.”

Obtain the list of media objects stored in your database, each one handed on as its own bundle.

When to use it
you check what exists before a cleanup with Delete a Media Object or a copy with Download a Media Object.
Watch out
every media object returned runs the next modules once, which adds operations on your plan.
Restdb.io19

List Subcollection Documents

Search

In Make“Lists documents from subcollection.”

Walk through every document under a parent record, turning a subcollection into a series of bundles you can process.

When to use it
you want all the lines of an order, or all the notes on a client, to build a summary or an export.
Watch out
an empty subcollection returns nothing, so the modules after it do not run for that parent.
Need help

Need help automating Restdb.io with Make?

A person reads every message.

FAQ

Restdb.io and Make: common questions

01Is the Restdb.io Make integration free?
Yes, on the Make side. Restdb.io is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution, with usage counted in operations per month. Your Restdb.io subscription is separate: check its pricing page on their side.
02What is needed to connect Restdb.io to Make?
An active Restdb.io account and an API key. In your dashboard, open Databases and copy the database URL, then click Manage on that database, open the API tab and copy the full access API key. In Make, add any Restdb.io module, click Create a connection, optionally name it, and paste those credentials. The connection is then reused by every Restdb.io module in your scenarios, so you only do this once per database.
03Does Restdb.io have a trigger in Make?
No. All 19 modules are actions or searches, so Restdb.io cannot start a scenario by itself. You have two ways around it. Start the scenario with a trigger from another app, such as a form or a shop, and let the Restdb.io modules follow. Or begin with List Collection Documents and let the scenario run on its own schedule, every 15 minutes by default, down to 1 minute on a paid plan. In both cases the reaction depends on the first module, not on Restdb.io.
04What if a Restdb.io module is missing in Make?
Use Make an API Call. It calls any part of the Restdb.io API with the connection you already set up, so whatever the other modules skip can still be done in the same scenario. Try the dedicated modules first, since they are easier to fill. Also note that the Make documentation for this app is marked as AI-generated from the official Restdb.io documentation, so verify important details and contact Restdb.io directly for questions about their own product.
05Make or n8n for Restdb.io: which one fits?
It depends on the tool your team already runs. On Make, Restdb.io comes with 19 ready modules, a connection built on your API key, and Make an API Call for the rest, which covers most document and media work without code. The same app often exists as an n8n node too, so check what that node offers before choosing. Compare what each tool lists for Restdb.io and how your scenarios will start, since Restdb.io has no trigger in Make.
Same platform

Other docs you might need on this stack.

Browse all integrations