Retool StrawberryThe Retool organization user attributes nobody wants to work through
It reads every organization user attribute your Retool account holds, drafts the changes that follow, and hands you a card for each one before a single organization user attribute moves.
Open the organization user attribute. Check it against something else. Write the change. Move to the next one. That is the Retool afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a organization user attribute until you approve it.
What it can do is exactly what Retool exposes to an account you authorise and nothing beyond it: 3 operations, no reads and 3 writes. In practice that means it can trigger a workflow, create an user and create an organization user attribute, and work across the organization user attributes, users and workflows.
The Retool API stops at Retool. 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.
What does it already know about your users?
In the tab.
Retool exposes no read operation to a connected account, so a companion opens Retool in the session you are already signed into and reads the screens you would.
The organization user attributes are what most of this inventory is about, alongside the users. A companion can hold all 3 of these operations and forty open tabs in the same pass, which is how an afternoon of Retool admin becomes a queue you review.
Who signs off on a new user?
All 3 write operations wait for you.
A companion can trigger a workflow, create an user and create an organization user attribute, and each one is staged on an approval card first: you see the organization user attribute, the field and the new value before it lands in Retool.
Nothing in Retool is sent, changed or deleted on your behalf without that click, and a rejected card leaves the organization user attribute exactly as it was. The gate is the same one on every surface, described at security.
- Trigger Workflow
- Create User
- Create Organization User Attribute
Can it trigger workflow on a schedule?
Yes.
Saved as a routine, the Retool organization user attributes 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 product and engineering playbook catalogues the other recurring shapes of the site work, the Retool organization user attributes 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