How many tickets have we sold for the gala, and who is coming?
Humanitix connects Memtro to your event ticketing. It reads your events with dates, venue, capacity, ticket types and prices, then each event's orders with buyer name, status, total and refunds, and its attendees by name and ticket type. It counts check-ins per event date, in total and per ticket type. When asked, and once an administrator has granted the action by name, it can check an attendee's ticket in or out, as a scan at the door would, if the key has the tickets:checkin scope. Buyer email, phone and form answers are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Humanitix tool, reads what it needs, and answers with the source cited.
These tools change something in Humanitix. 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.
Once Humanitix 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.
Humanitix + MemtroWhat events do we have coming up?
How many tickets have we sold for the gala?
Who is coming to Thursday's workshop?
How many people have checked in to tonight's launch so far?
Check in Priya Sharma for tonight's launch
Maya Okafor, events manager at Acme Ltd, asked how many VIP tickets had gone for the gala. Memtro listed the attendees with counts per ticket type and named the VIP holders. She set the top table from that list without opening Humanitix.
At the Northwind product launch, Dan Fletcher asked Memtro to check in Priya Sharma, whose phone had died with her ticket on it. Memtro found her ticket in the attendee list and checked it in to Humanitix, as a scan would, and the check-in count rose by one.
The teams that lean on Humanitix most, a question each of them asks, and what they connect beside it.
A record in Humanitix 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.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Clio Manage
YouTrack
Canny
Float
Productive
Smartsheet
Wrike
Financial Cents
Karbon
Scoro
Kanboard
Kimai
Leantime
Acuity Scheduling
Luma
Tito
Fellow
Samsara
ServiceM8
Cliniko
Fleetio
SavvyCal
Chili Piper
Circleback
Aha!
Tempo
Smoobu
Semble
Airmeet
Beds24
Bookeo
Commusoft
Fergus
Fixflo
Housecall Pro
Nookal
Paymo
ProductPlan
SimplyBook.me
TimeCamp
Workiz
Guesty
Buildium
Skilljar
Runn
ClockodoIn the Humanitix console, go to Account → Advanced → API keys. Only the account owner can create keys.
Create a key, give it a name and tick events:read, orders:read and tickets:read, and tickets:checkin only if Memtro should check people in. Confirm with the one-time code and copy the key, which is shown once.
In Memtro, open Connections → Humanitix and paste the key into API key.
Ask a first question, such as "What events do we have coming up?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Humanitix tools are the same everywhere.
Only when you ask, and only what it has been granted: check an attendee's ticket in to an event; undo an attendee's check-in (check the ticket out). 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.
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.
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.
API key. In the Humanitix console, go to Account → Advanced → API keys. Only the account owner can create keys.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
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