The Make.com integration allows you to connect CaptainBook with hundreds of external apps and automate workflows across sales, operations, marketing, finance, and customer support. This integration is available on Ultra and Corporateplans. Zapier remains available as an alternative automation platform.
Availability & Access
✅ Available on Ultra and Corporate plans
✅ Native CaptainBook app on Make.com
✅ Zapier integration also supported
How the Integration Works
CaptainBook exposes automation triggers through a secure API connection. When specific events happen in your CaptainBook account, Make.com can instantly react and execute automated scenarios across your tech stack.
To connect Make.com to CaptainBook, you will use:
Tenant ID
API Key (shown only once for security reasons)
Installation & Connection Setup
1. Install the CaptainBook App on Make.com
Log into your CaptainBook account.
Navigate to Plugins → Make.com.
Install the Make.com app.
This option is visible only if your plan supports it.
2. Retrieve Your Connection Credentials
After installation, CaptainBook will display:
Tenant ID
API Key
⚠️ Important Security Notice
The API Key is shown only once.
Store it securely immediately.
If you lose it, a new key must be regenerated, which will invalidate the previous one. Contact support if this happens to you.
These two values are required inside Make.com to authenticate your connection.
3. Connect CaptainBook Inside Make.com
Open Make.com.
Create a new Scenario.
Add a CaptainBook module as the trigger.
When prompted:
Enter your Tenant ID
Enter your API Key
Save the connection.
Your Make.com account is now securely connected to CaptainBook.
Available Triggers
You can currently trigger automations when the following events occur:
Booking confirmed
Booking cancelled
Booking rescheduled
Customer created
Diary notes updated for a slot
Liability waiver signed
And additional system events as they are rolled out
Each trigger can be connected to any action supported by Make.com, such as sending messages, creating CRM records, updating spreadsheets, or triggering internal workflows.
Common Automation Use Cases
Here are typical workflows customers build with the Make.com integration:
Sales & CRM
Create or update contacts in HubSpot, Attio, Pipedrive when a customer is created
Create deals automatically when a booking is confirmed
Operations
Notify Slack or Microsoft Teams when a booking is confirmed, cancelled, or rescheduled
Push diary note updates to operations channels
Finance
Send confirmed bookings to accounting tools
Trigger invoice creation after specific booking events
Customer Experience
Send WhatsApp or SMS messages after confirmation or rescheduling
Trigger email flows after waivers are signed
Zapier vs Make.com
If you are already using Zapier, you can connect CaptainBook in a similar way using Tenant ID and API Key. The connection logic is identical, only the automation platform changes.
For detailed Zapier setup instructions, refer to the internal guide:
“Connect CaptainBook with other apps using Zapier.”
Note that you cannot use your zapier credentials with make, you still need to install the make app in your captainbook workspace
Security & Data Protection
All connections use encrypted API authentication.
API keys are tenant-specific.
Keys can be revoked at any time.
Each regeneration immediately disables the previous key.
Make sure only trusted team members have access to integration credentials.
Troubleshooting
Connection fails
Verify that the Tenant ID and API Key were copied correctly.
Check that the key has not been regenerated.
Trigger not firing
Confirm the scenario is turned ON in Make.com.
Verify that the triggering event actually occurred in CaptainBook.
Lost API Key
Regenerate a new key from the CaptainBook integration settings. (contact support)
Update all connected scenarios with the new key.
Support
If you need help:
Contact CaptainBook support through your dashboard.
Provide your Tenant ID and the scenario name you are working on.