acuity-scheduling

Acuity Scheduling API integration with managed OAuth. Manage appointments, calendars, clients, and availability. Use this skill when users want to schedule, reschedule, or cancel appointments, check availability, or manage clients and calendars. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which Acuity enforces on every request; the endpoints documented here are the ones this skill uses, and any other Acuity endpoint needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn an Acuity Scheduling connection into automation, in the order they are used: the connection (the first step), a hosted function that runs an Acuity Scheduling action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Acuity Scheduling examples; they add no Acuity Scheduling capability - Acuity Scheduling is not an event source, a trigger cannot read Acuity Scheduling data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

Install only if you intend to let Maton access your Acuity Scheduling account. Approve the OAuth connection deliberately, review every create/update/delete action before it runs, and be especially careful with hosted functions, triggers, or destination URLs because they can run or forward data continuously until removed.