Review Event Orders
Read an event and its filtered order records.
/oo Ticket Tailor: Read Ticket Tailor event [event ID], list its orders with status [status], and summarize returned order records.
Read events, filter ticket orders, and inspect issued tickets for a box-office briefing. Ask your connected AI assistant to explain the results or carry out the specified operation.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Read an event and its filtered order records.
/oo Ticket Tailor: Read Ticket Tailor event [event ID], list its orders with status [status], and summarize returned order records.
Read a ticket’s current record for a specific order or event.
/oo Ticket Tailor: List Ticket Tailor issued tickets for event [event ID], then read ticket [ticket ID] and summarize returned ticket status.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect with a Ticket Tailor box-office API key.
Connect Ticket Tailor →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
Ticket Tailor connects supported service operations to your AI assistant. Read events, filter ticket orders, and inspect issued tickets for a box-office briefing.
Read event catalog and order records.
List and read issued ticket records.
List events belonging to the connected Ticket Tailor box office.
ticket_tailor.list_events Retrieve one event belonging to the connected Ticket Tailor box office.
ticket_tailor.get_event List orders belonging to the connected Ticket Tailor box office.
ticket_tailor.list_orders Retrieve one order belonging to the connected Ticket Tailor box office.
ticket_tailor.get_order List tickets issued by the connected Ticket Tailor box office.
ticket_tailor.list_issued_tickets Retrieve one issued ticket from the connected Ticket Tailor box office.
ticket_tailor.get_issued_ticket No matching tools.
Order lists support email along with event, status, and date filters.
The current actions read events, orders, and issued tickets.
Use starting_after or ending_before with the returned cursor identifiers.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.