Retool now supports the Login Attempted Retool Event, which triggers after a user authenticates and before the login process is complete. You can use Login Attempted to trigger a workflow and execute custom logic, such as modifying user data or querying external resources.

Choose to present users with an error message, or redirect them to an app or URL.

You can only attach one enabled parent workflow to this Retool Event. Retool recommends that this logic remain lightweight, because this workflow runs synchronously in the login flow and blocks users from accessing their Retool account until the workflow finishes.

Retool made several improvements to the usage of Source Control with Retool Workflows. The following features are now supported on Enterprise plans:

• Branched changes. You can now make changes to workflows using branches. Previously, all Source Control changes on workflows were branchless.
• Multi-element branching. You can make edits to workflows on the same branch as edits to apps, modules, and Query Library queries.
• Collaborative branches. Multiple users can commit changes and merge pull requests on collaborative branches.

This change is currently rolling out on Retool Cloud and is available in private beta for self-hosted organizations.

Multi-step functions are now available as a public beta in Retool Workflows on Retool Cloud and on self-hosted organizations. They operate as self-contained workflows with optional parameters.

Multi-step functions improve the Workflows experience in several key areas:

• Isolating complex operations with many steps.
• Enabling nested looping, replacing the need for multiple subsequent Loop blocks operating on the same piece of data.
• Eliminating the need to call a workflow from within another, therefore decreasing the number of billable workflow runs.
• Enabling builders to reuse blocks of code within a single workflow.

Use the Wait block to pause workflow execution for a specified amount of time. This block is useful for creating a single process that might need to take several hours, days, or weeks. For example, you could use the Wait block to:

• Grant a temporary access token, and revoke it after 24 hours.
• Send abandoned cart emails 1 hour after a customer leaves the website, and again after two days.
• Add a delay between several API calls in a loop to avoid hitting rate limits.

After the Wait block finishes executing, the workflow continues execution of the blocks downstream. Wait blocks only pause execution for blocks that are directly downstream, and they not do not affect blocks that are executed in parallel.

Workflow blocks, which enable you to trigger one workflow from another, now support two execution modes:

• Finished: The current workflow execution is paused until the triggered workflow run has completed.
• Queued: The current workflow execution continues and the triggered workflow run is queued. Both workflows may run simultaneously.

Query triggers, a new method for triggering workflows, are now available. Query triggers poll for messages from Amazon SQS and Kafka resources and execute a workflow's run for each message. These triggers are configurable to poll for messages on an interval or on a cron schedule.

Custom Python libraries fpr Retool Workflows is now available as a public beta. You can add one of the built-in Python libraries or provide a custom list of libraries and versions.

A new and improved version of the Loop Block is now available in beta. If you'd like to participate, complete this form to request access.

The new Loop Block features:

• Iteration-level timeout of up to 30 seconds when executing the entire workflow.
• Parallel, sequential, and batched execution modes with iteration delays
• Improved iteration-level error handling to allow subsequent iterations to run.
• Iteration metadata that is accessible in subsequent blocks.

Once enabled, any new Loop blocks added to workflows will use Loop block v2. Existing Loop blocks will continue to function as before.

You can now use configuration variables within workflows. Both values and secrets are supported and can be referenced using:

{{ retoolContext.configVars.YOUR_VAR_NAME }}

You can now use AI to generate fully functional workflows instead of assembling blocks or writing logic. You provide some instructions and Retool assembles the required blocks with any necessary logic. You can also select a database resource and provide context about table schema.