Resources · Make integration

QuintaDB Make integrationAutomate QuintaDB with Make.

Your QuintaDB tables can fill themselves and warn other tools the moment a record changes. The QuintaDB Make integration gives you 14 modules, including 1 instant trigger. This guide is for people who know QuintaDB and are opening Make for the first time, and it walks you from connection to a live scenario.

Try the QuintaDB integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the QuintaDB Make integration let you automate?

The QuintaDB Make integration links your QuintaDB account to Make so that records can be created, read, updated or removed without opening the database. You build a scenario, which is the automation itself: a chain of modules, each module being one brick such as a trigger, an action or a search.

A CRM table that stays current on its own. Leads collected in a form tool land in QuintaDB through Add a Record, and a later change in status is written back with Update a Record's Cell, so nobody retypes anything.

Other tools that hear about every change. Watch Records reacts when a record is added or modified in a form of your application, so a sales channel, a spreadsheet or an email tool can be told right away.

Clean lookups before writing. Search Records finds matching rows in a table or report, and you decide what happens next: update the one you found, or add a new record when nothing comes back.

If none of the 14 modules fits your need, Make an API Call reaches the rest of the QuintaDB API with the same connection. QuintaDB often has an n8n node too; the n8n vs Make comparison helps you choose. Before building, the Make review and the Make pricing page tell you what each plan covers.

Connect

How do you connect your QuintaDB account to Make?

  1. 01

    Grab your API key and domain

    In QuintaDB, click your profile icon or name in the top right corner, open Account Settings, then the API section. Copy the API key and the Domain shown there. You need an active QuintaDB account for this.

  2. 02

    Add a QuintaDB module in Make

    Inside your scenario, add any QuintaDB module and click Create a connection. A connection is your QuintaDB account linked to Make once, then reused by every QuintaDB module you add later.

  3. 03

    Paste the credentials and save

    Give the connection a name in Connection name if you like; the field is optional. Paste the API key and domain you copied, then confirm. Make can now read your applications, forms and records.

First scenario

Your first scenario: send new leads into a QuintaDB table

GoalWhen a lead arrives in another app, Make adds it as a new record in your QuintaDB table.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to place the first module. This first bubble is the app where your leads come from, a form tool for instance.

  2. 02

    Set up the source module

    Search that app by name, pick its module that watches new entries and link your account with Create a connection. Each lead it sends is a bundle: one item passed to the next module.

  3. 03

    Add Add a Record

    Click the + on the right, search QuintaDB and choose Add a Record. Connect your account, pick the application and form, then map the values from the previous module into the fields of your form.

  4. 04

    Test with Run once

    Click Run once and send a test lead. Each module shows the bundles it received; open the QuintaDB table and check that the new record is there with the right values.

  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 counts as an operation, the unit Make tracks on your plan.

Triggers

What can start a QuintaDB scenario?

1 module starts a scenario when something happens in QuintaDB. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by QuintaDB as soon as it happens.

QuintaDB1Watch Records

Watch Records

Instant trigger

In Make“Triggers when a record is added or modified in an application form.”

Watch Records starts your scenario as soon as someone creates or edits a record in one of your application forms, so the rest of your tools learn about it without anyone copying data by hand.

How it fires
instant: QuintaDB calls Make through a webhook as soon as it happens, which is what the lightning badge on the module means.
When to use it
a support table where a status change to closed should notify the customer or update a shared sheet.
Watch out
it reacts to edits as well as new records, so never write back to the same form with Update a Record in that scenario, or each update can wake the trigger again.
Modules

What can you do with QuintaDB in Make?

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

QuintaDB1

Add a Record

Action

In Make“Adds a new record.”

Add a Record creates a fresh row in the form you pick, filled with values mapped from earlier modules, so data from another tool lands in QuintaDB without retyping.

When to use it
a signup, an order or a ticket born elsewhere that must exist in your database.
Watch out
it adds every time; run Search Records first if duplicates are a risk.
QuintaDB2

Delete a Record

Action

In Make“Deletes a record.”

Delete a Record removes one record from your application, which keeps a table tidy when the source of that entry disappears elsewhere.

When to use it
a contact who unsubscribes or a cancelled order that should leave the list.
Watch out
a deletion is not something you roll back from Make, so test with Run once on a dummy record before switching the scenario on.
QuintaDB3

Get an Application

Action

In Make“Retrieves an application.”

Get an Application returns the details of one QuintaDB application, handy when a later module needs information about the database itself rather than about its rows.

When to use it
a scenario that works across several applications and has to confirm which one it is handling before going further.
QuintaDB4

Get a Record

Action

In Make“Retrieves a record.”

Get a Record fetches a single record when you already know which one you want, and passes all its values to the next module as one bundle.

When to use it
after Watch Records, to pull the complete entry before sending a summary to a colleague.
Watch out
it needs the record identified; when you only know a value like an email, Search Records is the right pick.
QuintaDB5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call”

Make an API Call lets you reach any endpoint of the QuintaDB API from your scenario, using the connection you already created, so nothing is out of reach even without a ready-made module.

When to use it
a task that none of the other QuintaDB modules covers.
Watch out
you write the request yourself, so keep the QuintaDB API documentation open while you set it up.
QuintaDB6

Update a Record

Action

In Make“Updates an existing record.”

Update a Record rewrites an existing entry with new values, keeping one row per customer or project instead of piling up copies.

When to use it
a deal that moves stage in your CRM, or an order whose delivery details change in the shop.
Watch out
pair it with Search Records to find the right row first; updating the wrong one silently overwrites good data.
QuintaDB7

Update a Record's Cell

Action

In Make“Updates the record's cell with the new value.”

Update a Record's Cell changes one single value in a record and leaves everything else untouched, the lightest way to flip a status or a date.

When to use it
marking an invoice as paid once the payment tool confirms it.
Watch out
if several values must change together, Update a Record does it in one module and saves operations.
QuintaDB8

List Applications

Search

In Make“Lists all applications for this account.”

List Applications gives you every application in the connected account, one bundle each, which is a quick way to check what Make can see.

When to use it
a report or backup scenario that has to loop over all your databases instead of a single one.
Watch out
as a search, it can return zero, one or many bundles, and each following module runs once per bundle.
QuintaDB9

List Fields in Form

Search

In Make“Lists all fields in the selected form.”

List Fields in Form tells you which fields a selected form contains, so a scenario can adapt to the structure of the form instead of assuming it.

When to use it
documenting a database for a new team member, or checking a form before mapping values into Add a Record.
QuintaDB10

List Forms in Application

Search

In Make“Lists all forms in the selected application.”

List Forms in Application returns all the forms of one application, a useful first step when your data lives across several forms such as clients, invoices and projects.

When to use it
a scenario that has to repeat the same action on every form of an application.
Watch out
each form comes out as its own bundle, so later modules run once per form.
QuintaDB11

List Records

Search

In Make“Retrieves the records from the table or report.”

List Records pulls the records of a table or a report into your scenario, which turns QuintaDB into a source for exports, digests or syncs with other tools.

When to use it
copying a filtered report into a spreadsheet for the finance team.
Watch out
every record is a bundle and every later module costs an operation per bundle, so point it at a report when you only need part of the table.
QuintaDB12

List Reports in Table

Search

In Make“Retrieves all reports in the selected table.”

List Reports in Table shows the saved reports of a chosen table, so you can see which filtered views already exist before reading data from one of them.

When to use it
picking the right report to feed List Records or Search Records when a table has many views built by colleagues.
QuintaDB13

Search Records

Search

In Make“Searches for records matching the chosen criteria in a selected table or report.”

Search Records finds the entries that match criteria you choose in a table or report, the safe step before any update or insert.

When to use it
checking whether an email already exists before Add a Record creates a duplicate.
Watch out
the result can be empty, so add a filter after it to decide what happens when nothing matches.
Need help

Need help automating QuintaDB with Make?

A person reads every message.

FAQ

Common questions about QuintaDB and Make

01Is the QuintaDB Make integration free?
Yes, on the Make side. QuintaDB is a standard app, so it works on the Make Free plan along with 3,000+ other standard apps. The Free plan allows 2 active scenarios, a minimum interval 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 bring a 1 minute interval, unlimited active scenarios and 40 minutes of execution. Usage is counted in operations per month. You still need an active QuintaDB account with API access, and its subscription is set on the QuintaDB side.
02What do you need to connect QuintaDB to Make?
An active QuintaDB account and its REST API key. In QuintaDB, open Account Settings from your profile icon, go to the API section, and copy both the API key and the Domain shown there. In Make, add any QuintaDB module, click Create a connection, optionally name it, and paste those two values. If the module you start with is Watch Records, which is instant, click Create a webhook first and then Create a connection. One connection serves every QuintaDB module in your scenarios.
03Does the QuintaDB trigger in Make react in real time?
Yes. Watch Records is an instant trigger: QuintaDB calls Make through a webhook as soon as a record is added or modified in an application form, so the scenario does not wait for a schedule. It is the only trigger of the app. If you would rather process records in batches, start the scenario with the scheduler instead and use List Records or Search Records as the first QuintaDB step; a new scenario runs every 15 minutes by default, and the Free plan cannot go below that.
04What if a QuintaDB module is missing in Make?
Use Make an API Call. It calls any endpoint of the QuintaDB API with the connection you already set up, so you can cover actions that the other modules do not offer. The official doc lists no specific limits for this app, but it does warn that its QuintaDB section is AI-generated and may contain mistakes, so check important details against the QuintaDB documentation or ask QuintaDB directly before relying on a behavior.
05Should you use Make or n8n for QuintaDB?
It depends on the tool your team already works in. On Make, QuintaDB offers 14 ready modules, including an instant trigger, plus Make an API Call for the rest, and it runs on the Free plan. QuintaDB often has an n8n node as well, so the choice rarely comes down to whether the app is supported. Compare how each tool fits your existing automations and how your team likes to build, and pick the one you will actually maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations