Resources · Make integration

Hubhus Make integrationAutomate Hubhus with Make.

Tired of copying leads into Hubhus by hand? The Hubhus Make integration gives you 5 modules: 4 actions and 1 search, all built around leads. This page is for teams new to Make, and it walks you from connecting your account to a working first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Hubhus Make integration do for you?

The Hubhus Make integration lets a Make scenario, meaning the automation you build as a chain of modules, read and write leads in your Hubhus account. Each module is one brick of that chain. Here every brick works on leads: you can create them, look them up, change them or remove them, with no code at all.

Leads that file themselves. When a prospect fills in a form on your website, another app starts the scenario and Create a Lead writes the contact into Hubhus. Nobody retypes a name or a phone number.

Records that stay current. A status changes in your quoting tool or your spreadsheet: List/Search Leads finds the matching lead, then Update a Lead writes the new value on it. Get a Lead is the one to pick when you already know exactly which lead you want.

A cleaner pipeline. Delete a Lead removes test entries or leads your team has closed out, once a filter in Make has confirmed they really should go.

Know the limits before you start. Hubhus has no trigger in Make, so something else must start the scenario, and Make's own documentation for the app is thin. The same app often has an n8n node too; our n8n vs Make comparison helps you pick a tool, and the Make training covers the editor from scratch. If a scenario misbehaves, see Make troubleshooting.

Connect

How do you connect your Hubhus account to Make?

  1. 01

    Add a Hubhus module

    Open a scenario, click the + and search for Hubhus. Pick any of its modules, for example Create a Lead, then click Create a connection. A connection is your Hubhus account linked to Make once and reused by every Hubhus module.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it pays off later. If you manage several Hubhus accounts, or a colleague opens your scenario, a clear name tells everyone which account the modules are writing to.

  3. 03

    Authorize and save

    Depending on what Hubhus asks for, either approve Make on the Hubhus page that opens or paste the key Hubhus gives you. Then click Save. Make can now read and write leads in that account.

First scenario

Build your first scenario with Hubhus

GoalWhen a new entry arrives in your form tool, Make creates the matching lead in Hubhus.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since Hubhus has no trigger, this first module comes from the app that collects your prospects, such as your form tool.

  2. 02

    Add Create a Lead

    Click the + on the right of that first module, search for Hubhus and choose Create a Lead. Select your connection, or click Create a connection if this is your first Hubhus module.

  3. 03

    Map the form data

    Fill the lead fields by mapping values from the first module: click a field, then pick the matching item from the form entry. Each entry is a bundle, one item passed from a module to the next.

  4. 04

    Test with Run once

    Click Run once, then send a test entry through your form. Open the bubbles to read the bundles each module received, and check in Hubhus that the lead looks the way you want.

  5. 05

    Schedule and switch on

    Set the schedule on the first module; a new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Then switch the scenario on so it keeps running without you.

Modules

What each Hubhus module does

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

Hubhus1

Create a Lead

ActionIn the docs only

Adds a fresh lead to Hubhus from data another app hands over, so new prospects appear without anyone typing them in.

When to use it
right after a form, a chat or a booking tool captures a new contact.
Watch out
the module creates a lead every time it runs, so put List/Search Leads in front of it if the same person might come in twice.
Hubhus2

Delete a Lead

ActionIn the docs only

Removes one lead from Hubhus, which keeps your list free of test records and dead entries.

When to use it
after a filter in Make has confirmed that a lead is a test or a duplicate you no longer want.
Watch out
treat every deletion as final, since the docs say nothing about restoring a lead, so run the scenario with Run once on a harmless record before you switch it on.
Hubhus3

Get a Lead

ActionIn the docs only

Fetches a single lead you already know, and hands its details to the next modules in your scenario.

When to use it
an earlier module has already pointed to the exact lead and you only need its current details.
Watch out
this module reads one lead it can identify; when you are not sure which lead matches, reach for List/Search Leads first.
Hubhus4

List/Search Leads

SearchIn the docs only

Looks through your Hubhus leads and returns every match it finds, which lets a scenario check what already exists before acting.

When to use it
before creating or updating a lead, to see whether that prospect is already in Hubhus.
Watch out
a search can return zero, one or many bundles, and each bundle runs the following modules once, which counts operations on your plan.
Hubhus5

Update a Lead

ActionIn the docs only

Changes the details of a lead that already exists in Hubhus, so your records follow what happens in your other tools.

When to use it
a prospect's status or contact details change somewhere else and Hubhus should reflect it.
Watch out
the module needs to know which lead to edit, so pair it with List/Search Leads or Get a Lead placed just before it.
Need help

Need help automating Hubhus with Make?

A person reads every message.

FAQ

Hubhus and Make: common questions

01Is the Hubhus Make integration free?
Yes. Hubhus is a standard app in Make, so you can use it on the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data 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. Usage is counted in operations, one per module run on one bundle. Any Hubhus subscription is a separate matter between you and Hubhus.
02What do you need to connect Hubhus to Make?
A Hubhus account and a Make account. Make's documentation lists no prerequisites and gives no Hubhus-specific steps, so the generic Make flow applies: add a Hubhus module, click Create a connection, optionally name it, authorize Make on the Hubhus page or paste the key Hubhus provides, then click Save. That connection is reused by all 5 Hubhus modules. If the window asks for a key and you cannot find one, Hubhus support is the right place to ask.
03Can Hubhus start a Make scenario in real time?
No. Hubhus has no trigger module in Make, neither scheduled nor instant, so it cannot start a scenario on its own. You have two ways around that. Start the scenario with a trigger from another app, such as the form or booking tool where prospects arrive, and let the Hubhus modules act on the leads. Or start it from Make's own schedule, which runs every 15 minutes by default, with List/Search Leads as the first module to pick up your leads.
04What if the Hubhus module you need is missing in Make?
It depends on what you need. The integration offers 5 modules, all about leads, and it does not include a Make an API Call module, so this page cannot promise anything beyond those lead modules. Make's own documentation for the app is limited as well. For needs beyond leads, check whether another app in your stack covers the step, or ask our team to look at your case and suggest a workable route.
05Should you use Make or n8n with Hubhus?
It depends on the tool you already work in. The same app often has an n8n node, so check both catalogs before deciding. On the Make side, Hubhus comes with 5 lead modules and no trigger, so the scenario always starts from another app or from a schedule. If your team already builds scenarios in Make, staying there keeps everything in one place. The comparison page linked above lays out the criteria side by side without picking a winner for you.