Ticket Tailor + Memtro

Ask how many tickets an event has sold, and how many people have checked in.

Connect Ticket Tailor with an API key and Memtro reads your box office: events and series with tickets issued and revenue, orders with totals, refunds and payment method, and issued tickets with their check-in state. Buyer emails, phones and addresses are never read out. A key reaches one box office. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can issue a ticket to a named attendee, which spends one credit and emails them only if asked, or permanently void a ticket, which refunds nobody.

In Memtro

What you can do with Ticket Tailor in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Ticket Tailor tool, reads what it needs, and answers with the source cited.

What it does

  1. 01Events with start and end, venue, tickets available and issued, and revenue
  2. 02Event series with status, venue, next date, number of occurrences, tickets issued and revenue
  3. 03Orders by event with status, ticket count, subtotal, tax, total, amount paid, refunds and payment method
  4. 04Issued tickets by event or order, with ticket type, status and whether checked in, and names only when asked for
  5. 05When asked and granted, issues a ticket to a named attendee from a ticket type or a hold, spending one Ticket Tailor credit and emailing them only if asked
  6. 06When asked and granted, permanently voids an issued ticket, optionally back to a hold, without cancelling the order or refunding anyone

Acts when asked

When you ask it to

These tools change something in Ticket Tailor. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.

  1. 01Issue a ticket for an event to a named attendee, spending one credit, emailing them only if asked
  2. 02Void an issued ticket (permanent), optionally back to a hold

Events

When it happens

Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Ticket Tailor, choosing the same kinds; the tab shows Ticket Tailor's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. Ticket Tailor signs every delivery, and one whose signature does not check out is refused before it is read.

Events and webhooks
  • 01Order placed
  • 02Order updated or cancelled
  • 03Ticket issued
  • 04Issued ticket updated or voided
  • 05Membership issued
  • 06Membership updated or voided
  • 07Event created
  • 08Event updated
  • 09Event deleted
  • 10Basket expired after the buyer entered details
In practice

Ask it like you would a colleague

Once Ticket Tailor is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.

Ticket Tailor + Memtro
  • How many tickets have we sold for the Acme summer meetup?

  • What revenue has the Northwind workshop series taken so far?

  • How many people have checked in at tonight's event?

  • Which orders for the Brightwave Ltd launch were refunded?

  • Issue a speaker ticket for the summer meetup to Priya Nair

01

Numbers for the venue

Three days before the Acme summer meetup the events lead asks how many tickets are out. Memtro reads the event: 186 issued of 220 available and the revenue so far, so she can give the venue a firm headcount.

02

A late speaker

Laura Bennett asks Memtro to give the Northwind workshop's guest speaker, Priya Nair, a ticket from the speakers hold and email it to her. Memtro issues the ticket, which spends one credit, and Ticket Tailor emails it to Priya.

Teams

Where it fits

The teams that lean on Ticket Tailor most, a question each of them asks, and what they connect beside it.

Better together

Works with

A record in Ticket Tailor is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.

Also in Content and web

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

Setup

How to connect

Connect withAPI key
  1. 1

    In your Ticket Tailor box office open Settings → API and generate a new API key

  2. 2

    Copy the key, which starts sk_. A key reaches one box office only, so make one for each box office

  3. 3

    Paste the API key into Connections → Ticket Tailor in Memtro and connect

  4. 4

    Ask how many tickets you have sold for your next event

Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Ticket Tailor tools are the same everywhere.

FAQ

Questions

Can Memtro change anything in Ticket Tailor?+

Only when you ask, and only what it has been granted: issue a ticket for an event to a named attendee, spending one credit, emailing them only if asked; void an issued ticket (permanent), optionally back to a hold. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

Who can use a Ticket Tailor connection?+

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Does Memtro store my Ticket Tailor data?+

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

How do I connect Ticket Tailor?+

API key. In your Ticket Tailor box office open Settings → API and generate a new API key.

Can Ticket Tailor start a job?+

Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Ticket Tailor, choosing the same kinds; the tab shows Ticket Tailor's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.

Connect Ticket Tailor in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time