Source Control configuration now supports embedded expressions in sensitive credential fields, including access tokens, passwords, private keys, and SSH keys. This enables secure credential management using configuration variables and secrets.

• On cloud and self-hosted instances, you can reference configuration variables:

  {{ environment.variables.MY_KEY_OR_TOKEN }}
  

• On self-hosted instances only, you can also reference secrets from secrets managers:

  {{ secrets.MY_SECRET.KEY }}
  

Embedded expression support is available for all Source Control git providers: GitHub, GitLab, Bitbucket, Azure Repos, and AWS CodeCommit. The UI includes field captions, autocomplete, and validation to help you use embedded expressions correctly.

Non-sensitive fields like repository names, branch names, and usernames do not yet support embedded expressions.

For Enterprise and Business plans, Retool now allows admins to control access to Assist and its Ask and Build modes. Organization admins can use roles and permissions to create roles and edit roles with one of the following permissions:

• Use Assist with Ask and Build mode
• Use Assist with Ask mode only
• No access to Assist

By default, all users have access to Assist and both Ask and Build mode through a preconfigured role. This role is called Assist Role or Editor, based on when your organization was created. Organization admins can edit these roles, or they can create new roles with more restrictive permissions.

This change is valuable for organizations that need to limit or prevent Assist usage to specific populations of users. For example, admins might wish to restrict Assist usage to user groups who do not have access to sensitive data or PII. Alternatively, admins could restrict access to all user groups except for a pilot group testing AI tools.

Multi-instance releases are now generally available to cloud instances and self-hosted instances on version 3.330 or later, with support for both apps and workflows.

Organizations using Source Control can manage releases of protected apps and workflows across multiple deployment instances. This feature enables you to publish different release versions across instances, making it easy to test newer versions on staging or development instances before promoting to production.

Retool now supports Azure OpenAI for use with Assist. Admins on the Enterprise plan can configure Assist to use Azure OpenAI as the single model provider for Assist-powered interactions.

Retool designed Assist to use two AI providers by default: OpenAI and Anthropic. Using both providers enables Assist to optimize for speed and quality. However, some customers may need to consolidate AI services with a single provider. To accommodate these customers, Enterprise organizations can configure Assist to work with a single provider.

Retool now supports Amazon Bedrock for use with Assist. Admins on the Enterprise plan can configure Assist to use Amazon Bedrock as the single model provider for Assist-powered interactions.

Retool designed Assist to use two AI providers by default: OpenAI and Anthropic. Using both providers enables Assist to optimize for speed and quality. However, some customers may need to consolidate AI services with a single provider. To accommodate these customers, Enterprise organizations can configure Assist to work with a single provider.

Enterprise customers can now use Source Control to protect workflow triggers. This prevents changes to a workflow's triggers without review. When you protect a workflow for the first time, triggers are now automatically included.

For workflows that are already protected, you now have the option to protect triggers using a new PR.

Once protected, triggers are versioned and published alongside each release. Information about your triggers is stored in the startTrigger.yml file in your Source Control repository.

Enterprise customers can now use the Get IP Allowlist by Region endpoint to programmatically retrieve Retool's IP addresses. If you make use of inbound firewall rules, include the following IP addresses in its allowlist so that Retool can access your resources.

The Fullstory integration for session replay is now generally available.

When enabled, data about user interactions with apps are reported directly to Fullstory for you to review in detail. You can then analyze app analytics, evaluate impact, and review interactions with session replay. This integration is useful for monitoring user activity across different apps, and using advanced analytical tools like heatmaps and funnels to identify usage patterns, debug errors, and improve the overall user experience.

Enterprise customers can send page load and query traces to Datadog and Sentry using Retool's performance monitoring integration, now in public beta. Customers can respond proactively to regressions and troubleshoot more quickly by creating dashboards and alerts to monitor the performance of their apps and use the spans themselves to help pinpoint where to take action if their apps are degraded.

Internationalization (i18n) is now generally available for organizations on the Enterprise plan. This allows you to localize Retool app content and data.