Checkin

<usecase>Compare multiple events or view revenue across all events. Two modes: 'compare' (default) for side-by-side metrics of 2-10 specific events, 'revenue_overview' for organization-wide revenue breakdown by event.</usecase><instructions>For 'compare' mode: provide eventIds (list of 2-10 event IDs). Returns per-event: orders, tickets sold, check-in rate, no-show rate, revenue, avg order value. For 'revenue_overview' mode: returns per-event revenue across events with pagination. This connection may cover several organizations (a parent and its subunits); most cover only one. Both modes work across all authorized organizations — 'compare' can mix events from different organizations, and 'revenue_overview' aggregates across all authorized organizations by default. Every event is tagged with organizationId and organizationName. Pass organizationIds to restrict revenue_overview to specific organizations. Use find-events() first to discover event IDs.</instructions>

compare-events

<usecase>Check-in monitoring and attendance analysis for an event. Auto-detects whether the event is live (shows real-time dashboard) or past (shows no-show/late arrival analysis). Override with the 'mode' parameter. Check-in = attendees having their ticket/badge verified at a physical entrance gate.</usecase><instructions>'live' mode: shows check-in rate, per-ticket-type breakdown, entrance gate stats, check-in timeline (counts per time bucket), and recent individual check-ins. 'post_event' mode: shows no-show count/rate, late arrivals (checked in after event start), and per-ticket-type no-show breakdown. Mode is auto-detected from event dates if not specified.</instructions>

event-check-in

<usecase>Get a comprehensive dashboard for a single event. Returns headline metrics (orders, attendees, check-in rate, revenue, capacity) plus full event configuration in 'eventDetails': event type (EVENT/TICKETS/COURSE/HYBRID/ONLINE/ELEARNING/BOOKING), location, registration window, enabled payment methods (card, Vipps (Norwegian mobile payment), Swish (Swedish mobile payment), invoice, pay-at-door), seat map settings, ticket delivery (email/SMS), booking/accommodation config, and invoice settings. Optionally include deeper sections: sales velocity/forecast, waitlist status, or full post-event analysis.</usecase><instructions>Use 'include' to add sections: 'velocity' (run rate, projected sell-out), 'waitlist' (per-ticket-type waitlist counts), 'post_event' (no-shows, top tickets/add-ons/coupons, hourly check-in curve, payment collection). Add-ons are optional extras purchased alongside tickets (e.g., parking, meals, t-shirts). Multiple values can be comma-separated. Without 'include', returns the core summary which is fast and token-efficient.</instructions>

event-dashboard

<usecase>Financial health overview for an event: payment status breakdown, aging buckets for outstanding amounts, and optionally abandoned/incomplete orders.</usecase><instructions>Always returns payment status counts and aging buckets for unpaid orders. Add include='abandoned_orders' to also list orders that were started but never completed (statuses: pending, waiting_payment, etc.) with potential revenue loss.</instructions>

event-finances

<usecase>Detailed sales analysis for a single event. Supports four focus areas: revenue overview (default), time-series trends, add-on performance, and discount/coupon analysis. Add-ons are optional extra products buyers can purchase alongside tickets (e.g., parking, meals, t-shirts).</usecase><instructions>Set 'focus' to choose the analysis type: 'overview' (default) — revenue breakdown by ticket type + add-on totals. 'time_series' — ticket sales grouped by day/week/month with cumulative totals. 'addons' — per-add-on quantity, revenue, and attachment rate. 'discounts' — coupon usage, discount-to-revenue ratio, manual discounts. Date filters (fromDate/toDate in YYYY-MM-DD) apply to overview and time_series.</instructions>

event-sales

<usecase>Search and list attendees for a specific event. Supports filtering by name/email, ticket type, and check-in status. Optionally include anonymized answer counts for the event's custom fields (dietary, accessibility, etc.).</usecase><instructions>PII is masked by default (initials + masked email). Use format='detailed' for full names/emails. Add include='answerBreakdown' for an anonymized count of how attendees answered each custom field (grouped by field and answer; no names — good for catering/logistics. Predefined choice options are always counted; free-text values are personal data and are listed only with format='detailed'). To read individual attendees' custom-field (additional) answers, first call with include='fieldCatalog' to discover the event's fields, then pass attendeeFields=[...] (field names or ids) to attach only those answers to each attendee — avoid requesting fields you don't need. Answer values count as personal data and are shown only with format='detailed' (like full names/emails). Use find-contacts(search) instead if you need cross-event contact history.</instructions>

find-attendees

<usecase>Look up contacts by name, email, or phone. Returns contact details and their registration history across all events (events attended, total spend, recent events).</usecase><instructions>Provide either a search term (min 2 characters) or a contactId for exact lookup. Returns up to 10 contacts by default. PII is masked by default — use format='detailed' for full names, emails, and phone numbers. Use contactId for exact lookup if you already have a contact ID. Use find-attendees(eventId, search) instead to search within a specific event. This connection may cover several organizations (a parent and its subunits); most cover only one. By default contacts from ALL authorized organizations are searched, each tagged with organizationId and organizationName. Pass organizationIds to restrict to specific organizations — call list-organizations() first to see which ones are available.</instructions>

find-contacts

<usecase>Find and list events for your organization. This is the starting point for most workflows — use it to discover event IDs before drilling into details with other tools.</usecase><instructions>Filters: period (upcoming/live/past/all), search by name, include unpublished drafts. Results are sorted by start date (newest first by default). Each result includes event ID, name, dates, registration window, location, event type (EVENT = standard/default event type (not booking, and not classified as online or hybrid), TICKETS = anonymous tickets, COURSE = multi-session, HYBRID = physical+online, ONLINE = digital-only, ELEARNING = self-paced, BOOKING = accommodation/resource reservation), organizer, and order count. Each result also includes a 'visibility' object showing where the event is listed (showInEventCalendar, showInEmbeddedCalendar, showOnLandingPage, showInGlobalSearch, showInCheckinSearch, and isHiddenEverywhere when none are enabled) plus isCancelled/cancelledAt. Use these to distinguish events hidden from the public calendar (e.g. duplicate events for extra rooms/halls) from publicly listed ones. This connection may cover several organizations (a parent and its subunits); most cover only one. By default events from ALL authorized organizations are returned, each tagged with organizationId and organizationName. Pass organizationIds to restrict to specific organizations — call list-organizations() first to see which ones are available.</instructions>

find-events

<usecase>Search and list orders for a specific event. Use this to find individual orders by contact name, email, invoice reference, or payment status.</usecase><instructions>Filters: search (name/email/invoice reference), paymentStatus (done, pending, waiting_payment), unpaidOnly (outstanding balance > 0), includeCancelled. PII is masked by default. Use format='detailed' for full contact info. To read order-level custom-field (additional) answers, first call with include='fieldCatalog' to discover the event's order-level fields, then pass orderFields=[...] (field names or ids) to attach only those answers to each order — avoid requesting fields you don't need. Answer values count as personal data and are shown only with format='detailed'. (Per-attendee fields live in find-attendees.) Use event-finances(eventId) instead for aggregate payment status overview.</instructions>

find-orders

<usecase>List the organizations this connection can access. A single connection may cover one organization (the common case) or a parent organization together with its subunits. Call this first when a request is about a specific organization, or when you need to know whether more than one organization is in scope.</usecase><instructions>Takes no parameters — it always returns exactly the organizations the connection is authorized for. Each entry includes organizationId, name, organizationType (organization/company/charity/subunit), isPrimaryConsentOrganization (the organization consent was granted to), parentOrganizationId/Name, and directSubunitCount. Pass an organizationId from these results to other tools via their organizationIds parameter to scope a query to specific organizations. Organization structures are at most one level deep: an organization is either standalone, a parent (has subunits), or a subunit (has a parent) — never both a parent and a subunit.</instructions>

list-organizations