# Acuity Scheduling integrations: appointments

> Create an appointment in Acuity Scheduling and start a workflow when Acuity Scheduling sends “Appointment scheduled”.

**Canonical page:** https://tray.ai/connectors/acuity-scheduling-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

Acuity Scheduling is an online booking tool that lets clients pick open times, book appointments and pay, while staff manage calendars and availability. Tray.ai connects to Acuity Scheduling through the HTTP Connector, so your workflows can call the Acuity Scheduling API alongside the rest of your stack.

## Use cases

### Appointments

Read, create, and update appointments in Acuity Scheduling from any Tray.ai workflow. The Acuity Scheduling API covers calls such as list appointments and create an appointment.

- List appointments
- Create an appointment
- Update an appointment

### Availability

Read availability in Acuity Scheduling from any Tray.ai workflow. The Acuity Scheduling API covers calls such as get available dates and get available times.

- Get available dates
- Get available times

### Acuity Scheduling events

Start a Tray.ai workflow the moment something happens in Acuity Scheduling. Acuity Scheduling sends events such as appointment scheduled and appointment rescheduled to a Tray.ai webhook trigger.

- Appointment scheduled
- Appointment rescheduled
- Appointment canceled

## Challenges Tray.ai solves

### Keeping Acuity Scheduling credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Acuity Scheduling credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Acuity Scheduling API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Acuity Scheduling API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Acuity Scheduling?

Yes. Tray.ai connects to Acuity Scheduling through the HTTP Connector, which calls the Acuity Scheduling API directly. Any call the Acuity Scheduling API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Acuity Scheduling?

The Acuity Scheduling API uses basic authentication and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Acuity Scheduling connector?

Acuity Scheduling runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Acuity Scheduling connector from the Acuity Scheduling API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/