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.

Retool now supports performing web searches from the Chat tab of the app builder and from functions in draft or published apps. While building apps, the agent can access the internet to answer questions or provide more context. Web searches use a Tavily account that Retool manages for you.

Help me find a public npm package to display an interactive map on the page.
Tell me what kinds of things I can do with the latest update to the Linear API.

Your apps can also use functions to perform web searches. Prompt the agent to include the search functionality that the users will need.

When the user clicks the Search button, search the internet and return the top three results for the user's query.

Web search is on by default. Admins can disable this feature by toggling off Web search in Settings > AI.

note

This feature is not available to self-hosted instances.

Retool's MCP server is now generally available on cloud and self-hosted instances using version 4.86 and later. Use the MCP server to interact with Retool from your chosen agentic environment, such as Claude Code, ChatGPT Cowork, or Cursor.

The following use cases are examples of what can be accomplished using the MCP server:

Connect your agentic development environment to the MCP server with the installation instructions, and refer to the tool reference for the full list of available tools.

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

Retool releases a version on the stable channel each quarter. 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.

You can now connect MongoDB Atlas to a cloud instance of Retool by signing in to Atlas. Click Connect MongoDB Atlas on a MongoDB resource, authorize Retool, and choose a cluster and the level of database access to grant. You don't need to create a database user, add an IP address to your access list, or enter connection details.

When you save, Retool creates a dedicated database user scoped to that cluster, adds Retool's IP addresses to the Atlas project's access list, and tests the connection. Deleting the resource also deletes the database user.

Connecting to a MongoDB server with a username and password or a connection string still works, and existing resources are unaffected. Atlas sign-in is available on cloud instances.

Retool is now a Snowflake OAuth partner application. When you connect Snowflake to a cloud instance of Retool with OAuth, you no longer create or manage a client ID, client secret, or redirect URI. Instead, you create a partner application security integration in Snowflake, then click Connect with OAuth in Retool to authorize.

Existing Snowflake resources that use a custom OAuth client continue to work and you don't need to migrate them.

Support for partner application authentication is available on cloud instances. Self-hosted instances continue to use a custom OAuth client.

Workflows triggered by a schedule, a webhook, or a query, can now run as a service user. Service users for workflows are available on Business and Enterprise plans. Previously these runs defaulted to running as the first admin in your organization.

Select a permission group in the Triggers panel of the workflow IDE. Retool creates a service user for the group, and triggered workflows run as that service user. Only members of the group and admins can edit workflows running as a service user, and run logs are limited to people in the service user group.

Key features of this release include:

  • Service users allow workflows run against resources with data access enforcement turned on. Scheduled and webhook-triggered workflows no longer need a separate unenforced resource. Grant the service user group access in your access policies.
  • Service users do not count toward your user seats.
  • Audit logs record actions that a service user performs under the existing event types, with the service user's ID as the actor.
  • Source control includes a workflow's run identity in its YAML file. On deploy, Retool matches the service user by ID, then by group name.

If an admin deletes a service user group, workflows set to run as that group will fail until you choose a new group.

To get started, refer to Run a workflow as a service user. For details on how run identities work, refer to Service users for workflows.