Starting January 1, 2027, Retool is deprecating Retool Email for organizations on the Free plan. After this date, Free plan organizations can no longer use Retool Email to send emails from apps, workflows, or other automations.

Retool Email remains available to organizations on the Team, Business, and Enterprise plans.

Who is affected​

This change affects cloud-hosted organizations on the Free plan that use Retool Email. Organizations on paid plans are not affected.

As part of our continued efforts to keep Retool secure and reduce vulnerabilities, Retool is deprecating several preinstalled third-party libraries, such as jsonwebtoken, crypto-js, moment, and uuid, currently available in custom authentication JavaScript steps. Retool plans to remove these libraries from cloud and self-hosted instances in Q2 2027.

If your custom authentication steps use any of these libraries, you can migrate to Node.js built-in equivalents, such as crypto and Buffer, well ahead of the removal date. Migrating before then avoids any disruption to your authentication flows.

Only REST API, GraphQL, OpenAPI, and gRPC resources that use Custom Auth with a JavaScript step that loads a preinstalled library are affected. JavaScript steps that use Node.js built-in modules, such as crypto, continue to work without changes.

Who is affected​

Any customers who have resources that use Custom Auth as its authentication method and one of its JavaScript steps loads a preinstalled library. Custom authentication steps that only use Form (modal), API Request, or Define a variable steps aren't affected, and neither are JavaScript steps that don't call require().

As part of our continued efforts to keep Retool secure and reduce vulnerabilities, hardened images become the default for self-hosted images starting in Q2 2027. As a result, Retool is deprecating Windows Authentication for Microsoft SQL Server resources. This deprecation also applies to Kerberos authentication for Microsoft SQL Server, which relies on Windows Authentication.

Hardened images are intentionally minimal and don't include the additional third-party libraries and utilities that Windows Authentication relies on. Microsoft SQL Server resources with Connect using Windows Auth enabled will eventually stop working, so plan to migrate before your resources are affected.

Who is affected​

This change only affects self-hosted organizations with Microsoft SQL Server resources that have Connect using Windows Auth enabled.

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.