Tito logo

Tito + Memtro

How many tickets have sold for our event, and is this person registered?

Tito connects Memtro to your event ticketing. It reads events, ticket types with price and tickets sold, registrations with who booked and their state, and tickets with attendee name and ticket type. Registrations also sync hourly. When asked, and once an administrator has granted the action by name, it creates and edits registrations and tickets, cancels registrations, voids tickets, reassigns a ticket, manages discount codes and puts ticket types on sale or pauses them. A refund through the payment provider moves money back and cannot be undone. Reassigning a ticket emails the new attendee. Use a live token.

In Memtro

What you can do with Tito in Memtro

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

What it does

  1. 01Lists events with title, dates, location, whether live and the public link, upcoming by default.
  2. 02Lists an event's ticket types with price, quantity on offer, tickets sold, and whether sold out, off sale or secret.
  3. 03Lists and finds registrations by name, email, reference or company, with who booked, state and number of tickets.
  4. 04Lists tickets with attendee name, email, company, ticket type, state and tags, and shows cancelled or void ones only when asked.
  5. 05When asked and granted, creates or edits registrations and tickets, cancels a registration or voids a ticket, reassigns a ticket (Tito emails the new attendee), and marks invoiced registrations paid.
  6. 06When asked and granted, refunds a registration through the payment provider, which moves money and cannot be undone, creates, changes or deletes discount codes, and puts a ticket type on sale or pauses it.

Acts when asked

When you ask it to

These tools change something in Tito. 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. 01Create a registration for named ticket types, emailing the registrant only when asked
  2. 02Edit a registration's name, email, company, purchase order or source
  3. 03Cancel a registration and void its tickets
  4. 04Refund a registration through the payment provider, or record a manual refund
  5. 05Mark an invoiced registration paid, or back to unpaid
  6. 06Add a ticket for an attendee, or edit an attendee's name, email, company or tags
  7. 07Reassign a ticket to a new attendee, which emails them
  8. 08Void a ticket so it can no longer check in
  9. 09Create, change or delete a discount code
  10. 10Put a ticket type on sale or pause its sale

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 Tito, choosing the same kinds; the tab shows Tito's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. Tito signs every delivery, and one whose signature does not check out is refused before it is read.

Events and webhooks
  • 01A registration was confirmed (e.g. payment complete)
  • 02Every ticket on a registration was filled in
  • 03A registration was updated
  • 04A registration was cancelled
  • 05Tickets were created for a confirmed registration
  • 06A ticket's required details were filled in
  • 07A ticket's details changed
  • 08A ticket was reassigned to someone else
  • 09A snoozed ticket was assigned
  • 10A ticket was voided
  • 11A voided ticket was restored
  • 12An attendee was checked in
  • 13Someone registered interest in an event
  • 14An interested person was updated
  • 15An interested person was removed
In practice

Ask it like you would a colleague

Once Tito 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.

Tito logoTito + Memtro
  • How many tickets have sold for our next event?

  • Is Sarah Chen registered for the conference?

  • Which ticket types have sold out?

  • Who from BigCo has booked?

  • Create a 20% discount code SPEAKERS for the autumn conference, limited to 10 uses.

01

Checking ticket sales

Maya Okafor, marketing manager at Acme Ltd, asked how sales were going for the autumn conference. Memtro listed each ticket type with tickets sold against quantity on offer, and named the one that had sold out.

02

Handing a ticket on

Tom Reilly, on the Acme Ltd events team, heard that a Northwind delegate could no longer attend and her colleague James Patel would go instead. He asked Memtro to reassign her ticket. Memtro reassigned it to James, and Tito emailed James, the original booker and the organisers.

Teams

Where it fits

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

Better together

Works with

A record in Tito 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.

Setup

How to connect

Connect withSecret API token and optional account slug
  1. 1

    Go to id.tito.io and choose Generate New Token. Set Type to secret, Mode to live and Version to 3.0, then copy it. The token can do anything your Tito user can, so Memtro changes things only through the actions an administrator grants.

  2. 2

    Find your account slug in your Tito URLs (ti.to/<account>/<event>). Leave it blank if the token covers only one account.

  3. 3

    In Memtro, open Connections → Tito and paste the token into Secret API token, with the Account slug if you need one.

  4. 4

    Ask "How many tickets have sold for our 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 Tito tools are the same everywhere.

FAQ

Questions

Can Memtro change anything in Tito?+

Only when you ask, and only what it has been granted: create a registration for named ticket types, emailing the registrant only when asked; edit a registration's name, email, company, purchase order or source; cancel a registration and void its tickets; refund a registration through the payment provider, or record a manual refund; mark an invoiced registration paid, or back to unpaid; add a ticket for an attendee, or edit an attendee's name, email, company or tags; reassign a ticket to a new attendee, which emails them; void a ticket so it can no longer check in; create, change or delete a discount code; put a ticket type on sale or pause its sale. 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 Tito 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 Tito 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. An hourly sync anchors recently changed Tito records into memory as entities.

How do I connect Tito?+

Secret API token and optional account slug. Go to id.tito.io and choose Generate New Token. Set Type to secret, Mode to live and Version to 3.0, then copy it. The token can do anything your Tito user can, so Memtro changes things only through the actions an administrator grants.

Can Tito 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 Tito, choosing the same kinds; the tab shows Tito'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 Tito 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