eventbrite

Eventbrite API integration with managed OAuth. Manage events, venues, ticket classes, orders, and attendees. Use this skill when users want to create and manage events, check orders, view attendees, or access event categories. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. 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 the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app 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 Eventbrite connection into automation, in the order they are used: the connection (the first step), a hosted function that runs an Eventbrite 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 Eventbrite examples; they add no Eventbrite capability - Eventbrite is not an event source, a trigger cannot read Eventbrite 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).

Before installing, understand that this skill can manage real Eventbrite business data and can create persistent automation if you approve it. Use the read/list commands first, confirm every write or automation step, keep connections scoped to the intended account, and avoid the raw API-key fallback unless the CLI cannot be used.