Luma StrawberryThe event work, done and queued for one look
Hand a companion the outcome. It reads the Luma events, does the 8-operation version of the job, and stops for your click on anything that changes a record.
Open the event. Check it against something else. Write the change. Move to the next one. That is the Luma afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a event until you approve it.
What it can do is exactly what Luma exposes to an account you authorise and nothing beyond it: 8 operations, 5 reads and 3 writes. In practice that means it can send invites, create an event and add guests, and work across the events, guests and invites.
The Luma API stops at Luma. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Where do the events come from?
5 of the 8 operations are reads.
Your account, not a guess at it: a companion can list ticket types, list events and get guests, and the full list below is the whole list, with nothing inferred from Luma's documentation.
The events are what most of this inventory is about, alongside the guests. A companion can hold all 8 of these operations and forty open tabs in the same pass, which is how an afternoon of Luma admin becomes a queue you review.
- List Ticket Types
- List Events
- Get Guests
- Get Guest
- Get Event
Can it change a event without asking?
All 3 write operations wait for you.
A companion can send invites, create an event and add guests, and each one is staged on an approval card first: you see the event, the field and the new value before it lands in Luma.
Nothing in Luma is sent, changed or deleted on your behalf without that click, and a rejected card leaves the event exactly as it was. The gate is the same one on every surface, described at security.
- Send Invites
- Create Event
- Add Guests
What does the recurring events pass look like?
Yes.
Saved as a routine, the Luma events pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The marketing playbook catalogues the other recurring shapes of campaign admin, the Luma events sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents