Changelog

Retool now supports the Login Attempted Retool Event, which triggers after a user authenticates and before the login process is complete. You can use Login Attempted to trigger a workflow and execute custom logic, such as modifying user data or querying external resources.

Choose to present users with an error message, or redirect them to an app or URL.

You can only attach one enabled parent workflow to this Retool Event. Retool recommends that this logic remain lightweight, because this workflow runs synchronously in the login flow and blocks users from accessing their Retool account until the workflow finishes.

Slack is ending support for their files.upload API on March 11, 2025. Refer to the Slack changelog for more information.

Retool is working to update our Slack integration as quickly as possible. In the meantime, if you need files.upload functionality, you can use a REST Query to utilize the new files.getUploadURLExternal and files.completeUploadExternal APIs.

This workaround is temporary, and Retool will restore access to file upload functionality within the Slack integration as soon as possible. Another changelog post will be made when the ability to upload files is restored. Other functionality in the Slack integration remains uninterrupted.

Previously, Retool Mobile only offered a component-based NFC reader, and we now support a resource-based NFC functionality that can both read and write.

The legacy option to create single-page apps has now been deprecated and is no longer available. Going forward, all newly created Retool apps support multiple pages, and newly created mobile apps support multiple screens.

Your existing single-page apps will continue to function as expected, and you are not required to migrate them. If you would like to do so, you can import legacy single-page apps as pages or use the Duplicate to multipage action on the apps landing page.

With multipage apps, Retool only evaluates the code and components of the page currently in view. The benefits of multipage apps include:

• Greater performance of large and complex apps. Since Retool only evaluates code and components for the current page, multipage apps are 30-40% faster than a single-page app.
• Seamless navigation between pages. Retool loads the complete app state whenever a user navigates to a single-page app. With multipage apps, navigation between pages is seamless and more responsive.
• Improved app management. Multipage apps can replace multiple apps in your organization, such as a team's frequently used apps. This reduces the number of apps to maintain and allows for easier permission management.
• Reduced module dependency. Modules are commonly used to create shared navigation menus across multiple single-page apps. With multipage apps, you can eliminate the need for additional modules and the complexities with maintaining them.
• Simplified code sharing. The mechanisms for sharing code and components in multipage apps (global code, frames) are lower friction, easier to set up, and more powerful than the mechanisms for sharing code across apps (modules, query library).

Retool has updated the built-in usage analytics with an improved experience that now organizes different data sets into tabs. These changes streamline the amount of data presented so that you can more easily focus on the analytics you need.

Retool surfaces a variety of usage analytics for you to monitor:

• Aggregate app usage over time.
• Aggregate active users over time.
• Individual app usage summaries.
• Individual user usage summaries.

The Usage Analytics feature is available for cloud- and self-hosted organizations on the Enterprise plan.

A redesigned Retool Database UI is coming soon. The improved interface makes working with tables faster and more intuitive.

Managing your data should be quick and frictionless, so we've made key improvements to help you navigate, edit, and interact with your data more efficiently. Here's what's new:

• Clearer Data View: A more structured layout makes it easier to understand your database at a glance and quickly find the information you need, reducing clutter and improving readability.
• Faster Navigation: We've streamlined the layout to help you move through your data more efficiently, with fewer clicks and less friction.
• One-Stop Command Bar: Quickly find and perform any actions from a new central location, enabling you to work efficiently without hunting through menus.

If you're interested in testing these new features early, you can join the waitlist.

Self-hosted Retool 3.148 is now available on the Stable release channel.

Retool releases a version on the Stable channel every 13 weeks (quarterly). A Stable release is generally four versions behind the cloud-hosted version at the time.

Preparation and testing of a Stable version occurs approximately four weeks prior to its release. Stable releases are rigorously tested before they are published. As the release cycle is less frequent, administrators can more easily maintain and upgrade deployments.

Retool supports each Stable release for six months. During this time, Retool will release patch updates that contain bug fixes or security updates. Patch updates do not contain functionality changes and can be applied more quickly than performing a full version upgrade.

After six months, a Stable release is considered deprecated. You can continue using a deprecated release but it will no longer receive updates. At this time, you should upgrade to the latest Stable release.

Retool AI* text action queries now support dynamic model selection. Clicking the Fx button next to the AI Model field in a query will display the model string in the following format: providerName::model-name, for example, openai::gpt-4o-mini. This provides the ability for users to dynamically change AI models from apps and workflows.

The App Inspector now appears when you have the Inspector open but no component selected. The App Inspector includes the following settings that were previously found in the App Settings sidebar:

• Browser title
• Custom URL
• Custom shortcuts
• Max width

The App Inspector also includes the Persist URL parameters setting, which configures search query parameters and hash parameters to persist during page navigation and when switching pages with the “Go to Page” event handler.

The directory structure for apps protected using Source Control is changing to reduce the likelihood of merge conflicts.

Component positioning information (stored in ToolScript files) is now organized by page. The apps directory contains a .positions directory, which contains one file per page in the format .pageName.positions.json.

Previously, all positioning information was stored in one .positions.json file. The new structure prevents merge conflicts.

app-name
└── .defaults.json
└── .positions.json
└── .mobilePositions.json
└── lib
  └── sqlQueryName.sql
  └── jsQueryName.js
└── src
  └── container1.rsx
└── functions.rsx
└── main.rsx
└── metadata.json

app-name
└── .defaults.json
└── .positions
  └── .global_mobile_positions.json
  └── .global_positions.json
  └── .pageName1.positions.json
  └── .pageName2.positions.json
  └── .pageName1.mobilePositions.json
  └── .pageName2.mobilePositions.json
└── lib
  └── sqlQueryName.sql
  └── jsQueryName.js
└── src
  └── container1.rsx
└── functions.rsx
└── main.rsx
└── metadata.json