New App Builder cannot discover existing workspace resources or trigger published workflow

đź’¬ App Building
2

Summary

On Retool Cloud using the new App Builder, an existing GitHub workspace resource never appears in the app's /backend/resources and cannot be selected, and a generated backend function using the native workflows[...] trigger pattern fails with 'Retool workflow triggers are not available in this app runtime.' The supported path is needed to expose an existing resource to the backend, trigger a published Workflow from a backend function, or invoke an existing REST resource.

AI Response

Both symptoms map to recently reported new App Builder behaviors on Cloud with confirmed guidance. For resource discovery, this is a known sandbox sync limitation where existing resources aren't surfaced to the agent; the confirmed workaround is to force a re-sync by opening a brand-new chat thread (or waiting ~10 minutes) after a hard refresh, and to verify the resource lives in the same workspace and is shared with a group where you have Edit or Own access, since the agent only connects resources you can edit or own (you can then @-tag it by name). For the workflow trigger, the 'Path not allowed'/'triggers not available in this app runtime' failure was a known regression that Retool confirmed fixed and live in production on Retool Cloud 4.47.0, so retrying on the current build should work; in the meantime, the supported bridge is to call the workflow via a REST resource pointing at its webhook trigger rather than the native workflows[...] pattern.

Sources

:bookmark: Custom REST resource not visible to new App Builder backend
A near-identical Cloud case where a custom/existing resource never appears in the new App Builder's /backend/resources; Retool staff confirmed ongoing sandbox resource-sync issues and gave the fix — open a new thread or wait ~10 minutes, and confirm same-workspace plus Edit/Own access.
:bookmark: Workflow trigger from app failing with Path not allowed error
Directly matches the workflow-trigger failure ('Path not allowed'/triggers unavailable in the app runtime); Retool staff confirmed it as a regression now fixed and live on Retool Cloud 4.47.0, with a REST-resource-over-webhook call offered as the interim workaround.

The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a :heart:, :+1:, or :-1:. Or by marking this post as the "Solution"! Let us know if you have any feedback here. :rocket: