Resources · Make integration

OnceHub Make integrationAutomate OnceHub with Make.

Every booking change in OnceHub can start a workflow. The OnceHub Make integration gives you 8 triggers that watch bookings and 1 module that calls the OnceHub API. This page shows you how to connect your account, build a first scenario and pick the right trigger.

Try the OnceHub integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the OnceHub Make integration do for you?

The OnceHub Make integration links your OnceHub account to Make, a no-code automation tool, so that booking events feed the rest of your stack. It reads bookings through 8 scheduled triggers, and a single Make an API Call module reaches any other part of the OnceHub API with the same connection.

A clean record of new meetings. Watch Bookings picks up each new booking so a scenario can pass the details to the tool your sales team already uses, instead of someone copying them by hand.

A follow-up for people who missed the call. Watch Booking No Showed catches the meetings flagged as no-shows, which is the right moment to send a second chance or alert the account owner. Watch Booking Completed covers the opposite case: the meeting happened and the next step can start.

Calendar changes that stay in sync. Cancellations, reschedules and reassignments each have their own trigger, so you can react to one kind of change without filtering the others out.

What Make does not give you here: no instant trigger (every watcher is scheduled) and no ready-made module to create or edit a booking. For anything beyond watching, Make an API Call is the way in. The same app often has an n8n node too; the n8n vs Make comparison helps you choose, and the Make pricing page explains how operations are counted. If you run other booking tools, the Acuity Scheduling Make integration follows the same logic.

Connect

How do you connect OnceHub to Make?

  1. 01

    Copy your OnceHub API key

    In OnceHub, open Account, then Integrations, then API, and copy the key shown on screen. You need an active OnceHub account to get this key.

  2. 02

    Add a OnceHub module in Make

    In your scenario, add any OnceHub module and click Create a connection. A connection is your OnceHub account linked to Make once; every OnceHub module of every scenario reuses it afterwards.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you manage several accounts (this field is optional), paste the API key you copied, then follow the on-screen instructions to finish.

First scenario

Build your first scenario with OnceHub

GoalWhen a new booking lands in OnceHub, Make picks it up and calls the OnceHub API to fetch the extra details your next step needs.

  1. 01

    Create the scenario

    A scenario is the automation you build in Make, a chain of modules. From the Scenarios page, create a new one and click the + to add the first module.

  2. 02

    Pick Watch Bookings

    Search for OnceHub, choose Watch Bookings and select the connection you created. Each new booking will reach the scenario as a bundle, one item passed from a module to the next.

  3. 03

    Add Make an API Call

    Click the + on the right of the trigger, add Make an API Call and map the booking data from the first module into the request you want to send to OnceHub.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received, so you can check what OnceHub really sends before going further.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default; adjust it within your plan, then switch the scenario on.

Triggers

Which OnceHub triggers start a scenario?

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

OnceHub1Watch Booking Canceled

Watch Booking Canceled

triggerIn the docs only

This trigger hands you every OnceHub booking that ends up canceled, so a free slot or a lost lead never goes unnoticed. Each cancellation arrives as its own bundle, ready to be sent to another app.

How it fires
scheduled, Make checks OnceHub on the scenario's schedule, shown by the clock badge on the module.
When to use it
a salesperson wants to know right after the next check that a prospect dropped the demo, to reach out while the interest is still there.
Watch out
Make lists this trigger in the documentation only, with no official description, so run it once on a real cancellation and read the bundle before building on it.
OnceHub2Watch Booking Canceled Reschedule Requested

Watch Booking Canceled Reschedule Requested

triggerIn the docs only

With this watcher, a scenario learns about the canceled bookings where a new date was asked for, which is a very different situation from a plain cancellation. The person still wants to meet; the booking simply needs a new slot.

How it fires
scheduled, Make queries OnceHub at the rhythm set on the first module.
When to use it
a support team that wants to nudge the contact with the booking link until the new time is picked.
Watch out
the doc gives no description of this module, so confirm with Run once what the bundle contains.
OnceHub3Watch Booking Canceled then Rescheduled

Watch Booking Canceled then Rescheduled

triggerIn the docs only

Here the loop is closed: the booking was canceled and a new one was then set up. Picking this trigger lets you update the old record instead of treating the new meeting as a stranger.

How it fires
scheduled, Make polls OnceHub whenever the scenario's clock tells it to.
When to use it
a consultant who keeps one line per client in a spreadsheet and wants the date replaced rather than a duplicate row.
Watch out
this event overlaps with Watch Booking Rescheduled in wording; test both on a real case before choosing, since the doc does not describe either one.
OnceHub4Watch Booking Completed

Watch Booking Completed

triggerIn the docs only

Once a meeting has taken place, this trigger passes it to Make so the after-meeting work starts without anyone remembering to do it. It is the natural starting point for thank-you notes, surveys or a task in your project tool.

How it fires
scheduled, Make looks at OnceHub on the scenario's schedule.
When to use it
a training company that sends course material to each attendee once the session is marked as done.
Watch out
the doc gives no description of this module, so check with Run once which bookings OnceHub treats as completed before you send anything to attendees.
OnceHub5Watch Booking No Showed

Watch Booking No Showed

triggerIn the docs only

Missed meetings get their own trigger, which lets you treat an absent prospect differently from one who canceled politely. Each no-show becomes a bundle you can route to a reminder, a CRM field or an alert.

How it fires
scheduled, Make asks OnceHub for new events at the interval set on the clock.
When to use it
a recruiter who wants candidates who skipped the interview to receive a message with a link to book again.
Watch out
the module has no official description, so test it on a real missed meeting with Run once before a message goes out to anyone.
OnceHub6Watch Booking Reassigned

Watch Booking Reassigned

triggerIn the docs only

When a booking moves from one host to another, this trigger lets the right person know. It avoids the classic case where a meeting changes owner and the new host discovers it at the last moment.

How it fires
scheduled, Make checks OnceHub each time the scenario's schedule comes around.
When to use it
a sales team that shares leads and wants the new owner pinged in the team chat along with the meeting details.
Watch out
the doc gives no detail on what the bundle carries about the previous host, so check a real run before mapping names.
OnceHub7Watch Booking Rescheduled

Watch Booking Rescheduled

triggerIn the docs only

This one fires on bookings that moved to another date, so every downstream tool gets the new time without manual edits. It is the trigger to choose when your aim is keeping calendars, reminders and records aligned.

How it fires
scheduled, Make reads OnceHub at the pace defined on the first module.
When to use it
a clinic that sends patients a confirmation with the updated time after they moved their appointment.
Watch out
the wording is close to Watch Booking Canceled then Rescheduled, and the doc describes neither, so compare both on a real case with Run once.
OnceHub8Watch Bookings

Watch Bookings

triggerIn the docs only

The broadest watcher of the list: it brings new OnceHub bookings into Make so you can log them, share them or enrich them elsewhere. Start here if you are not sure which event you need.

How it fires
scheduled, Make polls OnceHub on the scenario's schedule, every 15 minutes by default.
When to use it
an agency that wants each new discovery call copied into its client pipeline without anyone retyping it.
Watch out
on the Free plan, 15 minutes is also the shortest interval, so a booking can wait that long before the scenario sees it.
Modules

What else can OnceHub do in Make?

OnceHub gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

OnceHub1

Make an API Call

ActionIn the docs only

This module opens the whole OnceHub API from your scenario, using the connection you already set up, so you are not limited to the events the triggers watch.

When to use it
you need to read or change something in OnceHub that no listed module covers, for example after Watch Bookings has handed you a booking.
Watch out
you write the request yourself, so keep the OnceHub API documentation open and test every call with Run once before switching the scenario on.
Need help

Need help automating OnceHub with Make?

A person reads every message.

FAQ

Questions about the OnceHub Make integration

01Is the OnceHub Make integration free?
Yes, on the Make side. OnceHub is a standard app, available on every Make plan including Free. The Free plan allows 2 active scenarios, a minimum of 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 (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. You still need an active OnceHub account, whose price depends on OnceHub.
02What is needed to connect OnceHub to Make?
An active OnceHub account and its API key. In OnceHub, go to Account, then Integrations, then API, and copy the key displayed. In Make, add a OnceHub module, click Create a connection, optionally name it, and paste the key. That connection is saved once and every OnceHub module in your scenarios reuses it, so you only repeat the process if you link a second OnceHub account. If the key is refused, copy it again from the same screen.
03Do OnceHub triggers in Make fire in real time?
No. All 8 OnceHub triggers are scheduled, which means Make checks OnceHub on the scenario's schedule rather than being alerted the moment a booking changes. Make's doc only lists these modules, so this type is inferred from their names: confirm it with the clock badge on the module. A new scenario runs every 15 minutes by default. On the Free plan that is also the shortest interval allowed; paid plans can go down to 1 minute. Keep that gap in mind when a reminder has to go out close to the meeting time.
04What if a OnceHub module is missing in Make?
Use Make an API Call. It sends a request to any part of the OnceHub API with the same connection as the triggers, so creating or updating something that the 9 listed modules do not cover is still possible. You write the request yourself, following the OnceHub API documentation. Test it with Run once to see exactly what comes back before you map the result to the next module of your scenario.
05Should OnceHub be automated with Make or n8n?
It depends on the tool your team already works in. Make offers OnceHub as 8 scheduled triggers plus Make an API Call, set up in a visual editor with a free plan to start. The same app often has an n8n node as well, so check what it covers for your case. Compare the modules each side offers for the events you need, such as no-shows or reassignments, rather than picking by habit; the n8n vs Make comparison on this site walks through the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations