Connect Ticket Tailor to Well

Select Ticket Tailor in Well's Connections panel and start the handshake. Well discovers the OAuth metadata at the Ticket Tailor MCP server on mcp.tickettailor.ai, registers through Dynamic Client Registration, and sends you to approve the read scopes on Ticket Tailor's side. Nothing to paste, and you decide on its screen what Well may read.

The buyers, the orders, and the money behind them. Ticket Tailor maps to the company, people, invoice, and transaction entities, so an event buyer resolves to a person and an organising account to a company, a ticket order arrives as an invoice, and the payment that clears it lands as a transaction. The read runs one way; Well never edits an event or a ticket back in Ticket Tailor.

It does. When an order is paid in Ticket Tailor, Well reads the invoice for the tickets and the transaction that settled it, then records the amount against the buyer. Event income then sits next to the rest of your finances, so a question about ticket revenue for a given event answers from the same place that holds your bank and billing data.

Yes. Because each order arrives as an invoice joined to the buyer and the payment that cleared it, an agent can total takings for an event, surface refunded orders, or rank events by paid attendance, and answer from your workspace rather than the Ticket Tailor dashboard. Every figure keeps the order it came from, so the answer drills back to a single ticket sale when you need the detail.

Well reads orders, invoices, and the transactions behind them through the Ticket Tailor MCP connection and folds new sales in as they are read, with the first connect pulling existing order history in the background. Ticket Tailor stays the system of record for the events; Well keeps a queryable copy so ticket revenue sits beside the rest of your workspace.

Disconnect Ticket Tailor in Well and reads stop immediately and the token is released; because the connection only ever read, there is nothing to unwind on Ticket Tailor's side. The buyers, invoices, and transactions already brought across stay in your workspace for reporting, so historical takings questions keep answering after the connection ends.