Resources · Zapier integration

Hubhus Zapier integrationAutomate Hubhus with Zapier.

The Hubhus Zapier integration gives you 6 operations: 1 trigger, 3 actions and 2 searches. Enough to push leads in from your other tools, move them between campaigns and clean up, as long as you know which step costs a task.

See the 6 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Hubhus Zapier integration actually does

Hubhus is a CRM built around leads: you capture them, sort them into campaigns and follow them through a sales pipeline. Connected to Zapier, it can start an automation when a lead appears, and it can create, update, look up or delete leads when something happens elsewhere.

Three results people build first. A lead form somewhere else feeds Hubhus directly, through Create Lead, so nobody retypes names from an inbox. A fresh lead gets reviewed and moved to another campaign with Update Lead, before a salesperson even opens it. And a duplicate check runs before anything is written, thanks to Find Leads and its find-or-create option.

Now the part the app page skips. There is only one trigger, and it is polled: Zapier asks Hubhus for new leads on a timer, so the free plan can lag by up to 15 minutes. Nothing fires when a lead is edited or changes stage, only when one is created. There is no way to create or edit a campaign from Zapier either: the campaign has to exist in Hubhus before a Zap can drop leads into it.

If you would rather build the same flows elsewhere, the Hubhus Make integration covers the Make side, and the Make vs Zapier page helps with the choice between the two.

Vocabulary

Zapier words in one minute

Eight terms, each used again further down without a reminder.

Zap
Your automation on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts the Zap. Here, a new lead landing in Hubhus. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes something for you, like creating or updating a Hubhus lead.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan is a count of those.
Polling trigger
A trigger Zapier checks on a timer. It asks the app for new items and keeps only the ones it has not seen yet.
Instant trigger
A trigger the app reports itself, the second the event happens. Hubhus has none of these on Zapier today.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and quietly stops it otherwise.
Search step
A step that looks up something already in an app, so later steps can reuse what it found, like a lead ID.
Cost

What a Hubhus Zap really costs

Short version: Hubhus is not a premium app, so it works on the free plan, within the limits of that plan.

  • Free plan100 tasks a month, unlimited Zaps
  • Trigger checksFree of charge
  • Premium appNo
  • Filter or searchPaid plan required

The trigger never costs anything, however often Zapier checks for new leads. Each action that succeeds counts as one task; one that fails is not counted. A Zap that creates a lead and then updates it uses two tasks per run. The catch on the free plan: it only builds two-step Zaps, one trigger and one action. Add a filter or a search step and the Zap becomes multi-step, which needs a paid plan, whatever app sits in it.

Connect

Connect your Hubhus account

  1. 01

    Open your Apps page

    In Zapier, go to Apps and click + Add connection. A connection is your Hubhus account linked once, then reused by every step that touches Hubhus in any of your Zaps.

  2. 02

    Pick Hubhus

    Type Hubhus in the search box of the dialog, select it, then click Add connection. You need an existing Hubhus account for this, Zapier does not create one.

  3. 03

    Sign in and allow access

    Log in to Hubhus in the tab that opens and grant Zapier access. If the leads or campaigns belong to a colleague, make sure your account can read and write them first.

First Zap

Your first Hubhus Zap, step by step

GoalEvery new lead in Hubhus that meets your condition gets moved to a follow-up campaign, without anyone touching it.

  1. 01

    Build: choose the trigger

    Create a Zap, pick Hubhus as the app and New Lead as the event, then select the Hubhus connection you added in the previous section.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent leads of your account, so you can map fields from a real one instead of a blank.

  3. 03

    Add the filter

    From the plus icon, add Filter. Pick the field, the rule and the value. Use a text rule on text: a mismatched rule type is why a filter never passes.

  4. 04

    Add Update Lead

    Add Hubhus again, event Update Lead. Map the lead ID from the trigger, then choose the campaign the lead should move to.

  5. 05

    Test, then Publish

    Test each step and read what came back. When the update looks right in Hubhus, click Publish to switch the Zap on. A filter makes it multi-step, so this needs a paid plan.

Triggers

The Hubhus trigger

1 event starts a Zap when something happens in Hubhus. Zapier checks for them at the interval your plan allows.

1

New Lead

Polling trigger

In Zapier“Triggers when a new lead is created.”

This one starts your Zap each time a new lead is created in Hubhus, one run per lead. It is the only door into Zapier on the Hubhus side.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a solar installer wants every new prospect copied to the tool where site surveys get booked.
Watch out
editing a lead or changing its stage does not count as new, so this trigger will never react to pipeline moves.
Actions

Hubhus actions, grouped by what they do

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

1

Create Lead

Action

In Zapier“Creates a new lead in the system.”

Adds a fresh lead to Hubhus from whatever event started the Zap, so contact requests stop living in an inbox.

When to use it
a quote request lands in your form tool and should become a Hubhus lead in the right campaign.
Watch out
the campaign is mandatory, so pick it before testing.
2

Delete Lead

Action

In Zapier“Deletes a lead from the system.”

Removes one lead from Hubhus, identified by its lead ID. Hubhus itself flags this as something you cannot undo.

When to use it
rarely, and only on a lead ID you are sure about, such as one returned by Find Lead.
Watch out
test it on a dummy lead, never on a live pipeline.
3

Update Lead

Action

In Zapier“Updates an existing lead in the system.”

Changes an existing lead in place. You give it the lead ID and a campaign, both required, and it rewrites the fields you map.

When to use it
moving a qualified prospect to the campaign your closers work from.
Watch out
without a lead ID from an earlier step, add Find Leads first to get one.
Searches

Hubhus searches and the find-or-create option

2 search steps look for data that already exists in Hubhus, so a later step can use it.

A search step sits in the action list under its own SEARCH heading. It costs you a paid plan, because it makes the Zap multi-step, but it saves you from duplicates and missing IDs. Three settings decide what happens when the result is not what you expected.

1

Find Lead

Search

In Zapier“Finds a specific lead by its ID.”

Fetches one precise lead when you already hold its ID, and hands its details to the next steps.

When to use it
confirming a lead still exists and reading its current campaign before an update or a deletion.
Watch out
the lead ID is required, so this search cannot look up a lead by name.
2

Find Leads

SearchFind or create

In Zapier“Finds leads matching the criteria.”

Looks for leads that match the criteria you set, which is how a Zap checks whether someone is already in Hubhus.

When to use it
before creating a lead, so a returning prospect is not entered twice.
Watch out
the editor also shows Find or Create Lead. It is this same search with the create box ticked, not a separate operation.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that relied on it. Switched on, the Zap carries on empty-handed.
  2. Create Lead if it doesn't exist yet?
    Ticking this turns the search into a find-or-create. The setting above disappears and the step asks for the fields it needs to create the missing lead.
  3. If multiple search results are found?
    Three ways out when several leads match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When a Hubhus Zap breaks

Zapier publishes no help article for Hubhus, so the traps below come from how Zapier itself works.

With no Hubhus-specific limits on record, the risks here are the ones Zapier applies to every app: timing, loops and volume. Read these four before you publish, and keep the Zapier troubleshooting guide nearby for the day a run goes red.

  • Old leads are never picked up

    A Zap only reacts to leads created after you switch it on. The leads already in Hubhus stay where they are; moving that backlog is a separate job.

  • A Zap that feeds itself

    A Zap that starts on New Lead and ends with Create Lead creates a lead, which starts the Zap again. It loops and burns your task count fast.

  • A bulk import goes quiet

    After a big import into Hubhus, the trigger can suddenly return a huge batch. Zapier's flood protection may hold those runs back for review.

  • The same lead runs only once

    Zapier remembers which leads it has already seen on a polled trigger. A lead that was processed will not start the Zap a second time.
Need help

Need help automating Hubhus with Zapier?

A person reads every message.

FAQ

Hubhus Zapier integration: common questions

01Is the Hubhus Zapier integration free?
Yes, Hubhus is not a premium app, so you can use it on the free Zapier plan. That plan gives you 100 tasks a month and unlimited Zaps, which is plenty for a first test, but each Zap is limited to two steps: one trigger and one action. As soon as you add a filter, a search step or a second action, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a Hubhus Zap use?
One task per successful action, and nothing for the trigger. Zapier can check for new leads as often as your plan allows without charging you for those checks. A Zap with Create Lead alone costs one task per run; a Zap that finds a lead and then updates it counts the update as a task too. An action that fails is not counted. Keep an eye on loops, because a Zap that keeps restarting itself spends tasks on every pass.
03Does Hubhus trigger Zaps in real time?
No, New Lead is a polling trigger. Zapier asks Hubhus for new leads on a timer, and the timer depends on your plan: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. On paid plans you can also run a check by hand from the editor. If a sales team expects instant alerts on fresh leads, plan around that delay or pick a paid plan with a shorter interval.
04What does connecting Hubhus to Zapier require?
An active Hubhus account and the right to read and write the leads and campaigns your Zap will touch. You add the connection once from the Apps page with + Add connection, sign in to Hubhus in the new tab and grant access. After that, every Hubhus step in every Zap reuses the same connection. Make sure the campaigns you plan to use are visible to that account, since creating and updating leads both require one.
05Why does an Update Lead step keep failing?
Usually because a required value is missing. Update Lead needs both the lead ID and a campaign, and neither can be left empty. If the step that started your Zap does not carry the ID, add Find Leads or Find Lead before the update so Zapier has one to map. Also check that the campaign still exists in Hubhus and that your connected account can see it. Test the step again afterwards and read the result before publishing.
06What if a Hubhus operation is missing from Zapier?
Then the integration simply cannot do it today. Zapier lists one trigger, three actions and two searches for Hubhus, and nothing else is offered in the editor. There is no trigger for an updated lead and no step that creates a campaign, for example. A workaround sometimes exists, such as chaining a search and an update, but if the event itself is missing, ask Hubhus whether they plan to add it, or check whether another platform exposes it.
07Zapier, Make or n8n for Hubhus?
It depends on the criterion, not on a ranking. On Zapier, Hubhus works from the free plan, every successful action counts as a task, and the only trigger is polled. Before choosing, list the Hubhus events and steps your flow needs, then check which platform actually exposes them. Next, compare how each one bills a run of your flow, and whether the delay of a polled trigger is acceptable for your sales team. The answer usually falls out of those three checks.
Same platform

Other docs you might need on this stack.

Browse all integrations