Livestorm StrawberrySomeone still has to update event. It does not have to be you
Your Livestorm, worked while you do something else: 5 reads to go through it, 2 writes to change it, and a card in front of every one of those changes.
Open the event. Check it against something else. Write the change. Move to the next one. That is the Livestorm 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 Livestorm exposes to an account you authorise and nothing beyond it: 7 operations, 5 reads and 2 writes. In practice that means it can update an event and create an event, and work across the events, attendees and register someones.
The Livestorm API stops at Livestorm. 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.
Does it read the events or ask you for them?
5 of the 7 operations are reads.
Your account, not a guess at it: a companion can register someone for a session, list sessions and list events, and the full list below is the whole list, with nothing inferred from Livestorm's documentation.
The events are what most of this inventory is about, alongside the attendees. A companion can hold all 7 of these operations and forty open tabs in the same pass, which is how an afternoon of Livestorm admin becomes a queue you review.
- Register Someone For A Session
- List Sessions
- List Events
- List Attendees From Event
- Get Event
Can it change a event without asking?
All 2 write operations wait for you.
A companion can update an event and create an event, and each one is staged on an approval card first: you see the event, the field and the new value before it lands in Livestorm.
Nothing in Livestorm 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.
- Update Event
- Create Event
Does the event sweep have to be asked for every time?
Yes.
Saved as a routine, the Livestorm 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 operations playbook catalogues the other recurring shapes of the operations, the Livestorm 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