Acuity Scheduling

**Overall judgment**: Strong, production-oriented Acuity Scheduling integration that exposes most of the platform’s useful surface area (appointments, availability, calendars, clients, blocks, forms, labels). Well-suited for assistants that need to handle real scheduling workflows end-to-end for users already on Acuity. **Key strengths** - Comprehensive coverage of scheduling operations: create/update/cancel/reschedule appointments, check availability by date and appointment type, manage calendars and client records. - Managed OAuth via Maton with explicit connection management APIs, enabling multi-account setups where the host environment can maintain one or more Acuity connections. - Clear HTTP/JSON design and strong documentation, including concrete examples in Python and JavaScript and explicit error-handling guidance. **Risks and limitations** - Requires a valid MATON_API_KEY and external Maton + Acuity services; outages or misconfiguration in either will break functionality. - Connection management and header selection (Maton-Connection) add some operational complexity and must be carefully wired into the host environment. - Operates directly on live scheduling data (including cancelling/rescheduling and modifying clients), so incorrect prompts or logic can have real business impact; additional guardrails and confirmation flows are advisable, particularly in sensitive domains (e.g., healthcare). **Recommended scenarios** - Assistants used by businesses that already rely on Acuity Scheduling as their primary booking system and want chat-based booking, rescheduling, and cancellation. - Internal tools or agents that need to surface staff availability and manage appointment blocks (e.g., lunch breaks, out-of-office) programmatically. - Multi-tenant assistants where the platform can manage separate Acuity connections per business via the Maton connection APIs, and route each user to the correct connection using the `Maton-Connection` header.