Read every user, draft every task, approve in one pass
It reads every user your Teamwork account holds, drafts the changes that follow, and hands you a card for each one before a single user moves.
Open the user. Check it against something else. Write the change. Move to the next one. That is the Teamwork afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a user until you approve it.
What it can do is exactly what Teamwork exposes to an account you authorise and nothing beyond it: 8 operations, 3 reads and 5 writes. In practice that means it can update an user, update a task and delete a task, and work across the users, tasks and project tasks.
The Teamwork API stops at Teamwork. 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.
Can it list users on its own?
3 of the 8 operations are reads.
Your account, not a guess at it: a companion can list users, list project tasks and get an user, and the full list below is the whole list, with nothing inferred from Teamwork's documentation.
The users are what most of this inventory is about, alongside the tasks. A companion can hold all 8 of these operations and forty open tabs in the same pass, which is how an afternoon of Teamwork admin becomes a queue you review.
- List Users
- List Project Tasks
- Get User
Which users wait for your approval?
All 5 write operations wait for you.
A companion can update an user, update a task and delete a task, and each one is staged on an approval card first: you see the user, the field and the new value before it lands in Teamwork.
Nothing in Teamwork is sent, changed or deleted on your behalf without that click, and a rejected card leaves the user exactly as it was. The gate is the same one on every surface, described at security.
- Update User
- Update Task
- Delete Task
- Create User
- Create Task
Can it update user on a schedule?
Yes.
Saved as a routine, the Teamwork users 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 planning, the Teamwork users 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