Resources · Make integration

Dubb Make integrationAutomate Dubb with Make.

Tired of copying the same contact into Dubb by hand? The Dubb Make integration gives you 6 modules, all built around your Dubb contacts. This guide is for anyone new to Make: link your account, then build a first scenario that fills Dubb for you.

Try the Dubb integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Dubb Make integration do for you?

The Dubb Make integration lets Make read and edit the contacts stored in your Dubb account. You build a scenario, which is the automation itself: a chain of modules, each one a small brick that does one job. Here every Dubb brick handles contacts, so the scenario keeps your list in step with your other tools.

A contact list that fills itself. Put Create a Contact after any app that collects people, like a signup form or a booking tool. Each new person becomes a Dubb contact, with no copy and paste. The 123FormBuilder Make integration is one way to feed it.

Records that stay current. When someone changes their details somewhere else, Update a Contact rewrites the matching Dubb record. It needs the contact's Id, so a Get a Contact or List Contacts step often comes first.

Clean exits. Delete a Contact removes a person as soon as your process says so, for instance after an unsubscribe logged in another app.

Know the limits before you start. Make's own documentation for Dubb is marked as limited, because little public information about the app exists. That means no triggers: Dubb cannot start a scenario by itself, so another app or a schedule has to. When a listed module falls short, Make an API Call reaches the rest of Dubb's API with the same connection.

Weighing tools? The n8n vs Make comparison lays out the criteria, and our Make review shows how the editor feels day to day.

Connect

How do you connect your Dubb account to Make?

  1. 01

    Open a Dubb module

    In your scenario, click the + and type Dubb in the search box. Pick any module, for example Get a Contact. Make then asks for a connection, which is simply your Dubb account linked to Make once. Click Create a connection.

  2. 02

    Name the connection

    Give it a name you will recognize later, such as the team or the account it belongs to. This step is optional, but it helps when several people share one Make organization and each links a separate Dubb login.

  3. 03

    Authorize Make and save

    Depending on what Dubb asks for, either approve Make on the Dubb page that opens or paste the key Dubb gives you. Then click Save. Every other Dubb module in your scenarios reuses this same connection.

First scenario

Build your first scenario with Dubb

GoalWhen a new entry lands in another app, Make creates the matching contact in Dubb.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the canvas. Since Dubb has no trigger, the first module comes from the app where your contacts appear.

  2. 02

    Pick the starting app

    Search for that app, choose the module that watches new entries, and link your account. Each entry it finds will travel through the scenario as a bundle, which is one item, here one person.

  3. 03

    Add Create a Contact

    Click the + on the right of the first module, search Dubb and choose Create a Contact. Use the Dubb connection you made earlier, or click Create a connection now.

  4. 04

    Map the fields

    Fill each Dubb field by clicking into it and picking the matching value that the first module received. No need to type anything by hand.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Open Dubb and check that the new contact is there.

  6. 06

    Schedule and switch 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 counts as one operation on your Make plan.

Modules

What each Dubb module does

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

Dubb1

Create a Contact

Action

In Make“Creates a new contact.”

Adds a new person to your Dubb contacts using the values you map from earlier modules. You get a record ready to use in Dubb without opening the app.

When to use it
right after a form, a booking or a CRM step that captures someone new.
Watch out
the module creates a contact on every run, so filter out people who already exist or you will see duplicates.
Dubb2

Delete a Contact

Action

In Make“Deletes an existing contact by Id.”

Removes one existing Dubb contact, picked by its Id. Your list loses the people your process no longer needs, and nobody has to hunt for them by hand.

When to use it
when another app records an opt-out or a closed account.
Watch out
treat every deletion as final, so test it on a dummy contact with Run once before switching the scenario on.
Dubb3

Get a Contact

Action

In Make“Retrieves a contact.”

Fetches a single Dubb contact so later modules can reuse its details. Think of it as looking someone up before you act on them.

When to use it
you already hold the contact's Id and want the full record, for example to copy it into a spreadsheet or a message.
Watch out
it returns one contact only; to browse several people, reach for List Contacts instead.
Dubb4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends your own request to Dubb's API while reusing the connection you already set up. It opens every part of Dubb that the five contact modules leave out.

When to use it
a task you need is not in the module list and Dubb's API offers it.
Watch out
Make's documentation for Dubb is limited, so you will need Dubb's own API reference to know which address and body to send.
Dubb5

Update a Contact

Action

In Make“Updates an existing contact by Id.”

Changes the details of a contact that already lives in Dubb, targeted by its Id. The record stays in sync with what your other tools know about that person.

When to use it
someone edits their email or company in your CRM and Dubb should follow.
Watch out
without the right Id nothing matches, so map it from an earlier bundle, such as one coming out of List Contacts.
Dubb6

List Contacts

Search

In Make“Lists all contacts.”

Pulls your Dubb contacts into the scenario, one bundle per person. It is the search module of this app, so it can return none, one or many results.

When to use it
you want to check, export or clean up your whole contact base in one pass.
Watch out
every module placed after it runs once per contact, and each run counts as an operation on your plan.
Need help

Need help automating Dubb with Make?

A person reads every message.

FAQ

Questions people ask about Dubb and Make

01Is the Dubb Make integration free?
Yes, Dubb is a standard app, so it works on the Make Free plan. That plan has limits worth knowing: 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 lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations: one module run on one bundle is one operation. What Dubb itself charges is outside the scope of this page.
02What do you need to connect Dubb to Make?
A Dubb account and a Make account. Make's documentation lists no special prerequisite for Dubb. You add any Dubb module, click Create a connection, give it a name if you like, then authorize Make on the Dubb page or paste the key Dubb provides. Click Save and every Dubb module reuses that connection. Because the documentation is marked as limited, if something blocks, check that you are logged into the right Dubb account and try again.
03Can Dubb start a Make scenario in real time?
No. The integration has no trigger, so Dubb cannot start a scenario on its own. You have two ways around it. Start the scenario with a module from another app, such as a form or CRM that notices new entries, then add the Dubb modules after it. Or begin with List Contacts and let Make run the scenario on its schedule, every 15 minutes by default. Either way, the Dubb modules act when the scenario runs, not the instant something changes in Dubb.
04What if a Dubb module you need is missing in Make?
Use Make an API Call. It sends any request to Dubb's API through the same connection, so you can reach features that the five contact modules do not cover. The catch is documentation: Make says its guide for Dubb is limited because little public information exists, so you will need Dubb's own API reference to build the request. If that is not enough, handle the step in another app that stores the same data and connect it to your scenario.
05Should you use Make or n8n for Dubb?
It depends on the tool you already run. On Make, Dubb comes with 6 modules centered on contacts, plus Make an API Call for the rest, and it works on the Free plan. Many apps also have an n8n node, so check whether n8n offers one for Dubb before deciding. Compare the two on what matters to your case: the modules available for Dubb, how you like to build, and which platform already runs your other automations. The comparison page on this site lays out those criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations