Numbers before the night
Priya Sharma, events lead at Acme Ltd, asked how many were coming to Thursday's customer evening. Memtro gave the approved, pending and waitlist counts for the event, and said registration was still open.
Luma + Memtro
How many are registered for our next event, and who checked in?
Luma connects Memtro to your events calendar. It reads upcoming and past events, hosts and guest counts, guest lists with registration and check-in times, ticket types with prices and capacity, and contacts with events attended. A key belongs to one calendar. When asked, and once an administrator has granted the action by name, it creates and updates events, adds guests, emails invitations, approves or declines guests, reviews submitted events and tags or imports contacts. Invitations cannot be unsent. Cancelling an event is permanent and notifies every guest, and moving a paid guest out of going can refund them.
In Memtro
What you can do with Luma in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Luma tool, reads what it needs, and answers with the source cited.
What it does
- 01Lists upcoming events soonest first, or recent past ones, with start and end, venue, visibility and tags, and reads one event's hosts and guest counts.
- 02Lists an event's guests with email, status, registration time, check-in time and ticket names, filtered by status.
- 03Lists an event's ticket types, free or paid with price, capacity, whether approval is required and when each is on sale.
- 04Searches the calendar's contacts by name, email or tag, with how many events each was approved for and checked in to.
- 05When asked and granted, creates or updates events, adds guests, emails invitations that cannot be unsent, approves, declines or waitlists guests (refunding a paid one only if asked), and approves or rejects submitted events.
- 06When asked and granted, cancels an event, which is permanent and notifies every guest, and creates contact tags, tags contacts or imports contacts.
Acts when asked
When you ask it to
These tools change something in Luma. 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.
- 01Create a Luma event
- 02Update a Luma event
- 03Cancel a Luma event (permanent, notifies every guest)
- 04Add guests to a Luma event
- 05Email Luma invitations to an event
- 06Approve, decline, waitlist or un-approve a Luma guest
- 07Approve an event submitted to the Luma calendar
- 08Reject an event submitted to the Luma calendar
- 09Create a Luma contact tag
- 10Tag Luma contacts
- 11Import contacts into the Luma calendar
Events
When it happens
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Luma for you. Each event can start a job, with the event as its input, and can be remembered where you choose. Luma signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooks- 01A guest registered or was added
- 02A guest's registration changed
- 03A guest was refunded
- 04A ticket was registered
- 05An event was created
- 06An event was updated
- 07An event was canceled
- 08An event was added to the calendar
- 09An event was submitted to the calendar
- 10Someone subscribed to the calendar
- 11Someone opted out of the calendar
In practice
Ask it like you would a colleague
Once Luma 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.
Luma + MemtroHow many are registered for our next event?
Who checked in to last Thursday's meetup?
Who is still on the waitlist for the product launch?
Which ticket types are still on sale for the summit?
Invite the BigCo buying team to the customer evening on the 14th.
Filling the last seats
Dan Fletcher, a sales manager at Acme Ltd, asked Memtro to invite three Northwind buyers to the launch with a short note from him. Memtro sent the Luma invitations, and each buyer received an email they could accept or decline.
Teams
Where it fits
The teams that lean on Luma most, a question each of them asks, and what they connect beside it.
- ProductHear what customers actually ask forProduct manager, Researcher, Designer, Head of product“Which customers asked for SSO this quarter, and what is their combined ARR?”Used alongside Help Scout, HubSpot, Linear, Jira, Slack and 6 more.
- EngineeringKeep decisions from evaporatingEngineer, Tech lead, On call, New joiner“Who owns the billing migration, and what did we decide about retries?”Used alongside GitHub, Linear, Jira, Confluence, Slack and 5 more.
- OperationsMonitors and digests that run themselvesOperations lead, Analyst, Team manager, Administrator“List my jobs”Used alongside Help Scout, Stripe, Xero, Postgres, ShipEngine and 8 more.
Better together
Works with
A record in Luma 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.
- Engineering and operationsLuma with GitHubIssues, pull requests, code and commits, searchable by anyone who can ask a question.
- Engineering and operationsLuma with AWS CloudWatchLogs, metrics and alarms from AWS, answered in plain English with the query that found them.
- Engineering and operationsLuma with SentryAsk what is breaking in production and get the stack trace, not a dashboard.
- Documents and wikisLuma with NotionSearch pages and query databases, and write to them when you ask.
- Documents and wikisLuma with Google DriveSearch Drive and read Docs, Sheets and Slides as text, and write a Doc when you ask.
- Documents and wikisLuma with ConfluenceSearch and read wiki pages, and write them when you ask.
- Email, calendar and chatLuma with GmailSearch and read mail so the last thread with a customer is one question away, and send the reply when you ask.
- Email, calendar and chatLuma with SlackSearch messages, read channel history and threads, post when you ask, and answer when mentioned.
- Email, calendar and chatLuma with Google CalendarMeetings in a window, event details, and the next two weeks synced into memory, and events it can create, change or cancel when you ask.
Also in Work management
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Clio Manage- Linear
- Jira
- Asana
- monday.com
- Airtable
- Basecamp
- Trello
- ClickUp
- Harvest
- Productboard
- Shortcut
- Todoist
YouTrack- Baserow
Canny- Clockify
- Everhour
Float
Productive
Smartsheet- Teamwork.com
- Toggl Track
Wrike
Financial Cents
Karbon
Scoro
Kanboard
Kimai
Leantime- OpenProject
- Plane
- Redmine
- Vikunja
Acuity Scheduling
Tito
Fellow
Samsara
ServiceM8
Cliniko
Fleetio
SavvyCal
Chili Piper
Humanitix
Circleback
Aha!
Tempo- RotaCloud
Smoobu
Semble- airfocus
Airmeet
Beds24
Bookeo
Commusoft- Favro
Fergus
Fixflo- Hostaway
- Hostfully
Housecall Pro- Motion
Nookal
Paymo
ProductPlan
SimplyBook.me- Synchroteam
TimeCamp
Workiz- Zuper
Guesty
Buildium
Skilljar
Runn
Clockodo
Setup
How to connect
Connect withAPI key
- 1
In Luma, open your calendar and go to Settings → Developer → API Keys. It has also been called Calendar Settings → API.
- 2
Create an API key for the calendar and copy it. The key can manage everything on the calendar, so Memtro changes something only for actions an administrator has granted.
- 3
In Memtro, open Connections → Luma and paste it into API key.
- 4
Ask "How many are registered 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 Luma tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in Luma?+
Only when you ask, and only what it has been granted: create a Luma event; update a Luma event; cancel a Luma event (permanent, notifies every guest); add guests to a Luma event; email Luma invitations to an event; approve, decline, waitlist or un-approve a Luma guest; approve an event submitted to the Luma calendar; reject an event submitted to the Luma calendar; create a Luma contact tag; tag Luma contacts; import contacts into the Luma calendar. 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 Luma 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 Luma 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 Luma?+
API key. In Luma, open your calendar and go to Settings → Developer → API Keys. It has also been called Calendar Settings → API.
Can Luma start a job?+
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Luma for you. 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 Luma in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.