Planview Leankit StrawberryThe card work, done and queued for one look
Hand a companion the outcome. It reads the Planview Leankit cards, does the 26-operation version of the job, and stops for your click on anything that changes a record.
Open the card. Check it against something else. Write the change. Move to the next one. That is the Planview Leankit afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a card until you approve it.
What it can do is exactly what Planview Leankit exposes to an account you authorise and nothing beyond it: 26 operations, 6 reads and 20 writes. In practice that means it can update a custom field value, update card (or task) and start a task, and work across the cards, tasks and custom fields.
The Planview Leankit API stops at Planview Leankit. 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.
Where do the cards come from?
6 of the 26 operations are reads. Your account, not a guess at it: a companion can unblock card (or task), unassign user and get a card, and the full list below is the whole list, with nothing inferred from Planview Leankit's documentation.
The cards are what most of this inventory is about, alongside the tasks. A companion can hold all 26 of these operations and forty open tabs in the same pass, which is how an afternoon of Planview Leankit admin becomes a queue you review.
- Unblock Card (Or Task)
- Unassign User
- Get Card
- Find OR Create Card
- Find First Card
- Block Card (Or Task)
Who signs off on a new task?
All 20 write operations wait for you. A companion can update a custom field value, update card (or task) and start a task, and each one is staged on an approval card first: you see the card, the field and the new value before it lands in Planview Leankit.
Nothing in Planview Leankit is sent, changed or deleted on your behalf without that click, and a rejected card leaves the card exactly as it was. The gate is the same one on every surface, described at security.
- Update Custom Field Value
- Update Card (Or Task)
- Start Task
- Remove Tags From Card
- Remove Parent/Child Connection
- Move Cards To Another Board
- Move Cards Between Lanes
- Duplicate Task
- Duplicate Card
- Delete Custom Field
- Create Task Card
- Create Custom Field
- Add Comment To Card (Or Task)
- Create Card
- Add Card Type To Board
- Complete Task
- Assign User To Task
- Assign User To Card
- Add Tags To Card (Or Task)
- Create a Parent/Child Connection
What does the recurring cards pass look like?
Yes.
Saved as a routine, the Planview Leankit cards 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 Planview Leankit cards 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