← all gaps
Retool verdict · build

REST API endpoints (GET /users, GET /users/{userId}, GET /users/{userId}/user_attributes) to enable reading user attributes for conditional logic and workflows.

Built for Retool business-tier users needing to read and conditionally branch on user attributes within applications..

The receipts — real demand

“I noticed the business tier, maybe others i'm not sure, have access to POST /users/{userId}/user_attributes which lets us edit attributes, but there's no way to actually check the attribute value for conditional branching and whatnot Its a bit odd, since the API Token has access to User Attribues > Read/Write but there is no way to actually read... theres doesn't seem to be an endpoint for GET /user…”
Retool · view original →
7.1 / 10 · demand score
Pain 8
Willingness to pay 5
Specificity 9
Audience 6
Competition 2

Why this is a gap

Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.