Resources · Make integration

Hubflo Make integrationAutomate Hubflo with Make.

Can Make run your Hubflo client portal for you? The Hubflo Make integration gives you 34 modules: 9 triggers, 20 actions and 5 searches. This guide is for agencies and service teams that live in Hubflo, and it walks you from the API key to a first working scenario.

Try the Hubflo integration on MakeSee the 34 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Hubflo Make integration let you automate?

The Hubflo Make integration links your Hubflo account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick that watches, creates, updates or searches something. Hubflo brings companies, contacts, projects, tasks, forms and client workspaces into those scenarios.

A workspace ready the moment a client signs. Watch new companies spots the new account, Create workspace opens its space, and Invite contact to workspace brings the client in. Nobody copies names by hand.

Forms that turn into work. When a client finishes a questionnaire, Watch completed forms picks it up at the next check and Create task gives your team the follow-up, with the answers mapped into it.

Files that reach the right people. Watch uploaded files notices what a client drops in Hubflo, so another app can alert the account manager or archive a copy.

Two limits to know. All 9 triggers are scheduled, so Make checks Hubflo on the scenario's clock rather than hearing from it instantly. And the Make doc for Hubflo lists its modules without describing them, while flagging itself as AI-generated content that may contain mistakes: open each module in the editor and check its fields before you rely on it.

Hubflo may also exist as an n8n node; the n8n vs Make comparison lays out how the two tools differ. For a wider look at the platform, read the Make review, or follow the Make training to build faster.

Connect

How do you connect Hubflo to Make?

  1. 01

    Copy your Hubflo API key

    In Hubflo, open Settings, go to the API section and copy the key shown on screen. You need an active Hubflo account for this, and the key is what lets Make act on your behalf.

  2. 02

    Add a Hubflo module in Make

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

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name (optional, but handy with several accounts), paste the API key, then follow the on-screen instructions to finish. Make can now read your Hubflo data.

First scenario

Your first scenario: a workspace for every new company

GoalWhen a new company appears in Hubflo, Make creates a workspace for it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. Search for Hubflo and pick Watch new companies.

  2. 02

    Link your account

    Click Create a connection, paste the API key copied from Hubflo and save. Once the connection exists, Make lists what it can read in the module fields.

  3. 03

    Add Create workspace

    Click the + on the right of the trigger, search Hubflo again and choose Create workspace. Map the company data from the first module into the fields Make displays.

  4. 04

    Test with Run once

    Add a test company in Hubflo, then click Run once. Open the bubble above each module to read the bundles it received: one bundle is one item, here one company.

  5. 05

    Schedule and switch on

    Click the clock on the first module. A new scenario checks every 15 minutes by default; adjust if your plan allows, then turn the scenario on so it keeps running without you.

Triggers

What can start a Hubflo scenario?

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

Hubflo1Watch completed forms

Watch completed forms

triggerIn the docs only

Each Hubflo form a client finishes reaches your scenario at its next check, and each completed form arrives as a bundle ready to map into the next module. That turns an onboarding questionnaire into work for the team instead of an email to forward.

How it fires
scheduled. Make checks Hubflo on the scenario's schedule, so a form finished just after a check waits for the next one.
When to use it
after Send form to client, to collect the answers and create a task or update the contact.
Hubflo2Watch completed tasks

Watch completed tasks

triggerIn the docs only

Closing a task in Hubflo can now move something else forward: this trigger hands each completed task to your scenario so the next step happens without a reminder. Think of it as the handoff between two people or two phases.

How it fires
scheduled. Make checks Hubflo on the scenario's schedule and picks up the tasks completed since the last check.
When to use it
a finished review task should notify the client, open the next task or update the project.
Hubflo3Watch new companies

Watch new companies

triggerIn the docs only

Every company added to Hubflo becomes the starting point of a scenario, which is the cleanest way to launch client onboarding. The company arrives as a bundle, and later modules reuse its data without retyping.

How it fires
scheduled. Make checks Hubflo on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
a signed client should get a workspace, a first project or a record in your CRM right away. It is the trigger used in the first scenario above.
Hubflo4Watch new contacts

Watch new contacts

triggerIn the docs only

People are what this trigger follows: each contact created in Hubflo reaches your scenario, so your other tools learn about them without a manual export. Handy when several people on the client side need access or updates.

How it fires
scheduled. Make checks Hubflo on the scenario's schedule and passes along the contacts added since the previous check.
When to use it
a new contact should land in your newsletter tool or CRM, or receive an invitation to the right workspace.
Hubflo5Watch new folders

Watch new folders

triggerIn the docs only

A new folder in Hubflo often means a new stream of documents is about to begin, and this trigger lets your scenario react to it. Each folder comes through as its own bundle.

How it fires
scheduled. Make checks Hubflo on the scenario's schedule rather than getting a signal from Hubflo, so expect a gap between creation and reaction.
When to use it
mirror the folder structure in a storage app, or tell the team a new space for deliverables is open.
Hubflo6Watch new tasks

Watch new tasks

triggerIn the docs only

Fresh tasks get noticed here, whether the team or an automation created them in Hubflo. The scenario receives each one as a bundle, so you can route it to wherever people actually look.

How it fires
scheduled. Make checks Hubflo on the scenario's schedule and collects every new task since the last pass.
When to use it
post new tasks in a chat channel or add them to a calendar. Watch out: if the same scenario also runs Create task, it will pick up its own tasks and can start again on them.
Hubflo7Watch updated company

Watch updated company

triggerIn the docs only

Edits count too: when a company record changes in Hubflo, this trigger sends the updated version to your scenario. That keeps other systems aligned with what your team corrected in Hubflo.

How it fires
scheduled. Make checks Hubflo on the scenario's schedule and returns the companies changed since the previous check.
When to use it
sync company changes to your CRM or billing tool. Watch out: pairing it with Update company in the same scenario can trigger itself again, so update another app, not Hubflo.
Hubflo8Watch updated project stages

Watch updated project stages

triggerIn the docs only

Project progress becomes a signal: when a project moves to another stage in Hubflo, your scenario hears about it and can act on the new stage. It is the natural hook for client updates.

How it fires
scheduled. Make checks Hubflo on the scenario's schedule, so a stage change shows up at the next check, not the second it happens.
When to use it
send a message to the client when their project reaches delivery, or open the tasks of the next phase.
Hubflo9Watch uploaded files

Watch uploaded files

triggerIn the docs only

Files that land in Hubflo, from your team or your clients, flow into the scenario one bundle per file. Nobody needs to check the portal to know a document arrived.

How it fires
scheduled. Make checks Hubflo on the scenario's schedule and lists the files uploaded since the last check.
When to use it
alert the account manager in chat, or copy the file to a storage app. Watch out: on the Free plan Make handles files up to 5 MB, so large uploads need a paid plan.
Modules

What can Make do in Hubflo?

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

Hubflo1

Add embed to workspace

ActionIn the docs only

Your client sees outside content, such as a dashboard or a shared document, right inside their Hubflo workspace. Make adds the embed for you, so the portal stays the single place the client opens.

When to use it
a report built in another tool is ready and the client should find it next to the rest of the project.
Hubflo3

Add project task section

ActionIn the docs only

Tasks inside a Hubflo project stay grouped under clear headings, because this module creates a new section in the project's task list. The team reads the plan phase by phase instead of one long list.

When to use it
right after Create project, to lay out the phases before Create task fills each one.
Hubflo4

Create company

ActionIn the docs only

A new company record appears in Hubflo from data another app already holds, such as a won deal in your CRM or a signed quote. No double entry, and the spelling matches the source.

When to use it
as the first step of onboarding. Watch out: run Search a company before it, or a client already in Hubflo gets a duplicate.
Hubflo5

Create contact

ActionIn the docs only

People from your forms, CRM or inbox become Hubflo contacts without anyone typing their details again. That is the step that makes invitations and client updates possible later in the scenario.

When to use it
a lead converts elsewhere and needs a place in Hubflo. Watch out: Search for a contact first avoids creating the same person twice.
Hubflo6

Create note

ActionIn the docs only

Context stays with the record: this module writes a note in Hubflo from what the scenario gathered, such as a call summary or answers from a form. The team finds the history in one place.

When to use it
log the outcome of a meeting or an email exchange. For a note the client should see in their space, Create workspace note fits better.
Hubflo7

Create project

ActionIn the docs only

Delivery starts on its own: Make opens a project in Hubflo as soon as the scenario has what it needs, for instance a signed quote or a paid invoice in another app.

When to use it
to turn a sale into a project without waiting for someone to set it up. Follow it with Add project task section and Create task to build the plan.
Hubflo8

Create task

ActionIn the docs only

Work reaches the team as a Hubflo task, created from any event the scenario catches: a completed form, a new file, a message in another tool. Nothing depends on someone remembering.

When to use it
every client request should become an assigned task. Watch out: in a scenario started by Watch new tasks, this module feeds its own trigger.
Hubflo9

Create workspace

ActionIn the docs only

Each client gets their own space in Hubflo the moment the scenario runs, instead of whenever someone finds the time. It is the backbone of an automated onboarding.

When to use it
after Watch new companies or a won deal elsewhere. Search a workspace beforehand if the same client could come through twice, so they keep a single space.
Hubflo10

Create workspace folder

ActionIn the docs only

Documents stay tidy in the client's workspace because Make adds the folders for you. The client knows where to drop files, and so does the team.

When to use it
right after Create workspace, to set up the same structure for every client. Use Search a workspace folder when you need an existing one instead.
Hubflo11

Create workspace note

ActionIn the docs only

A message appears inside the client's workspace, written from data the scenario already holds: a welcome text, a status update, next steps after a meeting.

When to use it
the client should read the information in their portal rather than in a scattered email thread. Keep internal remarks for Create note, which is the better home for them.
Hubflo12

Invite contact to workspace

ActionIn the docs only

The client gets access to their workspace without anyone sending the invitation by hand. Make takes a contact and a workspace, and joins the two.

When to use it
at the end of an onboarding scenario, once Create workspace and Create contact have done their part. Watch out: take the contact and the workspace from earlier modules instead of typing them.
Hubflo13

Make an API call

ActionIn the docs only

Whatever the listed modules leave out, this one can reach: it calls any endpoint of the Hubflo API with the connection you already set up. No second login, no separate tool.

When to use it
you need a Hubflo feature that has no dedicated module. Watch out: you write the request yourself, so keep the Hubflo API documentation open.
Hubflo14

Retrieve a task

ActionIn the docs only

One task, fully loaded: give Make the task you want and it returns that task's details for the next modules to use. Useful when the trigger only gives you part of the picture.

When to use it
you know which task you need, for example from a previous module, and want its current state before deciding what to do next.
Hubflo15

Search a company

SearchIn the docs only

Before creating anything, check whether the company is already in Hubflo. The search can return zero, one or several companies, each as its own bundle.

When to use it
ahead of Create company or Update company, to avoid duplicates. Watch out: several matches mean the following modules run once per company, which costs one operation each.
Hubflo16

Search a project

SearchIn the docs only

Finding the right project becomes a step of the scenario, so later modules can update it or add tasks to it. Results come back as bundles, possibly none.

When to use it
an event in another app concerns an existing project and you need it before Update project, so you know what to change.
Hubflo17

Search a workspace

SearchIn the docs only

Locates the client's existing Hubflo workspace so the scenario can add links, notes or folders to it. It may return several workspaces, or nothing at all.

When to use it
a file or message arrives elsewhere and must be published in a workspace that already exists. Combine it with Update workspace or Add link to workspace.
Hubflo18

Search a workspace folder

SearchIn the docs only

Gets you the folder you need inside a workspace, so the next modules know where things belong. Like every search, it can return zero, one or many folders.

When to use it
you want to reuse a folder that Create workspace folder made earlier instead of creating a second one with the same purpose.
Hubflo19

Search for a contact

SearchIn the docs only

Check who already exists in Hubflo before adding or inviting anyone. The module hands back every matching contact as a bundle, or nothing if the person is new.

When to use it
a form or CRM sends a person and you must decide between Create contact and Update contact based on what comes back.
Hubflo20

Send form to client

ActionIn the docs only

The right questionnaire reaches the client when the scenario says so, not when someone thinks of it. Make sends a Hubflo form to a client and the answers come back through Hubflo.

When to use it
collect onboarding details once the workspace is ready, then pick up the answers with Watch completed forms in another scenario.
Hubflo21

Update company

ActionIn the docs only

Company details in Hubflo stay in line with the rest of your stack: Make rewrites the fields you map with fresh data from another app.

When to use it
the billing tool or CRM holds the reference version of a company. Watch out: do not run it in a scenario started by Watch updated company, or each update starts the scenario again.
Hubflo22

Update contact

ActionIn the docs only

A changed phone number or job title reaches Hubflo without manual edits, because Make updates the contact from the source that changed.

When to use it
right after Search for a contact found the person, when your CRM or form has newer details. That way Hubflo never lags behind.
Hubflo23

Update project

ActionIn the docs only

Project records follow what happens elsewhere: a paid invoice, a signed change order, a new deadline agreed by email. Make applies the change to the Hubflo project.

When to use it
after Search a project, when an event outside Hubflo should change the project. The client then sees an accurate status in their portal.
Hubflo24

Update task

ActionIn the docs only

Tasks in Hubflo change as the work changes: new assignee, new status, new details, all written by the scenario instead of by someone clicking through.

When to use it
a ticket closes in another tool and the matching Hubflo task should follow. Retrieve a task first if you need its current state before editing.
Hubflo25

Update workspace

ActionIn the docs only

The client's workspace keeps up with the relationship: Make changes its settings or details when something shifts, such as a new project phase or a renamed account.

When to use it
following Search a workspace, when data from your CRM or another scenario should be reflected in the portal the client sees.
Need help

Need help automating Hubflo with Make?

A person reads every message.

FAQ

Questions about the Hubflo Make integration

01Is the Hubflo Make integration free?
Yes, on the Make side. Hubflo is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute, remove the active scenario cap and allow runs up to 40 minutes. Usage is counted in operations, one per module per bundle. Hubflo itself needs its own active subscription.
02What is needed to connect Hubflo to Make?
An active Hubflo account and its API key. In Hubflo, go to Settings, open the API section and copy the key displayed. In Make, add a Hubflo module, click Create a connection, optionally name it, then paste the key and follow the on-screen instructions. The connection is then reused by all 34 Hubflo modules, so you only do this once per account. Keep the key private, since it gives access to your Hubflo data.
03Do Hubflo triggers in Make fire instantly?
No. All 9 Hubflo triggers are scheduled: Make checks Hubflo on the scenario's schedule and processes what changed since the previous check. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. None of the Hubflo triggers is instant, so there is no webhook to create when you add one. Expect a short delay between an event in Hubflo and the scenario's reaction.
04What if a Hubflo module is missing in Make?
Use the Make an API call module. It calls any endpoint of the Hubflo API with the connection you already created, so it covers what the other modules do not. You write the request yourself, which means reading the Hubflo API documentation. Also note that the Make doc for Hubflo describes itself as AI-generated and possibly inaccurate, and gives no description for each module: test with Run once and read the bundles before you trust a field.
05Should Hubflo be automated with Make or n8n?
It depends on how you prefer to work. Make gives Hubflo a ready app with 34 modules, 9 scheduled triggers, 20 actions and 5 searches, plus Make an API call for the rest, all set up with a single API key. Hubflo may also have an n8n node. The honest way to choose is to list the Hubflo events and actions your process needs, then check which tool covers them with the fewest hand-written requests. Neither tool is ranked above the other here.
Same platform

Other docs you might need on this stack.

Browse all integrations