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.

31 posts tagged with "New"

New features and functionality.

View All Tags

Connect MongoDB Atlas with OAuth

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.

Snowflake OAuth for partner applications

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.

Service users for workflows

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.

Retool on Google Cloud Marketplace

Retool is now available on Google Cloud Marketplace. Work with your Retool account team to set up a private offer. After you accept it in your Google Cloud console, Retool is billed through your Google Cloud account. To learn more, read the announcement blog post.

The Retool Blueprints listing enables you to deploy self-hosted Retool to Google Kubernetes Engine (GKE) as a prepackaged Kubernetes app. Deploying Blueprints requires a Retool license key. Blueprints has no usage fee, but Google Cloud charges for the GKE resources you run.

Retool CLI

The Retool CLI is now available in public beta. It enables you to build, manage, and publish Retool-native React apps from the command line and with the help of your chosen code development agent harness, like Claude Code or Codex.

With this tool, you can write and validate app code directly on your machine. You can use the CLI independently or pair it with a local development agent. Follow the installation instructions to get started, learn how the CLI works, or compare the CLI to the MCP.

note

Retool supports an existing CLI that is used exclusively for classic apps. This CLI is now deprecated. It will be removed from cloud instances on March 1, 2027, and from stable instances in the Q2 2027 stable release.

Microsoft Graph integration

Retool now provides a native integration for Microsoft Graph, the unified API for Microsoft 365 services. You can create a Microsoft Graph resource with OAuth 2.0 or Microsoft Azure Identity authentication to read and manage Entra ID users, mail, calendars, OneDrive and SharePoint files, and Teams messages—all from Retool apps and automations.