Brainbase Labs StrawberrySomeone still has to update worker. It does not have to be you
A companion works the 26 operations your Brainbase Labs account exposes. It can update a worker and update a voice deployment, and every one of those waits on an approval card showing the flow before it changes.
Open the flow. Check it against something else. Write the change. Move to the next one. That is the Brainbase Labs afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a flow until you approve it.
What it can do is exactly what Brainbase Labs exposes to an account you authorise and nothing beyond it: 26 operations, 14 reads and 12 writes. In practice that means it can update a worker, update a voice deployment and update a flow, and work across the flows, voice deployments and workers.
The Brainbase Labs API stops at Brainbase Labs. 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.
Which Brainbase Labs flows does a companion see?
14 of the 26 operations are reads.
Your account, not a guess at it: a companion can register phone number, make voice batch calls and list workers, and the full list below is the whole list, with nothing inferred from Brainbase Labs's documentation.
The flows are what most of this inventory is about, alongside the voice deployments. A companion can hold all 26 of these operations and forty open tabs in the same pass, which is how an afternoon of Brainbase Labs admin becomes a queue you review.
- Register Phone Number
- Make Voice Batch Calls
- List Workers
- List Voice Deployments
- List Voice Deployment Logs
- List Integrations
- List Flows
- Get Worker
- Get Voice Deployment
- Get Voice Deployment Log
- Get Team
- Get Phone Numbers
- Get Integration
- Get Flow
What happens before it can update worker?
All 12 write operations wait for you.
A companion can update a worker, update a voice deployment and update a flow, and each one is staged on an approval card first: you see the flow, the field and the new value before it lands in Brainbase Labs.
Nothing in Brainbase Labs is sent, changed or deleted on your behalf without that click, and a rejected card leaves the flow exactly as it was. The gate is the same one on every surface, described at security.
- Update Worker
- Update Voice Deployment
- Update Flow
- Delete Worker
- Delete Voice Deployment
- Delete Phone Number
- Delete Integration
- Delete Flow
- Create Worker
- Create Voice Deployment
- Create Twilio Integration
- Create Flow
Can the flows pass run every Monday?
Yes.
Saved as a routine, the Brainbase Labs flows 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 Brainbase Labs flows 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