App won't surface an existing Google OAuth 2.0 REST resource

💬 Queries and Resources
1

I'm stuck getting my app to recognize a resource I already created.

What I set up:

  • A REST API resource using Google OAuth 2.0 (Gmail API), created through Resources > Create new.

  • Authentication succeeded. The "Shared OAuth Tokens" modal for the resource shows a valid Access token and Refresh token.

The problem:

  • The resource never appears among my app's available resources. The agent in the Chat tab can't find any Google/Gmail resource; it only lists the ones already wired into the app

  • It also never shows in the Data tab.

Confirmed and tried:

  • The resource and the app are in the same workspace.

  • The OAuth tokens are valid (per the Shared OAuth Tokens modal).

  • Hard browser refresh; fully closing and reopening the app; asking the agent to re-scan and list every accessible resource; checked the resource's access/sharing settings.

Question:
How do I expose an existing workspace resource to my app, especially one created after the app was generated, so the agent can build queries against it? Is there a sync step or setting I'm missing, or are OAuth 2.0 resources handled differently than a standard REST resource like my Bubble one, which the app sees fine?

1 Like
New app builder - cannot connect Google Gemini resource to the app
New app builder cannot find Google Drive resource
Custom REST resource not visible to new App Builder backend
4

Thanks for reaching out, @kevincl - and welcome to the community!

You shouldn't have to do anything in particular. :sweat_smile: In my own testing, the newly created resource is taggable and the agent has sufficient context after a simple page refresh. That said, I've definitely run into this same bug before and remember resolving it by initializing a new chat thread.

I'll certainly try to identify the root cause and report back, but let me know if the above workaround unblocks you!

7

Resource discovery should be significantly better now, @kevincl! We've made several changes to the way the sandbox consumes that information. Let us know if you continue to see any lingering issues. :+1: