On this page

Jump to any section using the links below

Hubhus is a platform for managing leads, customer journeys, bookings, files, and automations. It is designed to keep processes structured, ensure clear workflows, and maintain consistent communication with customers.

All activity in Hubhus is organized into campaigns, which define their own fields, pages, booking forms, and automations.

Campaigns

A campaign is a workspace that groups together everything related to a specific business process—such as quotations, service visits, support cases, or onboarding.

Inside each campaign you define:

• Fields (data inputs such as name, phone, price, notes)

• Select fields (predefined choices for statuses or categories)

• Statuses (steps in your workflow)

• Booking forms and pages

• Automations (emails, SMS, routing rules)

• Files and documentation

• Real-time action listeners

Campaigns ensure each process has its own structure and flow.

Fields

Fields store information about each lead. They can be:

• text

• numbers

• dates

• select values

• structured JSON (data fields)

Fields are used in:

• forms and booking flows

• emails and SMS

• pages

• automations

• conditional visibility

They define the data model of the campaign.

Select fields

Select fields offer predefined options—such as customer type, urgency, or region.

They enable consistent categorization and are used in:

• reports

• automations

• conditional logic

Use:

• @select[field] to display the label

• @select[field,slug] for comparisons in logic

Statuses

Statuses represent where a lead is in the workflow.
Examples: New, Contacted, Quote Sent, Closed.

Statuses are used in:

• pipelines

• automation triggers

• reporting

• routing and visibility

They ensure each lead moves through the process in a controlled way.

Booking forms

Booking forms allow customers to book directly from your website.

A form determines:

• required resources

• duration

• address rules

• travel time constraints

• business hours

• availability logic

Booking forms can be:

• hosted standalone pages

• embedded widgets

• multi-step flows

All bookings respect the resource calendar logic.

Webpages

Hubhus pages allow you to present dynamic content such as:

• quotes

• documentation

• file upload flows

• customer dashboards

Pages support placeholders, logic, branding, and integration with automations.

Automations

Automations run based on events such as:

• status changes

• field updates

• bookings

• delays

• customer actions

They can:

• send emails or SMS

• update fields

• change status

• trigger webhooks

• run chained workflows

Automations reduce manual work and ensure consistency.

Action listeners

Action listeners react instantly to data changes, such as:

• new files

• updated fields

• created bookings

• completed submissions

Ideal for quick notifications and integrations.

Files

You can upload files directly to a lead—either internally or through customer-facing forms.

Files can be used in:

• documentation

• internal views

• emails

• pages

• workflows

All files are stored securely within the lead.

Placeholders and dynamic content

Placeholders automatically insert lead data into emails, SMS, or HTML pages.

Examples:

• %lead_name%

• %assigned_person_name%

• %brand_name%

• %event_start_date%

• {{api_name}} (custom fields)

How to find placeholders

Press:

• CTRL + K (Windows)

• CMD + K (Mac)

This opens the placeholder search modal, where you can find:

• lead fields

• select fields

• event placeholders

• booking form references

• HTML components

• pages (@page[…])

You can search using everyday words such as “lead name”, “address”, “event date”, “signature”, or “brand contact”.

Conditional logic (@if)

Conditional statements allow you to show different content depending on lead data.

Example:

@if(%assigned_person_name%)
  Your contact person is: %assigned_person_name%
@else
  No contact person assigned yet.
@endif

You can also compare select slugs:

@if(@select[task-type,slug] == urgent)
  This task is marked as urgent.
@endif

Logic can be used in:

• emails

• SMS

• pages

• HTML components

HTML components

HTML components allow you to create dynamic, styled content without writing code.

Typical uses include:

• internal summaries

• customer confirmations

• document previews

• signature blocks

• reusable content snippets

Components work with placeholders and conditional logic, and can be included across emails, pages, and templates.

Related articles

Understanding campaign filters and sources
Understanding the lead lifecycle
What is a campaign in Hubhus?
What is the Hubhus API?
Building workflows in Hubhus