Resources · Make integration

Arbox v3 Make integrationAutomate Arbox v3 with Make.

Can Make react when a lead, a booking or a membership changes in Arbox v3? Yes. The Arbox v3 Make integration offers 26 scheduled triggers and 13 actions. This guide shows teams that run classes and memberships how to link their account, build a first scenario and pick the right module.

Try the Arbox v3 integration on MakeSee the 39 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Arbox v3 Make integration automate?

The Arbox v3 Make integration links your Arbox account to Make, where you build a scenario: the automation, a chain of modules. A module is one brick of it, either a trigger that watches Arbox v3 or an action that writes to it. All 26 triggers here are scheduled, which means Make checks Arbox v3 on the scenario's schedule instead of waiting for an alert. Since the doc gives no type, that reading comes from their names. Check for the clock badge.

No lead left without a follow-up. Watch new lead picks up the leads added in Arbox v3, and Create a task hands a salesperson the next call to make. When the prospect goes cold, Mark a lead as lost closes the file so the pipeline stays honest.

A warmer welcome for trial visitors. Watch trial class starts a scenario around each trial, and Send a Message reaches out before the session. If the visitor signs up afterwards, Watch converted lead can kick off a second scenario for onboarding.

Membership changes the front desk actually hears about. Watch cancelled membership, Watch membership hold and Watch renew membership each start a scenario on a change of status, so nobody has to scan Arbox v3 to spot them.

What you will not get here is an instant trigger: everything runs on the schedule, every 15 minutes by default on a new scenario. The official doc also lists the modules without any description and warns that its content is AI-generated and may contain mistakes, so test each module with Run once before trusting it. For a guided path, the Make training covers the editor step by step, and n8n vs Make helps if you are still choosing a tool.

Connect

How do you connect Arbox v3 to Make?

  1. 01

    Copy your API key in Arbox v3

    Make signs in with an API key, and you need an active Arbox account to get one. In Arbox v3, open Settings, click Club Information and copy the API key displayed on screen. Keep it handy for the next step.

  2. 02

    Add a module and create the connection

    In your Make scenario, add any Arbox v3 module and click Create a connection. A connection is your Arbox account linked to Make once, then reused by every Arbox v3 module. The Connection name field is optional, but a clear name makes it easy to find later.

  3. 03

    Paste the key and save

    Paste the API key you copied from Arbox v3, or follow the instructions Make shows on screen, and save. The connection then sits in the module's menu, ready for every other Arbox v3 module you add to the scenario.

First scenario

Your first scenario with Arbox v3

GoalWhen a trial class shows up in Arbox v3, Make sends a message about it.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + in the editor to add the very first module.

  2. 02

    Add the trial class trigger

    Search for Arbox v3, pick Watch trial class and click Create a connection with your API key. The clock badge on the module tells you it is a scheduled trigger.

  3. 03

    Add the message

    Click the + on the right of the trigger and choose Send a Message. Fill its fields and map data from the trial class bundle, the item the trigger passes along.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check the message content before going live.

  5. 05

    Schedule and switch it on

    On the first module, set the schedule (every 15 minutes by default), then switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Triggers

Which Arbox v3 events can start a scenario?

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

Arbox v31Watch booked appointment

Watch booked appointment

triggerIn the docs only

Get a scenario going each time an appointment is booked in Arbox v3, so a private session or a consultation never slips past your team. Every booking reaches the next module as its own bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule and collects the bookings made since the previous check.
When to use it
a coach wants a reminder task each time a client books time with them.
Watch out
the doc gives no description of this module, so run it once on a real booking and read what it returns before you map anything.
Arbox v32Watch cancelled appointment

Watch cancelled appointment

triggerIn the docs only

Hear about a cancelled appointment in Arbox v3 without refreshing the calendar, and give the freed slot a second life with another client.

How it fires
scheduled. Make polls Arbox v3 at the pace set on the scenario, not at the moment the client cancels.
When to use it
pair it with Send a Message to warn the coach, or with Create a task so the front desk offers the slot again.
Watch out
a cancellation only reaches Make at the next scheduled check, so a slot freed right before a session may show up too late to rebook.
Arbox v33Watch cancelled event

Watch cancelled event

triggerIn the docs only

A cancelled event in Arbox v3 becomes a starting point: Make can warn the people involved, update a calendar in another app or log the change for the manager.

How it fires
scheduled. Make looks at Arbox v3 each time the scenario runs; the app pushes nothing to Make on its own.
When to use it
an event is called off and everyone registered should hear about it quickly.
Watch out
events and appointments have separate triggers here. If you are not sure which one Arbox v3 uses for your sessions, test both with Run once before building.
Arbox v34Watch cancelled membership

Watch cancelled membership

triggerIn the docs only

Know which members just left: this trigger hands Make each membership cancelled in Arbox v3, ready for a follow-up, a report or a win-back campaign in another tool.

How it fires
scheduled. Make queries Arbox v3 on every run of the scenario.
When to use it
your team wants to send a short exit survey, or add the person to a list in your email tool.
Watch out
paused memberships have their own trigger, Watch membership hold. Keep the two scenarios apart so a pause never gets treated like a departure.
Arbox v35Watch check ins

Watch check ins

triggerIn the docs only

Every check-in recorded in Arbox v3 can feed Make, which turns attendance into data you can use outside the app, in a sheet, a dashboard or a loyalty program.

How it fires
scheduled. Make checks the app on the scenario's schedule, so several check-ins can arrive in a single run.
When to use it
you count visits in a spreadsheet, or you want to reward regular members when they reach a milestone.
Watch out
a busy day means many check-ins, and each one is a bundle that costs an operation in every module it passes through.
Arbox v36Watch confirm entry from waiting list

Watch confirm entry from waiting list

triggerIn the docs only

When someone on a waiting list confirms their spot in Arbox v3, this trigger lets Make act on that confirmation at its next check, without anyone watching the list.

How it fires
scheduled, following the scenario's clock; Arbox v3 does not call Make by itself.
When to use it
the coach should see the updated attendance, or the member should get a confirmation through Send a Message.
Watch out
the name is close to Watch entry from waiting list. Run each one once to see which step of the waiting list it reports before you choose.
Arbox v37Watch converted lead

Watch converted lead

triggerIn the docs only

Share a win in the tools where your team works: Make receives each lead that Arbox v3 marks as converted and can pass it to finance, chat or your CRM.

How it fires
scheduled. Make checks Arbox v3 at the interval set on the first module.
When to use it
sales wants the new customer posted in the team chat, or your accounting tool needs the record.
Watch out
a lead and a client are different records. If you also run Watch new client, one sign-up may start both scenarios, so check that the person does not get two messages.
Arbox v38Watch credit refusal

Watch credit refusal

triggerIn the docs only

Spot each credit refusal logged in Arbox v3 and route it to the person who handles it, instead of discovering it at the front desk.

How it fires
scheduled. Make asks Arbox v3 for new refusals on each run of the scenario.
When to use it
the manager wants a task created with Create a task as soon as Make picks up a refusal.
Watch out
the doc does not define what a credit refusal covers. Run the scenario once on a known case and read what Arbox v3 sends before you build anything on top of it.
Arbox v39Watch edit task

Watch edit task

triggerIn the docs only

Stay in sync when someone changes a task in Arbox v3: Make receives the edited task and can mirror the change in the project tool your team prefers.

How it fires
scheduled. Make polls the app according to the scenario's schedule.
When to use it
tasks also live in another tool, and every edit made in Arbox v3 should follow there without retyping.
Watch out
this trigger only covers edits. Brand new tasks come through Watch new task, so run both in separate scenarios if you need the full picture.
Arbox v310Watch entry from waiting list

Watch entry from waiting list

triggerIn the docs only

Someone moves from the waiting list into a session in Arbox v3, and Make can react to that entry with a message, a task or a line in a report.

How it fires
scheduled. Make checks Arbox v3 whenever the scenario runs.
When to use it
the member deserves a heads-up that a spot opened, sent through Send a Message.
Watch out
the doc does not explain how this differs from Watch confirm entry from waiting list. Compare the bundles of both on a test before you pick one, or the member might be contacted twice.
Arbox v311Watch inactive users

Watch inactive users

triggerIn the docs only

Find members who have gone quiet: Make receives the users that Arbox v3 reports as inactive, so someone can reach out before they cancel.

How it fires
scheduled. Make checks the app on the scenario's schedule and returns the users found.
When to use it
a coach wants to call people who stopped coming, or your email tool should start a comeback message.
Watch out
the doc does not say how Arbox v3 decides that a user is inactive. Ask Arbox v3 or check a few results before promising anything to your team.
Arbox v312Watch lost leads

Watch lost leads

triggerIn the docs only

Each lead marked as lost in Arbox v3 can land in Make, so deals that slipped away stay visible instead of vanishing from the pipeline.

How it fires
scheduled. Make polls Arbox v3 at the pace of the scenario.
When to use it
marketing wants lost leads added to a nurturing list, or the sales manager wants a simple log to review.
Watch out
if another scenario uses Mark a lead as lost, the leads it closes will probably come back through this trigger. Check with Run once so you do not count them twice.
Arbox v313Watch medical certificate

Watch medical certificate

triggerIn the docs only

Medical certificates handled in Arbox v3 become events Make can act on, which keeps this paperwork from piling up in a corner of the admin tasks.

How it fires
scheduled. Make queries Arbox v3 on the scenario's schedule.
When to use it
the front desk wants a task whenever a certificate needs someone to look at it.
Watch out
health documents are sensitive. Pass on only what the next app really needs, and think about who can see the bundles of this scenario in Make.
Arbox v314Watch membership hold

Watch membership hold

triggerIn the docs only

Hear when a membership is put on hold in Arbox v3, so billing, coaching plans and follow-ups can adjust without a manual check.

How it fires
scheduled. Make checks Arbox v3 on each run of the scenario.
When to use it
a member pauses for an injury or a long trip, and their coach should know before the next session.
Watch out
a hold is not a cancellation. Cancelled memberships arrive through Watch cancelled membership, so build a separate scenario if you need to follow both.
Arbox v315Watch new client

Watch new client

triggerIn the docs only

Greet each new client that Make finds in Arbox v3 with the tools you already use, from a welcome email to a record in your accounting app.

How it fires
scheduled. Make checks the app at the scenario's interval, not at the second the client is created.
When to use it
a new client should get a welcome message and appear in your billing or email tool.
Watch out
clients you create with Create a client in another scenario will likely show up here too. Plan for it so nobody gets welcomed twice.
Arbox v316Watch new entrance

Watch new entrance

triggerIn the docs only

Log each new entrance recorded by Arbox v3 and use it outside the app, for a visitor log, an occupancy sheet or a report for the owner.

How it fires
scheduled. Make polls Arbox v3 whenever the scenario runs.
When to use it
you keep a visitor log in a spreadsheet and want it filled without typing.
Watch out
the doc does not explain how an entrance differs from a check-in. Test this trigger and Watch check ins side by side, or you might count the same visit twice.
Arbox v317Watch new lead

Watch new lead

triggerIn the docs only

Start a scenario for every lead added to Arbox v3, so no prospect waits days for a reply while the team is busy on the floor.

How it fires
scheduled. Make checks Arbox v3 on the scenario's schedule, every 15 minutes by default.
When to use it
sales wants a follow-up task through Create a task, or the lead copied to the CRM they use.
Watch out
leads created with Create a lead in another scenario come back through this trigger, so never create and watch leads in the same scenario.
Arbox v318Watch new purchase

Watch new purchase

triggerIn the docs only

Turn every purchase recorded in Arbox v3 into an entry somewhere else: an accounting line, a thank-you message or a sales log for the owner.

How it fires
scheduled. Make polls the app on the scenario's schedule.
When to use it
the finance team wants each sale in its own tool without copying it by hand.
Watch out
the doc says nothing about what a purchase bundle contains. Click Run once after a real sale and read the result before you map any amount.
Arbox v319Watch new task

Watch new task

triggerIn the docs only

Hand every new task from Arbox v3 to Make, which can post it in the place your team actually checks during the day.

How it fires
scheduled. Make checks Arbox v3 on the scenario's clock.
When to use it
coaches read their team chat far more than Arbox v3 and want new tasks posted there.
Watch out
tasks your own scenarios create with Create a task will appear here as well, so a single scenario should never both create and watch tasks, or it keeps feeding itself.
Arbox v320Watch renew membership

Watch renew membership

triggerIn the docs only

Renewals in Arbox v3 reach Make, which can thank the member, update your books or tell the coach that the person is staying.

How it fires
scheduled. Make checks the app on the scenario's schedule.
When to use it
a renewal deserves a thank-you through Send a Message and a line in your finance tool.
Watch out
the doc does not say whether automatic renewals count here. Check a few cases with Run once before your team relies on the figures this scenario produces.
Arbox v321Watch sessions

Watch sessions

triggerIn the docs only

Follow the sessions in Arbox v3 and copy them wherever your team plans its work, such as a shared calendar or a staffing sheet.

How it fires
scheduled. Make polls Arbox v3 on each run of the scenario.
When to use it
session times should appear in a calendar that people outside Arbox v3 can open.
Watch out
the doc does not say whether this trigger covers new sessions, changed ones or both. Read the bundles from a test run before building on it, then adjust your mapping.
Arbox v322Watch trial class

Watch trial class

triggerIn the docs only

Use trial classes booked in Arbox v3 as the start of a welcome flow, so a first-time visitor feels expected before walking in.

How it fires
scheduled. Make checks Arbox v3 at the interval set on the scenario.
When to use it
a newcomer should get practical details or a friendly note before the class through Send a Message.
Watch out
trials booked by Book a trial class in another scenario probably count as well, so check with Run once that nobody receives the same message twice.
Arbox v323Watch updated Lead statuses

Watch updated Lead statuses

triggerIn the docs only

See each lead status change in Arbox v3 and let Make move the same lead along in your other tools, so every team reads the same stage.

How it fires
scheduled. Make checks the app when the scenario runs.
When to use it
your CRM should show the same stage as Arbox v3 without anyone updating it by hand.
Watch out
a scenario that also uses Update lead status would feed this trigger again. Keep changes made from Make and changes made in Arbox v3 in separate scenarios.
Arbox v324Watch updated appointment

Watch updated appointment

triggerIn the docs only

Changes to an appointment in Arbox v3 reach Make, so the other tools that show that appointment stay correct after a move.

How it fires
scheduled. Make polls Arbox v3 on the scenario's schedule.
When to use it
the coach's calendar in another app should follow every change made in Arbox v3.
Watch out
cancellations have their own trigger, Watch cancelled appointment. Check whether a cancelled appointment also shows up here before running both, or the calendar may receive two updates.
Arbox v325Watch user cancel registration

Watch user cancel registration

triggerIn the docs only

When a user cancels a registration in Arbox v3, Make can pass the news on, free up follow-ups and keep attendance figures right.

How it fires
scheduled. Make queries Arbox v3 at the pace of the scenario.
When to use it
the coach wants to know who dropped out, and the person handling the waiting list needs a nudge.
Watch out
Cancel a user booking does the reverse from Make. If a scenario uses it, the cancellations it makes may come back through this trigger, so keep them apart.
Arbox v326Watch waiver

Watch waiver

triggerIn the docs only

Waivers handled in Arbox v3 become a signal for Make, so the paperwork follows the member to your document storage or CRM without a manual step.

How it fires
scheduled. Make checks the app on the scenario's schedule.
When to use it
a signed waiver should be filed in a shared folder or noted on the member's CRM record.
Watch out
the doc does not say whether the trigger reports signed waivers, pending ones or both. A test with Run once tells you before a member slips through.
Modules

What can Make do in Arbox v3?

Arbox v3 gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Arbox v31

Book a trial class

ActionIn the docs only

Put a prospect into a trial session in Arbox v3 straight from a scenario, with no retyping at the front desk.

When to use it
a form on your website collects trial requests and each one should be booked right away.
Watch out
the doc lists no fields for this module, so open it after connecting and let Make show you what it asks for.
Arbox v32

Cancel a trial class booking

ActionIn the docs only

Remove a trial class booking in Arbox v3 when the prospect changes plans, so the spot goes back to people who will show up.

When to use it
the person answers a reminder saying they cannot come after all.
Watch out
test it on a booking created for the purpose, since running it on a live one cancels a real visitor.
Arbox v33

Cancel a user booking

ActionIn the docs only

This action cancels a member's booking in Arbox v3 from a scenario, which saves the front desk a trip into the schedule.

When to use it
a member asks to drop out through a form or a message handled by another app.
Watch out
the cancellation may come back through Watch user cancel registration, so keep that trigger in a different scenario.
Arbox v34

Create a client

ActionIn the docs only

Add a new client to Arbox v3 from data collected elsewhere, a signup form or a payment tool, instead of copying it by hand.

When to use it
someone signs up online and should exist in Arbox v3 before their first visit.
Watch out
the doc says nothing about duplicates, so test what happens when the same person signs up twice.
Arbox v35

Create a lead

ActionIn the docs only

Drop a prospect into Arbox v3 as a lead the moment another app captures them, so sales works from a single list.

When to use it
an ad form or a website contact form should feed the Arbox v3 pipeline directly.
Watch out
leads you create here will reach Watch new lead too, so do not watch leads in the same scenario.
Arbox v36

Create a membership

ActionIn the docs only

Open a membership in Arbox v3 from a scenario, which ties a sale made elsewhere to the member's account without admin work.

When to use it
a payment confirmed in an online shop should activate the matching membership.
Watch out
the doc does not describe the fields, so run the module once on a test member before connecting real payments.
Arbox v37

Create a task

ActionIn the docs only

Give someone on the team a to-do inside Arbox v3, generated by whatever just happened in the scenario.

When to use it
a new lead just came in, a credit was refused, or a medical certificate needs a human to check it.
Watch out
tasks created here also start Watch new task, so a scenario that creates tasks should not watch them as well.
Arbox v38

Get a schedule

ActionIn the docs only

Read the schedule from Arbox v3 so the next modules can reuse it, in a message, a sheet or another calendar.

When to use it
a coach wants the upcoming sessions sent to them, or a website page should display them.
Watch out
reading a schedule still costs an operation, and the doc does not say how much of the schedule comes back, so test it first.
Arbox v39

Get a users

ActionIn the docs only

Fetch user information from Arbox v3 in the middle of a scenario, to complete a record before the next step uses it.

When to use it
a trigger gives you little detail and the following module needs more about the person.
Watch out
the doc does not say whether it returns one user or a list, so read the bundles after Run once before mapping.
Arbox v310

Make an API call

ActionIn the docs only

Reach any endpoint of the Arbox v3 API with the connection you already set up, for everything the other modules do not cover.

When to use it
you need an Arbox v3 feature that none of the 39 modules on this page handles.
Watch out
you write the request yourself, so keep the Arbox v3 API documentation open while you set it up.
Arbox v311

Mark a lead as lost

ActionIn the docs only

Close a lead in Arbox v3 as lost from a scenario, so the pipeline reflects reality without someone cleaning it up by hand.

When to use it
a prospect replies that they are not interested, or a reminder sequence in another tool ends without an answer.
Watch out
the lead will then appear in Watch lost leads, so plan that scenario accordingly.
Arbox v312

Send a Message

ActionIn the docs only

Send a message through Arbox v3 from a scenario, triggered by a booking, a renewal or any event another app reports.

When to use it
a trial visitor should hear from the club before the class, without anyone typing the text.
Watch out
the doc does not say which channel the message uses, so send one to yourself with Run once before reaching real members.
Arbox v313

Update lead status

ActionIn the docs only

Move a lead to another status in Arbox v3 when something happens outside the app, so sales sees the real stage.

When to use it
a prospect books a call in your scheduling tool and should move forward in Arbox v3.
Watch out
the change feeds Watch updated Lead statuses, so never run that trigger and this action in one scenario.
Need help

Need help automating Arbox v3 with Make?

A person reads every message.

FAQ

Arbox v3 and Make: common questions

01Is the Arbox v3 Make integration free?
Yes, Arbox v3 is a standard app, available from the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the minimum interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution, with usage counted in credits per month. Your Arbox subscription is separate: you still need an active Arbox account to connect.
02What do you need to connect Arbox v3 to Make?
You need an active Arbox account and its API key. In Arbox v3, open Settings, click Club Information and copy the key shown on screen. In Make, add any Arbox v3 module, click Create a connection, give the connection a name if you like, then paste the key or follow the instructions on screen. That connection is created once and reused by all 39 modules of the app, triggers and actions alike.
03Does the Arbox v3 trigger fire in real time in Make?
No. All 26 Arbox v3 triggers are scheduled: Make checks the app on the scenario's schedule instead of receiving an alert. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval allowed; paid plans can go down to 1 minute. Anything that happens in Arbox v3 between two checks is picked up at the next run, one bundle per item, and each module that processes it counts one operation.
04What if the Arbox v3 module you need is missing?
Use Make an API call. It reaches any endpoint of the Arbox v3 API with the same connection as the other modules, so you are not limited to the 13 actions listed. Keep in mind that the official doc lists the modules without descriptions and states that its content is AI-generated and may contain mistakes. When a module behaves differently from what you expect, contact Arbox v3 directly and test each step with Run once.
05Should you pick Make or n8n for Arbox v3?
It depends on where your automations already live. On Make, Arbox v3 comes with 39 ready modules, a single connection and a visual editor where you test each step with Run once. Many apps also have an n8n node, so check whether the Arbox v3 features you need exist there before comparing. Pick the tool your team already uses for its other scenarios, and choose on the modules you actually need rather than on the total count.
Same platform

Other docs you might need on this stack.

Browse all integrations