Payload shape
Trace which task output fields Retool exposes and how they should be normalized before the next block runs.
Retool Workflows
A focused audit for Retool workflows where a user task, approval, or human handoff needs assignee fields available to the next block, notification, database update, or API call.
Fit
The audit keeps the fix narrow: identify the available fields, shape the next block input, and prove it with one test path.
Trace which task output fields Retool exposes and how they should be normalized before the next block runs.
Flag cases where profile, group, team, or user fields are not available and define a safe fallback.
Verify the database update, API call, message, or webhook receives the exact assignee values it expects.
Payload checklist
Most Retool assignee issues are payload-shape issues: the human task captures the right person, but the next block expects a different field name, object level, or fallback value.
Save the raw task output, assignee field path, current user context, and the block that needs the assignee details.
Return one clean object with the assignee id, email, display name, and review status instead of passing the whole task payload downstream.
Define what happens when the task is unassigned, reassigned, cancelled, or completed by a different user than expected.
Deliverables
Send the workflow goal, the user task block, and the downstream block that needs assignee details. TinyOps will return the field map and test path.