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.

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.

Admins can now customize the Content Security Policy (CSP) that Retool enforces on apps. Retool applies a strict default policy that restricts which origins an app can load scripts, fonts, images, and other resources from. You can now extend that policy org-wide to allow the additional origins your apps need, or tighten the defaults further.

For example, if custom JavaScript in an app loads a charting library from a CDN such as https://cdn.example.com, the default script-src 'self' policy blocks the script and the app fails to render it. You can now add that origin to script-src so the app can load it without loosening the policy for any other resource.

Configure rules in Settings > App security > Content Security Policy. Changes apply to every app in your organization and are recorded in your audit logs.

For more information, refer to Customize the Content Security Policy for apps.

While prompting from the Chat tab in the new app builder, you can now restore the app to a previous state. Each time the agent finishes making changes, it presents a summary of the changes and a Restore button. Click this button to return your app to the state it was in when the agent finished those changes.

Retool now supports audio and visual browser notifications for app building. If you prompt Retool to build an app and navigate away from the tab, a ping sounds and a red dot appears on the favicon of the tab when you need to return to it. Now, you can multitask and return to the app builder only when your input is required.

This notification occurs at the following key points in the building process:

• The agent needs you to provide input or make a choice (such as selecting a resource).
• The agent needs your approval to run a function.
• The agent is finished building.

To turn off the notification sound, click the Model options selector in the prompting box and toggle off the Sound notifications setting.

You can now use Retool's MCP server to import React apps directly from your agentic coding environment.

Open a React app, and ask Retool to import the app. Retool guides you through the process of selecting the appropriate resources, and sends you a link to the newly imported app in the app builder. From there, you can make tweaks to the generated app, and securely publish the app using the MCP server or from the app builder.

Retool's new app builder now supports importing React apps from external sources, such as Replit, Lovable, and Claude Code, for further refinement and development in Retool.

To import your React app in Retool, generate a .zip file of the code, and select Import React code from the app builder. Learn more about how it works.

Apps created with the new app builder can now be protected and checked into your chosen Source Control Manager (SCM). Source Control lets organizations manage changes using remote SCM providers GitHub, GitLab, AWS CodeCommit, Bitbucket, and Azure Repos. Using this distributed approach, your users can:

• Prevent unwanted changes to apps.
• Work collaboratively and methodically through reviews.
• Edit React code from your preferred development environment.

To get started, first protect your app. Then you can create, publish, and tag new versions.

Builders on cloud instances can now use Retool's MCP server to build apps. Apps are built using React and use Retool's updated app builder. Connect the MCP server to Claude, ChatGPT, Codex, Cursor, Kiro, or another agentic coding environment, and describe the app you want to build. Retool's building agent generates the app and returns a preview link. Publish and manage the app from the app builder.

Beyond initial generation, you can also use the MCP server to:

• Continue building or iterating on an existing app.
• Monitor active builds and view past agent activity.
• Review function runs that require human approval.
• Inspect or read the files of an existing app.
• Cancel a failed or in-progress build.

App building tools require the user to be a builder, and the builder must authorize the mcp:write scope. Refer to the tools reference for the full list.