Hand the Breathe employees to a companion
A companion works the 3 operations your Breathe account exposes. It can create a leave request and create an employee, and every one of those waits on an approval card showing the employee before it changes.
Open the employee. Check it against something else. Write the change. Move to the next one. That is the Breathe afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a employee until you approve it.
What it can do is exactly what Breathe exposes to an account you authorise and nothing beyond it: 3 operations, no reads and 3 writes. In practice that means it can create a leave request, create an employee and approve or reject leave request, and work across the employees, leave requests and reject leave requests.
The Breathe API stops at Breathe. 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 Breathe employees does a companion see?
In the tab.
Breathe exposes no read operation to a connected account, so a companion opens Breathe in the session you are already signed into and reads the screens you would.
The employees are what most of this inventory is about, alongside the leave requests. A companion can hold all 3 of these operations and forty open tabs in the same pass, which is how an afternoon of Breathe admin becomes a queue you review.
Can it change a employee without asking?
All 3 write operations wait for you.
A companion can create a leave request, create an employee and approve or reject leave request, and each one is staged on an approval card first: you see the employee, the field and the new value before it lands in Breathe.
Nothing in Breathe is sent, changed or deleted on your behalf without that click, and a rejected card leaves the employee exactly as it was. The gate is the same one on every surface, described at security.
- Create Leave Request
- Create Employee
- Approve or Reject Leave Request
Can the employees pass run every Monday?
Yes.
Saved as a routine, the Breathe employees 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 recruiting playbook catalogues the other recurring shapes of hiring admin, the Breathe employees 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