What your AI client can do
The tools, prompts and event summaries TixFin offers a connected AI client, and how it proposes changes
Once connected, your AI client sees a list of TixFin tools. You do not call them yourself: you ask in your own words ("How did the summer festival sell last week compared to the week before?") and the client picks the tools it needs. Tools that read answer at once. Tools that would change something answer with a proposal, and nothing changes until you confirm it.
Every tool runs as you, with your permissions in the project. A tool your role may not use in the dashboard is refused here too.
Always live, never cached
Every answer is read from TixFin at the moment the client asks. Sales figures, check-ins and seat maps are never taken from a copy, so two questions a minute apart can give two different numbers when tickets sold in between. Amounts reach the client in cents.
Long lists come in pages of 20; a list that has no pages stops at 50 entries with a note, and the client asks for the next page or a narrower question.
Buyers' personal data
Tools marked personal below answer with names, e-mail addresses or other personal data of your buyers, guests or
team. They work only when you allowed See buyers' personal data on the consent page and the project's
AI access setting lets AI clients see
personal data; otherwise the client is told personal data is not available. In every other answer, names, contact
details, addresses and similar fields are replaced by [masked] unless both allow it
(what is masked).
Text your buyers wrote, such as order notes, reaches the client marked as buyers' words, not as instructions.
Tools
The tables below describe the reading tools. Every tool that maps to one TixFin operation, including those that propose changes, is listed with its scope and operations in the tool reference.
Orientation
| Tool | What it reads |
|---|---|
projects_list | The projects you allowed this client. Without personal data it lists their ids, not their names. |
project_get | One project's details (personal) |
me_permissions | What this connection may do: the permissions you allowed and the projects |
Planning
| Tool | What it reads |
|---|---|
events_wizard_presets | The event presets you can start an event from |
venues_list | Your project's venues |
seatmap_templates_list | Seat map templates for a seated venue |
Events and tickets
| Tool | What it reads |
|---|---|
events_list | Your project's events |
event_get | One event |
tiers_list | An event's ticket tiers |
group_discounts_list | The project's group discounts (quantity breaks) |
lotteries_list | An event's lotteries (personal) |
Venues and seats
| Tool | What it reads |
|---|---|
seatmap_get | A seat map with its sections and seats |
seatmap_validate | Errors, warnings and hints for a seat map |
Sales
| Tool | What it reads |
|---|---|
sales_summary | An event's tickets sold, reserved and refunded with gross, refunded and net amounts, by ticket type and day, for a period of up to 400 days, and optionally a second period to compare with, such as the same weeks last year |
orders_list | Your project's orders (personal) |
order_get | One order's lines, notes and balance (personal) |
Door and attendance
| Tool | What it reads |
|---|---|
attendance_get | An event's check-ins, newest first (personal) |
checkin_lists_list | An event's check-in lists (personal) |
guest_list_links_list | An event's guest-list signup links with their counts (personal) |
Shop
| Tool | What it reads |
|---|---|
shop_pages_list | Your shop's pages |
shop_customization_get | Your shop's design settings |
Marketing
| Tool | What it reads |
|---|---|
campaign_templates_list | E-mail campaign templates for the project or an event (personal) |
campaign_preview | Who a campaign would reach, before anything is sent (personal) |
attribution_links_list | Tracking links with their visits, orders and revenue (personal) |
journeys_list | Your project's journeys (personal) |
newsletter_sync_status | The latest lines of the newsletter sync log (personal) |
Products
| Tool | What it reads |
|---|---|
products_list | Your project's products |
packages_list | Your project's packages, optionally for one season |
Reports
| Tool | What it reads |
|---|---|
reports_list | Your saved reports (personal) |
report_export | A link to the report in the dashboard, where you export it as CSV or XLSX yourself. The file never goes to the client. (personal) |
Everything else
| Tool | What it reads |
|---|---|
api_search | Finds other operations of the organiser API by words, with each one's class (read, write or money), for questions no named tool covers |
api_call | Calls one operation api_search found, under the same rules as every tool: a read answers, a write or money operation answers with a proposal |
Changes
With Make changes you confirm, the client gets tools that propose changes: events, ticket types, tiers, lotteries, venues, publishing seat maps, shop pages, new products, journeys, campaign drafts, tracking links and report runs. With Take actions that move money or reach buyers, it also gets refunds, exchanges, cancelling, postponing and deleting events, sending campaigns, guest-list links and approving their signups, creating and deleting group discounts, packages, changing a product, applying a seat map template, importing external admissions and the shop's design settings. Two changes are money proposals by what they ask: a ticket type for an event that exists already, and an event update that sets the event's refund terms, start, seat map or venue country. The tool reference lists each one.
TixFin answers these tools itself:
| Tool | What it does |
|---|---|
event_plan | One proposal for a new event: the event as a draft, its ticket types, group discounts and a hidden shop page (details) |
event_publish | Proposes putting a draft event on sale |
proposal_get | Shows a proposal's changes against the current state, and whether it is open, applied or expired |
proposal_apply | Applies a proposal once you said yes |
Some things have no tool yet, because TixFin cannot yet hold them to the projects you allowed: listing, changing and deleting ticket types (creating them works), a project's issued tickets, live seat availability, vouchers and discount actions. Use the dashboard for those.
Prompts
Many clients offer prompts as ready-made starting points, often in a menu or with /. Each asks for the project and,
where it needs one, the event.
| Prompt | What it does |
|---|---|
plan_new_event | Gathers what a new event needs from your idea, checks it against your venues, presets and similar past events, and gives you a checklist. You create the event in the dashboard. |
draft_campaign_email | A campaign email about an event from your brief, saved as a template only once you agree; sending stays a separate step |
weekly_sales_report | Sales of your events on sale over the last seven days against the seven days before, and which events sell slower |
event_wrap_up | After an event: sales by ticket type, the no-show rate and three things to keep or change |
refund_triage | Sorts an event's orders that may need a refund into due, at your discretion and none, with reasons. You refund in the dashboard. |
event_wrap_up and refund_triage read attendance and orders, so they need personal data.
Event summaries
Clients that show resources can attach an event's summary to the conversation as tixfin://projects/{projectId}/events/{eventId}.
It is read live each time, like every tool.