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.

You can now trigger workflows from functions in the new app builder. Converting classic apps that trigger workflows is now supported as a result.

To trigger a workflow from your app, open the Chat tab and prompt your agent with the workflow's name.

Update my app so that the Customer Feedback table retrieves data using the Retrieve Survey Feedback workflow.
Create a new app that tracks our quarterly sales KPIs. For the data, use the Calculate Conversion Rate workflow as well as the lifetime_value and quota_attainment tables in @Retool Database.

The triggered workflow is run on behalf of the app's authenticated user.

Classic apps that include custom components and organization-level themes can now be converted to the new app building experience.

To support custom components, the agent investigates the custom component and recreates it in the converted app with as few changes as possible.

To support classic organization-level themes, the agent applies the same style, color, and typography to the app as were represented in the organization-level theme. The agent does not create a new organization-level theme that applies to apps created with the new app builder.

Retool now supports publishing apps on custom domains. If you self-host Retool (which inherently uses a custom domain) or use a custom domain on a cloud instance, your apps are published to the domain you define in the following format: https://example.retool.com/rr/app/<appName>.

If your organization uses custom domains, previously-published apps should be republished in order to serve them from the appropriate domain.

Apps published on custom domains are subject to an additional set of limitations that are applied because Retool runs your app inside a sandboxed iframe with allow-same-origin disabled.

note

This change applies only to apps created using the new app builder.