--- title: "Ticket Tailor Integration" description: "Read Ticket Tailor box office data with AI agents. Agents sync orders and attendee lists into a CRM or warehouse, look up individual orders and issued tickets for support and check-in, and report on sales across events and recurring series." url: https://flowrunner.ai/integrations/ticket-tailor date_modified: 2026-08-04T10:04:16-07:00 --- # Ticket Tailor [Scheduling](https://flowrunner.ai/integrations/category/project-management-productivity) Read Ticket Tailor box office data with AI agents. Agents sync orders and attendee lists into a CRM or warehouse, look up individual orders and issued tickets for support and check-in, and report on sales across events and recurring series. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 7 actions · Basic auth · available [Ticket Tailor website](https://tickettailor.com/) · [Platform Documentation](https://developers.tickettailor.com/) · Capability data verified 2026-07-27 1. A nightly schedule fires ahead of tomorrow's event 2. Get Event pulls the event's ticket types, availability, and sales totals 3. List Orders scoped to the event collects every buyer, total, and payment status 4. List Issued Tickets builds the attendee roster with barcodes and check-in status 5. The agent flags anomalies, duplicate holders, unpaid orders, or ticket counts that disagree with order totals 6. The event manager reviews the flagged orders and decides which buyers get contacted before doors open 7. The clean roster lands in the check-in tool and a sales summary posts to the team channel ## What This Integration Enables Ticket Tailor keeps the box office simple and flat-fee, which is exactly why the data work around it tends to be manual: CSV exports, copy-pasted rosters, per-event sales tallies. This connector makes the box office queryable from inside your workflows. FlowRunner agents sync orders and attendees into the CRM or warehouse continuously, assemble check-in rosters keyed by barcode, answer buyer support questions with the actual order in hand, and report sales across single events and recurring series without anyone exporting anything. - Sync buyers, totals, and line items into CRM, sheets, or warehouse on a schedule - Build check-in rosters from issued tickets with holder, ticket type, and barcode - Resolve support requests with full order detail, custom checkout answers included - Report sales across events and recurring series from live data - Reconcile issued tickets against orders to catch discrepancies before event day Event operations reward exactly this kind of orchestration because everything converges on a hard deadline. The roster, the sales report, and the support queue are separate chores on a normal week and a single compounding crisis on event day. FlowRunner keeps them as one coordinated system: the same live data feeds the check-in tool, the finance sheet, and the support drafts, and the [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) gate ensures the one action with real blast radius, messaging the whole attendee list, never happens on autopilot. The box office stays simple; the operation around it stops being manual. ### Without FlowRunner **Roster exports the night before**: Someone downloads a CSV at 11pm and hopes nothing sells between export and doors **Sales reporting per event, by hand**: Each event's numbers get compiled separately, and series-level trends stay invisible **Support lookups mean logging in**: A buyer emails about their order and the reply waits until someone opens the box office ### With FlowRunner **Rosters stay live until doors**: Agents re-pull issued tickets on a schedule so late sales and changes are always included **Sales roll up across the whole series**: Orders flow into one sheet with event, occurrence, and ticket type dimensions intact **Order context arrives with the question**: Agents fetch the buyer's order and tickets the moment a support message lands ## Use Case Scenarios ### The daily sales report that covers every event at once Each morning an agent calls List Events for active events, then List Orders per event, and appends buyer, total, currency, and status rows to [Google Sheets](https://flowrunner.ai/integrations/google-sheets). For recurring programs, List Event Series keeps occurrences grouped under their parent, so the weekly workshop reads as one trendline instead of twelve unrelated events. A summary posts to [Slack](https://flowrunner.ai/integrations/slack): last night's sales by event, slowest seller flagged. The organizer sees the whole box office in ninety seconds over coffee. ### A check-in roster that is never stale The evening before an event, an agent pulls List Issued Tickets scoped to the event and writes each attendee into [Airtable](https://flowrunner.ai/integrations/airtable) with name, ticket type, barcode, and check-in status. It re-runs every hour until doors, so the buyer who purchased at 6:40pm is on the roster at 7:00. Duplicate holder emails and tickets attached to unpaid orders get flagged for the event manager before they become an awkward conversation at the door. ### Support replies with the order already open A buyer emails asking why they got charged twice. The agent searches recent orders with List Orders, pulls the candidate with Get Order, and drafts a reply in [Gmail](https://flowrunner.ai/integrations/gmail-service) with the actual line items, totals, and payment status quoted, plus the issued tickets from Get Issued Ticket so the buyer can be told exactly what is valid at the door. A person reviews the draft before it sends. The buyer gets a precise answer in minutes instead of a "we will look into it" that takes two days. ## Human-in-Loop Highlight List Issued Tickets is a read, but what it returns is the entire attendee list: names, emails, and barcodes for everyone who trusted your box office with their details. Every workflow built on it inherits that blast radius, because the natural next step after pulling a roster is contacting it. A venue change, a cancellation, a schedule shift: the agent can pull the affected event with Get Event, assemble the recipient list from issued tickets, and draft the announcement in minutes. What it does not do is send. The event manager sees "214 issued tickets across 187 orders for Saturday's show. Draft venue-change notice attached. Send to all holders?" and reads the draft as an attendee would before approving, because a wrong or premature message to a full attendee list cannot be pulled back, and refund conversations sparked by a botched announcement cost real money. The agent compiles at machine speed. The message to two hundred inboxes waits for one person. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 7 actions ### Events 3 - **List Events** Lists box office events, most recent first, with schedule, venue, ticket types, and sales status. Cursor-paginated with Limit and Starting After. The discovery step behind reporting and event pickers. - **Get Event** Retrieves a single event's full details, including ticket types with prices and availability plus sales totals. Used to check capacity and sales before event-day workflows run. - **List Event Series** Lists recurring event series, each grouping its individual occurrences under a parent. The step that lets weekly classes and repeating shows report as one program instead of scattered events. ### Orders 2 - **List Orders** Lists orders, most recent first, optionally filtered to a single event. Each order carries buyer details, line items, totals, currency, status, and the tickets it produced. The backbone of sales sync and reconciliation. - **Get Order** Retrieves one order in full, including custom checkout questions and payment status. The support workhorse when a buyer writes in about a charge or a missing ticket. ### Issued Tickets 2 - **List Issued Tickets** Lists individual attendee tickets, optionally scoped to one event, with holder details, ticket type, barcode, and check-in status. The roster builder, and the read whose downstream sends this page's human gate governs. - **Get Issued Ticket** Retrieves a single issued ticket with the holder's name and email, barcode, check-in status, custom question answers, and parent order and event. Used for door-side lookups and single-attendee support. ## Frequently Asked Questions ### What can FlowRunner do with Ticket Tailor? FlowRunner agents can run List Events, Get Event, and List Event Series in Ticket Tailor, plus 4 more actions. ### Does connecting Ticket Tailor to FlowRunner require OAuth? No. Ticket Tailor connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Ticket Tailor trigger a FlowRunner workflow automatically? Ticket Tailor doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Ticket Tailor?** This integration exposes Ticket Tailor to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/ticket-tailor. Site index: https://flowrunner.ai/llms.txt