Introducing @Resource_Bot: an automated search engine and fact-finder

Hey everyone! In the coming days, you'll start to see a new "face" in some topic threads: @Resource_Bot, a tool that our community team has been building and testing behind the scenes.

How it works
On topic creation, we kick off a thorough search for relevant info in the Retool docs and existing forum content. Based on the results of those searches, @Resource_Bot then summarizes the stated question or problem and shares links to the most highly relevant resources, whether they be forum threads or docs pages.

Our goals
To be clear, this new system is not replacing our Community team; instead, it will augment and even highlight the work that they already do. Nor will it replace those users that enjoy helping their fellow builders. This forum works because real people bring real judgment and varied experience to bear on specific problems.

Because of all your contributions, there is a wealth of information out there; despite that, discovery continues to be an issue, as evidenced by the continued creation of duplicate topics. That is exactly where @Resource_Bot can be most useful - unblocking users in minutes instead of hours or days by quickly surfacing existing solutions.

Asks
We understand that LLMs are not infallible and, as such, are setting relatively conservative goals for the early days of this new system. Your feedback will be very much appreciated as we continue to make incremental tweaks and adjustments! To help:

  • Give the @Resource_Bot reply a :+1: or even mark it as the solution, if it's helpful
  • Let us know if it misses something obvious or surfaces irrelevant info

In general, we're always looking for ways to make this space as helpful and engaging as possible. Let us know if you have any ideas! Last but not least, thank you all for helping to build a forum with the valuable human content that is required to power our new friend. :robot:

~Retool Community Team

3 Likes
Text Input component "default value" stopped populating input field (evaluates correctly, suddenly broke)
[Bug] Retool email disabled for sending spam
Backend function trigger throws internal runtime error
Embedding New Retool Apps inside Classic Apps?
New app builder - cannot connect Google Gemini resource to the app
Setup row editable using Dynamic Columns
The error is across most of my database connections and its inconsistent
Workflow editing via MCP/API
App Builder eats through AI credits *way* too quickly
Installing App to home screen with Safari causes "App not found" error
Tag options not displaying in table
Public link sharing missing for new app builder
Retool Assist with AI Gateway for AWS Bedrock?
Models from Anthropic used by Assist could not be successfully verified
Can't embed app in an iframe with the new app builder
Set a Default Retry Config on a Resource
Editing branch stuck out of sync with published version β€” "integrate changes" fails, no way to reset (Retool-managed git)
AI assist is locked up
Self-hosted, Workflow, internal error running a block
New app builder cannot find Google Drive resource
Licensing and deployment options for building client apps in Retool
Workflow Not Working 2
OpenAPI Resource not working with spec that contains no origin
Protected workflow calling another protected workflow is failing on feature branch
Resource authorisation changes broke our new apps
Activating Email from Operating Code
Calling function or workflow recursively
Custom Domain not showing target Web App URL

To surface a miss, this bot reply on this real (and, sadly for us, quite disruptive) Retool bug yesterday was not helpful, and perhaps distracting.

Could be nice to have a way to downvote the bot’s replies, and if it receives enough, it’s collapsed or hidden by default. Or if a Retool mod could perform the same action. Either would especially be useful in the event of an ongoing and acknowledged-by-Retool bug.

P.S. Thanks for your help in responding to that issue thread, @Darren !

The very first bot response being such a miss after a ton of positive testing was definitely a face-palm moment for me. :rofl: It found reliable sources but seemingly misinterpreted them pretty badly.

I'm actually working on this! In this particular case, negative feedback is just as helpful as positive. I suppose the current pathway would be to just flag and hide the post.

1 Like

glad to hear it’s already being worked on!

Quick update - I haven't hooked up any additional automations to flag or hide the response, but you can now downvote it!

1 Like