Skip to main content

Changelog

Updates, changes, and improvements at Retool.

Refer to the stable and edge release notes for detailed information about self-hosted releases.

You can now delete workflows programmatically using the DELETE /api/v2/workflows/{workflowId} endpoint in the Retool REST API.

To use this endpoint, your API token must have the workflows:write scope. The endpoint only supports deleting standard workflows—deleting agents and functions via the API is not supported.

Refer to the Retool API reference for full endpoint details, including request parameters and error responses.

Retool now provides a native integration for CockroachDB, a relational database management system. You can create a CockroachDB resource to securely connect to your databases and create apps and automations that use SQL queries to perform create, read, update, and delete operations.

To enable the CockroachDB integration in Retool, navigate to Beta > Settings and turn on CockroachDB connector.

App builders can now defer the initialization of modules until they're viewable to improve the initial loading time of larger apps.

To enable this public beta, navigate to Beta > Settings and enable [Perf] Module deferred evaluation.

When an app is initially loaded, Retool initializes all code, components, and modules. However, a common use case for modules is including them in conditionally hidden frames, and these modules don't need to be loaded when they are still hidden.

Modules now have a new option in the Inspector: [Beta] Defer evaluation until visible. When a “deferred” module is hidden (either ‘hidden’ state is true, or it is in a hidden frame, or otherwise not being rendered), Retool defers the module's initialization. When the module is shown, Retool invokes the initialization procedure that would typically happen during app startup.

This gives builders more flexibility in how components are loaded in their apps, and large apps load more quickly.

Retool made significant updates that improve Assist's app generation capabilities:

  • Improved quality of app generation. Assist has an improved ability to successfully set a wider set of properties across a wider set of components.
  • Quicker app generation. Generating an app from scratch is approximately 20% faster.
  • Better token efficiency, especially for app editing. Token use has decreased by approximately 40-50%, depending on the change type. Users will notice a decrease in the number of context window issues they encounter.
  • Improved support for building forms and using repeatable components inside apps.

This change is currently rolling out to cloud instances and will be available to self-hosted instances in an upcoming edge release.

Retool now provides a native integration for ServiceNow, an IT service management platform for managing incidents, change requests, service catalog items, and other operational workflows. You can create a resource and write queries to interact with the ServiceNow API.

READMEs can now be protected for apps that use Source Control. For existing apps that have a README, Retool will add a README.md file to your repository with your next commit. If you are protecting an app for the first time, Retool will include the README.md file automatically.

This feature is currently rolling out to cloud instances and will be available to self-hosted instances on an upcoming edge release.

As a form of feedback, you can now submit prompts from the help button. Find the help button at the bottom right of pages like the apps or resources landing page. Each prompt triggers an internal prototype generated with AI, which Retool can use to improve the product. If Retool implements the feature, you can choose to be credited with your name in the changelog.

Retool would like to thank the Conductor team, who inspired this change with their recent update.

Retool has two new improvements to the API:

  • A new per-instance API reference is now available at {your-instance}/reference. The reference is available on all cloud instances and served locally by self-hosted deployments within its VPC—no internet connection required. The API reference reflects only the API version running on your instance and always matches what's available to you.
  • The API version now tracks the Retool release version. The Retool API version now corresponds to your instance's release version. This makes it easier to track Retool API changes whenever your instance is updated.