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.

Retool is deprecating the dedicated BigID resource type.

Retool will remove the resource type in Q1 2027, after two quarterly Stable releases. After removal, BigID resources will stop working. Queries in apps and workflows that still point at those resources will fail. Cloud and self-hosted organizations will not have a BigID connection option after removal.

Organizations can keep querying BigID after removal by creating an OpenAPI or REST API resource. Retool will not migrate BigID resources or their query references automatically.

1. Create an OpenAPI resource with specification URL https://sandbox.apps.mybigid.com/BigAPI.yaml or the BigAPI.yaml URL for your BigID instance, and environment server variable set to your BigID hostname. For REST API, set the base URL to https://HOSTNAME/api/v1.
2. Set Authentication to Custom Auth. Add an API Request step that sends POST /api/v1/refresh-access-token with your BigID user token in the Authorization header. Add a Define a variable step named SYSTEM_TOKEN with value {{ http1.body.systemToken }}. Add an Authorization header on the resource that uses {{ SYSTEM_TOKEN }}. Enable Run this custom auth workflow without prompting the user. Configure a refresh auth workflow that repeats the exchange after a non-200 response. Generate the user token in the BigID UI and exchange it as described in BigID's token authentication.
3. Open each app, workflow, and Query Library query that uses the BigID resource. Change the query to use the new resource, then test it. For OpenAPI, select the same operation. For REST API, recreate the request as method and path, such as GET /ds-connections. If the OpenAPI query editor shows an Authorization parameter, leave it empty.

Custom authentication is not supported in public apps. If you have a large number of BigID queries and need help finding them, contact Retool Support.

Retool is deprecating the dedicated Vertica resource type.

Retool will remove the resource type in Q1 2027, after two quarterly Stable releases. After removal, Vertica resources will stop working. Queries in apps and workflows that still point at those resources will fail. Retool will no longer ship the Vertica JDBC driver. Cloud organizations will not have a Vertica connection option after removal.

Self-hosted organizations can keep querying Vertica after removal by creating a JDBC resource and adding a Vertica JDBC driver that you provide. Retool will not migrate Vertica resources or their query references automatically.

1. Download the Vertica JDBC driver from Vertica.
2. Add the .jar file to your self-hosted instance. Follow the JDBC configuration steps for JDBC_DIRECTORY_PATH.
3. Create a JDBC resource with Driver name com.vertica.jdbc.Driver, connection string jdbc:vertica://HOSTNAME:5433/DATABASE?user=USERNAME&password=PASSWORD&DisableCopyLocal=true, and schema query select table_name, column_name, data_type, table_schema from columns. Include DisableCopyLocal=true on the connection string.
4. Open each app and workflow query that uses the Vertica resource. Change the query to use the new JDBC resource, then test it.

JDBC resources do not support Retool-managed SSH tunnels. If your Vertica resource uses an SSH tunnel, or you have a large number of Vertica queries and need help finding them, contact Retool Support.

Retool is deprecating versions 1.0 and 2.0 of the Microsoft SQL integration. Organizations with Microsoft SQL resources still using these versions must update their resource configuration to use version 3.0.

This deprecation will first take effect on cloud instances on August 24, 2026. It will then take effect in the next edge and stable releases that follow.

Version 3.0 has been available since February 2, 2026 for cloud instances and the 3.334 stable release. If you haven't intentionally created a resource on an older integration version, your resource is likely already on version 3.0 and requires no changes.

To upgrade an existing resource, open its settings from the Resources page, change Connector version to Version 3.0, and save your changes.

Versions 1.0 and 2.0 will be removed entirely from cloud instances in Q4 2026, followed by the subsequent edge and stable releases. After that, apps, workflows, and queries that depend on Microsoft SQL resources still using version 1.0 or 2.0 will stop working.

Retool is phasing out support for MongoDB Server version 3.4 and earlier. Organizations with an unsupported version of MongoDB Server connected to Retool must upgrade to MongoDB Server 3.6 or later.

• For cloud organizations, support for MongoDB Server 3.4 and earlier has already been removed.
• For self-hosted organizations, support for MongoDB Server 3.4 and earlier will be deprecated in the Q2 2026 stable release. It will be removed in the Q3 2026 stable release.

MongoDB Server 3.4 has been end of life (EOL) since January 2020. We recommend upgrading to a currently supported MongoDB release.

Python 3.10 will reach end of life on October 31, 2026. After this date, Retool will no longer support Python 3.10 in Workflows.

What's changing​

New and existing workflows on Python 3.10 will continue to run but they will not be supported. They will not be automatically migrated to a newer version.

How to upgrade existing workflows​

Python 3.14 is rolling out to cloud instances and will be available in an upcoming self-hosted release.

1. Open the workflow and go to the Languages & Libraries tab.
2. Click ... next to Python and select Update version.
3. Choose Python 3.14 and click Apply.

When you upgrade, Retool automatically identifies built-in libraries your workflow uses and installs them as custom libraries. Python 3.14 is mostly backwards-compatible, but Retool recommends publishing a workflow release before upgrading so you can revert if needed.

See Configure Python version for full details on how to upgrade and revert to a previously published release.

Timeline​

Retool no longer supports the Llama 4 Maverick or Llama 4 Scout AI models in Retool AI. The Kimi K2 Instruct model will be used instead.

Retool has deprecated version 1.0 of the Databricks connector. If your organization has any Databricks resources that still use this connector version, update the resource configuration to use the version 2.0 connector.

Self-hosted customers must also enable the Java DBConnector to use version 2.0 of Databricks connector.

Change the connector version from the Databricks resource's configuration settings. Any existing queries that previously worked with version 1.0 will continue to work with version 2.0.

The option to use version 1.0 of the Databricks connector will be removed in Q2 2025 from cloud instances and subsequent releases for self-hosted instances.