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.

Business and Enterprise organizations can now use the Retool API to authenticate apps that are embedded in an app or website external to Retool.

Once configured, the custom authentication flow exchanges an API token for an embed URL. When a parent app authenticates a user using your preferred authentication method, the parent app makes an API request to Retool to generate an embed URL. This embed URL is a secure, single-use link on the domain of your published app. Loading it in the iframe exchanges the link for a session, sets the cookies the app needs, and then displays the app.

Standard authentication through Retool remains supported.

note

This flow is available for apps published on a cloud instance that use the standard Retool domain (example.retool.com). It is not available to self-hosted instances or organizations that use a custom domain.

You can now prompt the app building agent to create REST API or PostgreSQL resources directly from the app builder.

Describe the resource that you want to create, and the agent initiates the resource creation process. You'll be asked to provide credentials or more details where applicable.

Best practice

Retool encrypts all resource credentials and never exposes them to the agent.

Organizations on the Team plan can now use Retool-provided AI models for app building, in addition to the full catalog of supported models. These models, prefixed with Retool, have been tuned by Retool for enhanced performance and speed for app building.

The following Retool-provided models are supported:

  • Retool Mini
  • Retool Power