Resources · Make integration

Tadabase Make integrationAutomate Tadabase with Make.

Your Tadabase records can feed the rest of your stack on their own. The Tadabase Make integration gives you 9 modules: 2 triggers, 6 actions and 1 search. This guide walks you through the connection, a first working scenario and every module, one by one.

Try the Tadabase integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Tadabase Make integration automate?

The Tadabase Make integration links your Tadabase account to Make, a visual tool where you chain apps together without writing code. Each automation is called a scenario: a chain of modules, and each module is one brick, like a trigger that starts things or an action that writes a record.

Orders that land as records. A web shop receives an order, and Make passes it to Create a Record, so your Tadabase app holds the order without anyone retyping it. Pair it with Search Records first when the same customer might already exist.

Changes that reach your other tools. The instant Watch Records tells Make when a record is created, updated or deleted, so a sales team can see a status change in their chat or CRM a moment later.

Documents filed on the right record. A signed contract comes out of an e-signature app, and Upload a File attaches it to the record by its ID. No more hunting for the PDF in an inbox.

Know the edges before you build. The scheduled Watch Records only sees new records, and the instant one needs a Tadabase PRO plan or above. For anything the listed modules skip, Make an API Call reaches the rest of the Tadabase API with the same connection. Deciding between tools? Read n8n vs Make, and if you want a structured path into the editor, the Make training starts from zero. When a run fails, Make troubleshooting covers the usual causes.

Connect

How do you connect Tadabase to Make?

  1. 01

    Generate your API key in Tadabase

    In Tadabase, open the Settings menu in the left sidebar, pick API Keys, then click Generate New API Key. Keep the page open: you will need the Client ID, the API key and the Client secret it shows.

  2. 02

    Open the connection window in Make

    Add any Tadabase module to your scenario and click Create a connection. A connection is your Tadabase account linked to Make once, then reused by every Tadabase module. The Connection name field is optional, but a clear name helps when you run several apps.

  3. 03

    Paste the three credentials

    Copy the Client ID, the API key and the Client secret from Tadabase into the matching fields, or follow the instructions Make shows on screen. Save, and Make can now list what it reads in your Tadabase account.

First scenario

Your first scenario with Tadabase and Make

GoalWhen another app sends new data, Make finds the matching Tadabase record and updates it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app that holds the new data first, a form tool or a payment app for example, and set up its trigger.

  2. 02

    Add Search Records

    Click the + on the right of that first module, search for Tadabase and choose Search Records. Click Create a connection if you have not linked your account yet, then set the conditions that identify the right record.

  3. 03

    Add Update a Record

    Add Update a Record after the search. Map the record ID from Search Records, then map the values coming from the first app into the fields Make lists for your Tadabase data.

  4. 04

    Test with Run once

    Click Run once, send one test item from the first app, and open each module to read the bundles it received. A bundle is one item passing from module to module, here one record.

  5. 05

    Schedule and switch it on

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

Triggers

Which Tadabase triggers can start a scenario?

2 modules start a scenario when something happens in Tadabase. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Tadabase as soon as it happens.

Tadabase1Watch Records

Watch Records

Scheduled trigger

In Make“Triggers when records are created.”

This version of Watch Records picks up every record created in Tadabase since its last check and sends each one to the next module as a bundle. It covers new records only, which keeps it easy to reason about.

How it fires
scheduled. Make checks Tadabase on the scenario's schedule, no more often than every 15 minutes on the Free plan, and down to every minute on paid plans.
When to use it
a new lead or a new request only needs to reach another tool, and a short wait is fine.
Watch out
edits and deletions never reach this trigger; switch to the instant Watch Records for those.
Tadabase2Watch Records

Watch Records

Instant trigger

In Make“Triggers when records are created, updated or deleted. Only available for Tadabase PRO plan or above.”

The instant Watch Records reacts to three events on your records: a creation, an update and a deletion. Your scenario starts on the change itself, with no waiting for the next scheduled check.

How it fires
instant. Tadabase calls Make through a webhook as soon as the record changes, which the lightning badge marks in the editor.
When to use it
a status moves to approved and the sales team should hear about it in their other tools right away.
Watch out
it requires a Tadabase PRO plan or above, and you click Create a webhook before creating the connection.
Modules

What can the Tadabase modules do in Make?

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

Tadabase1

Create a Record

Action

In Make“Saves a new record.”

Create a Record saves a brand new entry in your Tadabase app. You fill it with values mapped from the modules that come before it, so nobody retypes anything.

When to use it
an order, a sign-up or a support request arrives in another app and must live in Tadabase from now on.
Watch out
it never checks for duplicates, so put Search Records before it when the item may already exist.
Tadabase2

Delete a Record

Action

In Make“Deletes a record.”

With Delete a Record, Make removes one Tadabase record for you, identified by the ID you map from a previous module.

When to use it
a customer cancels in your billing tool and the matching entry should disappear from Tadabase too.
Watch out
a deletion cannot be undone from Make, so test on a throwaway record with Run once first.
Tadabase3

Get a Record

Action

In Make“Gets a record.”

Get a Record fetches the full content of one record when you already hold its ID, and hands every value to the following modules.

When to use it
a trigger gave you only an ID, and the next step needs the complete record to write an email or a document.
Watch out
no ID, no result; when you only know a name or an email, Search Records is the module to pick.
Tadabase4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call gives you access to any endpoint of the Tadabase API, using the connection you already set up, for the jobs the ready-made modules do not cover.

When to use it
you need a Tadabase feature that none of the other eight modules offers.
Watch out
you write the request yourself, so keep the Tadabase API reference open while you fill it.
Tadabase5

Update a Record

Action

In Make“Updates an existing record.”

Update a Record changes the values of a record that already exists in Tadabase, instead of creating a second copy next to it.

When to use it
a payment clears or a ticket closes elsewhere, and the related Tadabase record should reflect the new status.
Watch out
it needs the record ID; get it from Search Records or from a trigger bundle before this step.
Tadabase6

Upload a File

Action

In Make“Uploads a file to a record by the record ID.”

Upload a File attaches a file to a Tadabase record, located by its record ID, so the document sits right next to the data it belongs to.

When to use it
a signed quote, a photo from the field or an invoice PDF comes out of another app and belongs on a customer record.
Watch out
on the Make Free plan, files above 5 MB will not go through.
Tadabase7

Search Records

Search

In Make“Filters and sorts records based on conditions.”

Search Records filters and sorts your Tadabase records on the conditions you set, then returns whatever matches as separate bundles.

When to use it
you know an email or a reference number but not the record ID, and you must find the entry before updating it.
Watch out
it can return zero, one or several bundles, and every following module then runs once per bundle.
Need help

Need help automating Tadabase with Make?

A person reads every message.

FAQ

Tadabase and Make: common questions

01Is the Tadabase Make integration free?
Yes, on the Make side. Tadabase is a standard app, available from the Make 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. On the Tadabase side, your account needs API access, which depends on your Tadabase plan, and the instant Watch Records trigger requires the PRO plan or above. Paid Make plans lower the interval to 1 minute and remove the cap on active scenarios.
02What do you need to connect Tadabase to Make?
You need an active Tadabase account whose plan includes API access, plus a Make account. In Tadabase, go to Settings, then API Keys, and click Generate New API Key. Copy the Client ID, the API key and the Client secret. In Make, add a Tadabase module, click Create a connection, give it a name if you like, and paste the three values. For the instant trigger, click Create a webhook before creating the connection. The connection is then reused by every Tadabase module in your scenarios.
03Does the Tadabase trigger in Make react in real time?
It depends on which Watch Records you pick, since Tadabase has two. The instant version reacts as soon as a record is created, updated or deleted, because Tadabase calls Make through a webhook; it needs a Tadabase PRO plan or above. The scheduled version only sees new records, and Make checks for them on the scenario's schedule: every 15 minutes by default, 15 minutes at least on the Free plan and down to 1 minute on paid plans. Choose it when a short wait does not matter.
04What if a Tadabase module is missing in Make?
Use Make an API Call. The Tadabase app in Make includes this module, and it reaches any endpoint of the Tadabase API with the same connection as the other modules. That covers what the 8 ready-made modules leave out. You write the request yourself, so the Tadabase API reference helps here. Before going that way, check whether Search Records combined with Get a Record or Update a Record already does the job, because the ready-made modules are easier to map and to maintain.
05Should you use Make or n8n with Tadabase?
It depends on the tool your team already runs. On Make, Tadabase comes with 9 modules, including an instant trigger and Make an API Call for anything else, and every step is built visually in the scenario editor. On n8n, check first whether a Tadabase node exists and which operations it offers. Compare the two on the modules you actually need for your process, the tool your colleagues know, and how each one fits the rest of your stack, rather than on reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations