Arlo StrawberryRead every event, draft every presenter, approve in one pass
Your Arlo, worked while you do something else: 7 reads to go through it, 3 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 Arlo 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 Arlo exposes to an account you authorise and nothing beyond it: 10 operations, 7 reads and 3 writes. In practice that means it can update a presenter, create a presenter and create an event, and work across the events, presenters and registrations.
The Arlo API stops at Arlo. 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?
7 of the 10 operations are reads.
Your account, not a guess at it: a companion can list venues, list registrations and list presenters, and the full list below is the whole list, with nothing inferred from Arlo's documentation.
The events are what most of this inventory is about, alongside the presenters. A companion can hold all 10 of these operations and forty open tabs in the same pass, which is how an afternoon of Arlo admin becomes a queue you review.
- List Venues
- List Registrations
- List Presenters
- List Events
- List Event Templates
- Get Registration
- Get Event
Who signs off on a new presenter?
All 3 write operations wait for you.
A companion can update a presenter, create a presenter 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 Arlo.
Nothing in Arlo 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 Presenter
- Create Presenter
- Create Event
Does the event sweep have to be asked for every time?
Yes.
Saved as a routine, the Arlo 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 busywork, the Arlo 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