add_booking
ChatGPTPut an artist on an event's booking wishlist (status WANTED). Needs ids from search_events and search_people. The artist sees the wish in their portal (bell; e-mail if they have a login).
assign_pos_products
ChatGPTPut existing catalog products on a register (add) or take them off it (remove). Takes effect on the terminal with its next load; products stay in the catalog.
assign_shift
ChatGPTPut a person (EMPLOYEE/VOLUNTEER) on a shift, or personId null to free it. The person is notified.
complete_todo
ChatGPTMark a task as done (moves it into the board's done column; linked rider items count as provided).
copy_cost_positions
ChatGPTTake over the plan positions of another event of the organisation (e.g. last year's) — titles, categories, planned amounts and notes, never invoices or actuals. Appended to the existing positions (copying twice duplicates). Always needs a confirmation.
create_artist
ChatGPTCreate an artist (passive person without login) in the organisation. Refuses when an artist with the same name exists — then ask the user whether they mean that one; set allowDuplicate only after they say it is a different person.
create_cost_category
ChatGPTCreate a cost category. Categories belong to the whole organisation (every event's budget). The description tells the app's invoice reading what lands there — keep categories clearly distinct. Check get_budget first so you do not create a near-duplicate.
create_cost_positions
ChatGPTAdd plan positions to an event's cost plan (budget), e.g. a whole budget you drafted with the user. Each position needs a title and a categoryId from get_budget; plannedEur is the gross budget. All or nothing. Show the plan to the user first; more than 5 positions need a confirmation. Actuals come from invoices, never from positions.
create_guest_invite
ChatGPTCreate a one-time invite link for ONE spot on a guest list (reserves the spot). The guest opens it, enters their own data and gets the QR pass by mail. The link gives access to that spot — share it only with the intended guest.
create_guestlist
ChatGPTCreate a guest list at an event and get its public link: the holder adds guests or sends invites there; every guest gets a QR pass by mail. Optional recipientId (from search_people) = the person the list belongs to; one list per person and event — if one exists, its link is returned instead. The link gives full access to the list — share it only with the intended holder.
create_income_line
ChatGPTAdd an income position to an event's budget (sponsoring, grants, bar settlement, tickets sold elsewhere): planned and actual gross in euros, never negative. Live ticket-shop and POS revenue come in automatically — do not add them here.
create_invoice
ChatGPTFile an invoice the user shared with you (photo/PDF) in an event's cost planner. You read it yourself — this connection cannot receive files — and pass the values exactly as printed; never invent missing ones, ask instead. Cost side: pick the category (and the plan position, if one clearly fits) from get_budget; side INCOME = an invoice the organiser issued (sponsoring, fees), no category. With a gross amount (and a category on the cost side) it is booked at once, otherwise it waits for review in the app. Check list_invoices first so it is not filed twice. The original file is not stored: when the user uploads it later in the app, it is attached to this invoice automatically.
create_pos_products
ChatGPTAdd products to an event's bar/POS catalog and put them on registers right away. A product whose name already exists in the catalog is not created again — it comes back under "exists"; put it on a register with assign_pos_products. Negative price = deposit return (e.g. -2).
create_shifts
ChatGPTCreate shifts in a work area. count = parallel positions with the same time (open shifts staff can apply for). More than 5 shifts need a confirmation. Ask the user for missing times; never assume them.
create_stage
ChatGPTAdd a stage / floor (e.g. Mainfloor) to an event's timetable. Read get_timetable first — an existing name is returned instead of a duplicate.
create_timeslots
ChatGPTAdd slots to an event's timetable. Each slot: stageId, startTime/endTime and exactly one of artistId (artist with a CONFIRMED booking), groupId (band with a CONFIRMED booking), title (own programme item, e.g. "Opening") — or none for an open slot artists can apply for. Read get_timetable first and show the user the planned running order (stage, times) before creating it. Overlaps on a stage are refused. More than 5 slots need a confirmation. Artists are not notified.
create_todo
ChatGPTCreate a task on the event's task board (first column, at the bottom). Assignees are team (backoffice) members — ask the user who if unclear; their ids are in get_context (team).
create_work_area
ChatGPTAdd a work area / location to staff (e.g. Bar, Einlass) to an event. Check list_shifts first — it refuses an existing name.
delete_booking
ChatGPTDelete ONE booking with its documents, rider and unsigned contracts. Always needs a confirmation. Refused when a signed contract exists (cancel instead).
delete_cost_position
ChatGPTDelete ONE plan position. Its invoices stay booked on the category. Always needs a confirmation.
delete_income_line
ChatGPTDelete ONE income position. Always needs a confirmation.
delete_invoice
ChatGPTDelete ONE invoice incl. its stored file. Always needs a confirmation.
delete_shift
ChatGPTDelete ONE shift. Always needs a confirmation; the assigned person loses it (and the automatic guest list slot).
delete_todo
ChatGPTDelete ONE task with its comments and attachments. Always needs a confirmation.
get_booking_details
ChatGPTEverything about one booking as on its settlement and contract tabs: fee and deal terms, payment plan (paid / open), settlement (ticket figures from the shop or manual, payout, § 50a withholding — estimates), linked invoices (with the costs permission), current contract (status, counterparty, signatures, deadlines; full text with includeContractText) and the contract history.
get_budget
ChatGPTCost planner of one event as in the app: cost categories with plan/actual, positions, booking fees, booked invoices, rider costs still without a position, income (lines + income invoices, e.g. sponsoring, grants), live ticket/POS revenue and the totals. Cost diff negative = over budget; income diff negative = below target. Sponsoring has no own model — it appears as income lines or income invoices. Carries the ids the cost planner write tools take (categories, positions, invoices, income lines).
get_checkin_status
ChatGPTAdmission of one event so far: shop tickets checked in / valid and guest-list guests checked in / total (each part only with the shop resp. guestlist permission).
get_context
ChatGPTWho you act as: organisation, user name, the permissions of this connection and the team (backoffice members, e.g. task assignees). Call it first in a conversation.
get_credits
ChatGPTCredit wallet of the organisation (1 credit ≈ 1 cent; paid features like AI helpers or larger ticket volumes use them). Balance for every member; with the credits permission also auto top-up and the recent ledger (top-ups, spends, refunds) with totals for an optional period.
get_day_sheets
ChatGPTDay sheets of an event's confirmed acts, as printed for the crew: arrival, soundcheck, stage slots with stage managers, contact person, notes and the rider the organiser provides (hospitality, technical, what the artist brings). Fees are deliberately not part of it. Filter by performer name.
get_event_overview
ChatGPTStatus of events as on the event overview page: setup checklist, tickets sold, revenue, tasks, bookings, shifts, budget and open items — for every planned event (not over, not archived), or one event with its details (address, type, genres, capacity, description). Areas the user has no permission for are null.
get_matcher_stats
ChatGPTVisitor matcher of an event (visitors swipe the line-up in the visitor app): participants, swipes, like rate, how far they got, and per artist likes, dislikes, reach, like rate and score (95 % lower bound of the like rate — use it to rank popularity, a 9/10 beats a 1/1), per stage totals and clashes (parallel slots the same visitors liked).
get_newsletter_stats
ChatGPTNewsletter figures (read only — drafting and sending stay in the app): subscriber counts by status and sign-up source, changes in the last 30 days, and the campaigns with recipients, opens, clicks and unsubscribes.
get_nfc_stats
ChatGPTCashless wristband overview of one event: bands by status, money on the bands, top-ups (cash/card vs. online), payments, refunds, payouts and the activity of the last 24 hours. Amounts in EUR.
get_pos_sales
ChatGPTBar/POS sales of one event (completed orders, wristband top-ups and payouts excluded): revenue per payment method, products sold and the registers with their own figures. Amounts in EUR.
get_shop_order
ChatGPTOne ticket-shop order: buyer details, items, amounts, discount code, tickets (product, scan, voided) and refunds.
get_site_plan
ChatGPTSite planning of an event (power, water, fences) per assigned site map, checked like in the editor: key figures, sources with load, cable/hose metres per class, fence totals, problems (e.g. UNPOWERED, UNSUPPLIED, SOURCE_OVERLOAD, VOLTAGE_DROP, FENCE_BLOCKS_WALKWAY) and every consumer with its plug (connector) and supply state. Lengths are straight-line here (no obstacle routing) — exact values in the editor. Never claim a plan is certified or safe.
get_survey_results
ChatGPTResults of one survey per question: answer counts, averages, NPS, option distributions and the newest free-text answers. Questions carry categoryId — group them by categories like the survey pages.
get_ticket_sales
ChatGPTTicket-shop sales per event — the same figures as the shop statistics page: valid tickets (tickets), sold, refunded, scanned, orders, revenue in EUR (net = after refunds and discounts), products with stock and sell-through, payment methods, discount codes, buyer countries/cities/age groups, shop traffic (visitors → checkout → paid, devices, sources), plus totals. Without eventIds: events with sales in the period (or starting in year), at most 12. soldFrom/soldTo limit the figures to orders placed on those days. leadTime = cumulative valid tickets N days before each event's start over the whole sale (ignores soldFrom/soldTo); an upcoming event adds its daysUntilStart as a milestone for every event of the call. For "vs. last year" questions compare the editions at the SAME lead time (same daysBefore milestone) — never a finished sale's total against a running one.
get_timetable
ChatGPTTimetable of one event: stages, slots per festival day (Europe/Berlin; a set past midnight belongs to the day it starts and shows again in the next day's carryOver) and the confirmed performers with whether they already have a slot. Pass day (YYYY-MM-DD, see the weekday labels) to read one day, e.g. before planning "Saturday".
list_appointments
ChatGPTTeam calendar of the organisation: appointments with time, place, description, assigned members and external participants. Default window: today to 30 days ahead; mine = only those the user is assigned to.
list_bookings
ChatGPTBookings (wishlist → requested → confirmed / declined / cancelled) of one event — or of one artist across all events (fee history, e.g. to check a budget). Per booking: performer, status, fee (EUR), deal (null = fixed fee), current contract status (null = no contract yet; SIGNED = signed by both sides), settlement status and payments. Pass exactly one of eventId, artistId.
list_form_submissions
ChatGPTSubmissions of one form, newest first: contact details, status and every answer under its question. Uploaded files appear as file names only. Reading does not mark anything as opened.
list_forms
ChatGPTApplication forms of the organisation (Bewerbungsformulare, e.g. volunteers, food trucks, artists): linked event, open/closed, number of submissions, still NEW ones and ones you have not opened yet.
list_guestlists
ChatGPTGuest lists of one event: quota, occupied slots (guests + pending invites), active/submitted, recipient, guests (max 200 per list) with check-in state and the public list link. A list link gives full access to that list — share it only with the list's holder.
list_invoices
ChatGPTEvery invoice of one event's cost planner (cost and income side), newest first: status (UPLOADED/PROCESSING/REVIEW/CONFIRMED/FAILED — only CONFIRMED counts in the budget), supplier or recipient, number, dates, amounts, category, position, linked artist, warning flags and whether the original file is stored. Use it to find an invoice to assign or correct, and before create_invoice so nothing is filed twice.
list_pos_registers
ChatGPTBar/POS registers of one event (on/off, payment methods, wristband top-up) and the event's product catalog with price, VAT, category and the registers each product is offered on. Prices in EUR (gross).
list_rider_items
ChatGPTRider requirements of an event's bookings (technical + hospitality): what, how many, when, priority and fulfilment (OPEN / CONFIRMED / PROVIDED / UNAVAILABLE). Default scope = what the organiser has to provide (agreed items, as on the rider overview); scope "all" adds items under review, proposals and what artists bring themselves. POWER and LIGHT items are free text — the power plan's consumers and plugs are in get_site_plan.
list_shifts
ChatGPTWork areas and shifts of one event (area, times, role, assigned person, applicants from the staff portal by name).
list_shop_orders
ChatGPTTicket-shop orders of one event, newest first, 20 per page, with status counts. search matches order number, buyer name or e-mail. Use get_shop_order for items, tickets and refunds of one order.
list_suppliers
ChatGPTSuppliers (Dienstleister) of the organisation: trades, rating (TOP/OK/AVOID, null = not rated), contacts and document names. With the costs permission also the cost history per event from confirmed invoices.
list_surveys
ChatGPTVisitor surveys of the organisation (newest first): event, open/closed, question and response counts.
list_todos
ChatGPTTasks of one event with column (status), priority, due date and assignees.
search_events
ChatGPTFind events of the organisation by title (case-insensitive substring) and optional start year. Put a year mentioned by the user into year, not into query ("Bee Festival 2026" → query "Bee Festival", year 2026). Several plausible results → ask the user which one; never pick yourself.
search_people
ChatGPTFind or list people of the organisation (artists, employees, volunteers, external) by name, role and tag. Use it before creating someone and to get ids for bookings or shifts. Several matches → ask the user. With the people permission the result has contact data, social links and notes (e.g. to find incomplete contacts). Profiles have no genre field — genres only appear if the organisation uses them as tags.
set_booking_status
ChatGPTChange a booking's status. CONFIRMED adds the artist to the lineup and notifies them. DECLINED/CANCELLED need a confirmation: they void open contracts and remove the artist from lineup, slots and guest list.
set_budget_settings
ChatGPTWhich automatic sources an event's budget counts: confirmed booking fees as costs (includeBookings), live POS revenue and ticket-shop revenue as income. Only the given switches change.
set_pos_register_active
ChatGPTSwitch a bar/POS register on or off. Off = its terminal shows "closed" and takes no orders, payments or top-ups until it is switched on again; sales so far are kept.
update_cost_category
ChatGPTRename a cost category or change its description (null clears) or colour. Categories belong to the whole organisation (every event's budget). The description tells the app's invoice reading what lands there — keep categories clearly distinct.
update_cost_position
ChatGPTChange ONE plan position: title, category (moves its linked invoices along), planned gross amount or note (null clears).
update_income_line
ChatGPTChange ONE income position: title, planned or actual gross in euros, note (null clears).
update_invoice
ChatGPTAssign or correct ONE invoice: plan position (also moves it into that position's category), category, linked artist (booking), the printed values, or status — CONFIRMED books it (needs gross + category on the cost side), REVIEW takes it out of the budget again. Ids from get_budget / list_invoices / list_bookings. Changing category or position moves the amount in the budget. Several plausible positions → ask the user.
update_todo
ChatGPTChange a task's title, due date (null clears it) or assignees (replaces the list).