Resources · Make integration

Zite DB Make integrationAutomate Zite DB with Make.

Can your Zite DB records fill and update themselves while you work elsewhere? The Zite DB Make integration gives you 5 action modules to create, read, update and delete records. This page shows how to link your account, build a first scenario and pick the right module.

Try the Zite DB integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Zite DB Make integration do?

The Zite DB Make integration lets a scenario, the automation you build in Make, write to and read from your Zite DB records without code. Each step is a module, one brick of the scenario, and Zite DB offers 5 of them, all actions. Something else starts the scenario: a trigger from another app or a schedule you set in Make.

New entries land in Zite DB on their own. Put a trigger from your form tool or CRM first, then Create a record, and every submission becomes a record without anyone copying it by hand.

Records stay in sync with what changes elsewhere. When a status moves in another tool, Update a record writes the new value into Zite DB. Pair it with Get a record when a later step needs the full record before acting.

Old entries get cleaned out. Delete a record removes a record once another app says it is no longer needed, for example a cancelled order.

Zite DB has no trigger in Make, so it cannot start a scenario by itself. When the four record modules are not enough, Make an API call reaches the rest of the Zite DB API with the same connection. If you are weighing tools, the n8n vs Make comparison lays out the criteria, the Make pricing page covers plans, and the Make training helps you go further.

Connect

How do you connect Zite DB to Make?

  1. 01

    Copy your Zite DB API key

    You need an active Zite DB account. In Zite DB, open Settings, click the Developer tab and copy the API key shown on the screen. Keep it at hand for the next step.

  2. 02

    Add a Zite DB module

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

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you manage several accounts. Paste the API key you copied, or follow the on-screen instructions, and save the connection.

First scenario

Your first scenario with Zite DB

GoalWhen a new entry arrives in another app, Make creates a matching record in Zite DB.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Zite DB has no trigger, this first module comes from the app where your entries start.

  2. 02

    Set up the starting app

    Search that app by name, pick its trigger and create its connection. This module hands over one bundle per new entry, a bundle being one item passing from a module to the next.

  3. 03

    Add Create a record

    Click the + on the right of the first module, search Zite DB and pick Create a record. Choose your Zite DB connection, then map the incoming data into the record fields Make shows you.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open each module to read the bundles it received, then check in Zite DB that the new record 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. From now on each new entry becomes a Zite DB record without you stepping in.

Modules

What the Zite DB modules can do

Zite DB gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Zite DB1

Create a record

ActionIn the docs only

Create a record adds a fresh entry to Zite DB from data another module passes along, so nobody has to type it twice.

When to use it
a form submission, a new deal or a signup should appear in Zite DB as its own record.
Watch out
if the source app can resend the same entry, you may end up with duplicates, so test with Run once before switching on.
Zite DB2

Delete a record

ActionIn the docs only

Delete a record removes one record from Zite DB when another part of your process says it no longer belongs there, which keeps your data free of dead entries.

When to use it
an order is cancelled or a contact asks to be removed, and the matching record should go too.
Watch out
point it at a test record first with Run once, because a wrong mapping deletes the wrong entry.
Zite DB3

Get a record

ActionIn the docs only

Get a record reads one existing record from Zite DB and hands its contents to the next modules, so later steps can use values you already stored.

When to use it
before sending an email or updating another tool, you need details that only Zite DB holds.
Watch out
it returns a single record, the one you point it to, so it does not browse or list your data.
Zite DB4

Make an API call

ActionIn the docs only

Make an API call lets you reach any endpoint of the Zite DB API from your scenario, reusing the connection you already created, for anything the four record modules do not cover.

When to use it
you need a Zite DB action that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Zite DB API documentation open while you set it up.
Zite DB5

Update a record

ActionIn the docs only

Update a record changes an existing Zite DB record with new values from earlier modules, so your data follows what happens in your other tools instead of going stale.

When to use it
a deal changes stage, a payment clears or a ticket closes, and the record should say so.
Watch out
map only the fields you want to change, and check the result after Run once so no value gets wiped by mistake.
Need help

Need help automating Zite DB with Make?

A person reads every message.

FAQ

Zite DB and Make: common questions

01Is the Zite DB Make integration free?
Yes, on the Make side. Zite DB is a standard app, available from the 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. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits, meaning operations, per month. You still need an active Zite DB account, whose own subscription terms are listed on the Zite DB pricing page.
02What do you need to connect Zite DB to Make?
An active Zite DB account and its API key. In Zite DB, go to Settings, open the Developer tab and copy the key shown there. Then add any Zite DB module in Make, click Create a connection, give it a name if you like and paste the key. The connection is saved once and every Zite DB module in your scenarios can reuse it, so you do not repeat this step for each new module.
03Can the Zite DB Make integration react in real time?
Not by itself. Zite DB has no trigger module in Make, so it cannot start a scenario when something changes in your data. Two options remain. You can open the scenario with a trigger from another app, such as your form or CRM, and let Zite DB modules act after it. Or you can run the scenario on a schedule set on its first module, every 15 minutes by default, down to 1 minute on paid plans and 15 minutes on the Free plan.
04What if a Zite DB module you need is missing in Make?
Use Make an API call. It reaches any endpoint of the Zite DB API with the same connection, which covers what Create, Get, Update and Delete a record do not. You write the request yourself, so the Zite DB API documentation is your guide. Also note that Make labels its Zite DB documentation as AI-generated from the official Zite DB docs, so verify important details and contact Zite DB directly when something looks off.
05Should you use Make or n8n for Zite DB?
It depends on what you check first. Make offers 5 Zite DB modules covering the full record cycle, plus Make an API call for the rest of the API. Apps listed in Make often have an n8n node too, so look at whether one exists for Zite DB and what it covers before choosing. Compare the modules each tool offers for your use case and the tool your team already runs. The n8n vs Make comparison linked above sets out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations