Acuity Scheduling connector
Set up the Acuity Scheduling connector in Kaivo: authentication, configuration, the 7 BigQuery tables it syncs, and answers to common questions.
Acuity Scheduling connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Acuity Scheduling data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your customer support data instead of moving it.
What is the Acuity Scheduling connector
Section titled “What is the Acuity Scheduling connector”Sync your Acuity Scheduling appointments and clients into BigQuery with Kaivo to analyse bookings, no-shows, and demand across your services.
| Category | Customer Service |
|---|---|
| Authentication | Username and password |
| Setup | Self-service |
Getting started with the Acuity Scheduling connector
Section titled “Getting started with the Acuity Scheduling connector”- Sign up for Kaivo and create a workspace.
- Connect your Acuity Scheduling account.
- Choose which tables to sync.
- Wait for the initial sync to finish.
- Query your data in BigQuery or your favourite AI or BI tool.
Authenticating Acuity Scheduling
Section titled “Authenticating Acuity Scheduling”Connect with your Acuity Scheduling login. You provide:
| Field | Description |
|---|---|
| Password | |
| Your Acuity API Key, found under Settings → Integrations → API. |
|
Configuring the Acuity Scheduling connector
Section titled “Configuring the Acuity Scheduling connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| Username | |
| Your Acuity User ID, found under Settings → Integrations → API. |
| | Start Date |
Any data before this date will not be fetched.
|
Tables and columns synced from Acuity Scheduling
Section titled “Tables and columns synced from Acuity Scheduling”Kaivo syncs 7 tables from Acuity Scheduling into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
appointment-types (16 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
type |
STRING |
|
description |
STRING |
|
active |
BOOL |
|
category |
STRING |
|
color |
STRING |
|
duration |
FLOAT64 |
|
id |
FLOAT64 |
|
image |
STRING |
|
name |
STRING |
|
padding_after |
FLOAT64 |
|
padding_before |
FLOAT64 |
|
price |
STRING |
|
private |
BOOL |
|
scheduling_url |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: appointment-types__addon_i_ds
Section titled “Subtable: appointment-types__addon_i_ds”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: appointment-types__calendar_i_ds
Section titled “Subtable: appointment-types__calendar_i_ds”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
FLOAT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: appointment-types__form_i_ds
Section titled “Subtable: appointment-types__form_i_ds”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
FLOAT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
appointments (34 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
type |
STRING |
|
amount_paid |
STRING |
|
appointment_type_id |
FLOAT64 |
|
calendar |
STRING |
|
calendar_id |
FLOAT64 |
|
calendar_timezone |
STRING |
|
can_client_cancel |
BOOL |
|
can_client_reschedule |
BOOL |
|
canceled |
BOOL |
|
category |
STRING |
|
confirmation_page |
STRING |
|
confirmation_page_payment_link |
STRING |
|
date |
STRING |
|
date_created |
STRING |
|
datetime |
STRING |
|
datetime_created |
STRING |
|
duration |
STRING |
|
email |
STRING |
|
end_time |
STRING |
|
first_name |
STRING |
|
forms_text |
STRING |
|
id |
FLOAT64 |
|
insert_date |
STRING |
|
last_name |
STRING |
|
location |
STRING |
|
notes |
STRING |
|
paid |
STRING |
|
phone |
STRING |
|
price |
STRING |
|
price_sold |
STRING |
|
time |
STRING |
|
timezone |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: appointments__addon_i_ds
Section titled “Subtable: appointments__addon_i_ds”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: appointments__forms
Section titled “Subtable: appointments__forms”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
FLOAT64 |
|
name |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: appointments__forms__values
Section titled “Subtable: appointments__forms__values”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
field_id |
FLOAT64 |
|
id |
FLOAT64 |
|
name |
STRING |
|
value |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
blocks (12 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
description |
STRING |
|
calendar_id |
FLOAT64 |
|
calendar_timezone |
STRING |
|
end |
STRING |
|
id |
FLOAT64 |
|
insert_date |
STRING |
|
managed |
BOOL |
|
notes |
STRING |
|
service_group_id |
FLOAT64 |
|
start |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
calendars (11 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
description |
STRING |
|
email |
STRING |
|
id |
FLOAT64 |
|
image |
BOOL |
|
location |
STRING |
|
name |
STRING |
|
reply_to |
STRING |
|
thumbnail |
BOOL |
|
timezone |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
clients (7 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
email |
STRING |
|
first_name |
STRING |
|
last_name |
STRING |
|
notes |
STRING |
|
phone |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
forms (6 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
description |
STRING |
|
hidden |
BOOL |
|
id |
FLOAT64 |
|
name |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: forms__appointment_type_i_ds
Section titled “Subtable: forms__appointment_type_i_ds”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
FLOAT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: forms__fields
Section titled “Subtable: forms__fields”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
type |
STRING |
|
id |
FLOAT64 |
|
lines |
FLOAT64 |
|
name |
STRING |
|
required |
BOOL |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
labels (5 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
color |
STRING |
|
id |
FLOAT64 |
|
name |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Acuity Scheduling sync works
Section titled “How the Acuity Scheduling sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Acuity Scheduling supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.
Frequently asked questions
Section titled “Frequently asked questions”How long does the initial sync take for Acuity Scheduling?
Section titled “How long does the initial sync take for Acuity Scheduling?”It depends on how much history is in your Acuity Scheduling account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.
Can I sync only some tables or columns?
Section titled “Can I sync only some tables or columns?”Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.
What happens when Acuity Scheduling’s schema changes?
Section titled “What happens when Acuity Scheduling’s schema changes?”New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Acuity Scheduling, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.
How do I handle GDPR or data deletion requests?
Section titled “How do I handle GDPR or data deletion requests?”Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Acuity Scheduling instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Acuity Scheduling connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Acuity Scheduling data
Section titled “Common use cases for Acuity Scheduling data”Booking trends
Section titled “Booking trends”Aggregate appointments by date, type, and calendar to see demand patterns and busy periods.
Service mix
Section titled “Service mix”Use appointment-types to see which services book most and which drive repeat visits.
Client analysis
Section titled “Client analysis”Join clients with appointments to find repeat customers and lapsed ones to win back.
Capacity planning
Section titled “Capacity planning”Compare bookings against blocks and calendars to spot underused time and staff.
Use Acuity Scheduling data in your AI and BI tools
Section titled “Use Acuity Scheduling data in your AI and BI tools”Once Acuity Scheduling data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Acuity Scheduling data.
Claude
Section titled “Claude”Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →
Power BI
Section titled “Power BI”Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →
Data Studio
Section titled “Data Studio”Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →
Tableau
Section titled “Tableau”The premium analytics standard, with native BigQuery integration. Setup guide →
Google Sheets
Section titled “Google Sheets”Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →
Connect via Power Query’s BigQuery connector. Setup guide →
Metabase
Section titled “Metabase”Open-source BI tool with strong BigQuery support. Setup guide →
See our pricing page for Acuity Scheduling connector pricing and plan details.