Summary
Using the new app builder, an added Google Drive resource is not being surfaced/recognized by the builder agent, and hard-refreshing, starting a new thread, and asking the agent to find or create the resource haven't helped.
AI Response
This is a known resource-discovery behavior in the new app builder, where resources created after the app was generated may not surface to the agent. Beyond the refresh and new-chat-thread steps already tried, confirm the resource and app are in the same workspace and that the relevant user group has explicit access to the Google Drive resource, since the builder only surfaces resources the group is permitted to use. A confirmed workaround is to ask the builder to add the resource from scratch (reusing the same credentials), then delete any duplicate that results. Note that Retool shipped changes on July 31, 2026 that significantly improved how the sandbox consumes resource information, so retrying after ensuring access should now be more reliable.
Sources
App won't surface an existing Google OAuth 2.0 REST resource
A near-identical new app builder case where a globally created Google resource wouldn't surface; Retool staff shared the refresh + new-chat-thread workaround and confirmed on July 31, 2026 that resource discovery was significantly improved.
A solved thread on the same resource-discovery behavior, resolved by asking the builder to add the resource from the beginning (same credentials) and then removing the duplicate.
The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a 
, 
, or 
. Or by marking this post as the "Solution"! Let us know if you have any feedback here. 