Lamini StrawberryBatch completions checked against completions, in one pass
Hand a companion the outcome. It reads the Lamini batch completions, does the 4-operation version of the job, and stops for your click on anything that changes a record.
Open the batch completion. Check it against something else. Write the change. Move to the next one. That is the Lamini afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a batch completion until you approve it.
What it can do is exactly what Lamini exposes to an account you authorise and nothing beyond it: 4 operations, 2 reads and 2 writes. In practice that means it can upload a dataset and generate a completion, and work across the batch completions, completions and datasets.
The Lamini API stops at Lamini. 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 batch completions come from?
2 of the 4 operations are reads.
Your account, not a guess at it: a companion can get batch completions and evaluate job, and the full list below is the whole list, with nothing inferred from Lamini's documentation.
The batch completions are what most of this inventory is about, alongside the completions. A companion can hold all 4 of these operations and forty open tabs in the same pass, which is how an afternoon of Lamini admin becomes a queue you review.
- Get Batch Completions
- Evaluate Job
Can it change a batch completion without asking?
All 2 write operations wait for you.
A companion can upload a dataset and generate a completion, and each one is staged on an approval card first: you see the batch completion, the field and the new value before it lands in Lamini.
Nothing in Lamini is sent, changed or deleted on your behalf without that click, and a rejected card leaves the batch completion exactly as it was. The gate is the same one on every surface, described at security.
- Upload Dataset
- Generate Completion
What does the recurring batch completions pass look like?
Yes.
Saved as a routine, the Lamini batch completions 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 Lamini batch completions 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