6 posts tagged with "workflows"

We are excited to announce improvements to the loop blocks are now available in beta both Cloud and self-hosted deployments, versions 3.42 or later. If you'd like to participate in the beta, complete this form to request access.

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

Iteration-level timeout​

Loop block v2 allows timeouts of up to 30 seconds per iteration when executing the entire workflow.

Execution modes and delays​

Loop block v2 supports parallel, sequential, and batched execution modes with iteration delays.

Improved iteration-level error handling and metadata​

It is now possible to ignore iteration errors so that subsequent iterations can still run. In addition, metadata for each iteration is now exposed and accessible in subsequent blocks.

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.

We're excited to announce that Retool Workflows is now generally available. Workflows is a visual automation product that lets you compose APIs and database queries with code (JavaScript or Python) to automate work. It combines the ease of drag-and-drop with the extensibility and reliability of code that engineers need for production-grade work. We've also integrated it with the rest of the Retool product so you can extend workflows with user interfaces or vice versa.

Read the blog post to learn more about Workflows, check out the documentation, and start building for free.

The Response block in Retool Workflows allows for synchronous webhook runs. Workflows can now return data as a webhook response at any time during a run or upon completion.

The Response block works in conjunction with the Webhook trigger and enables you to configure your own responses. You can specify the HTTP status code and a JSON response body to return, which can include any data from the workflow. For example, use a workflow to look up a customer's mailing address based on their email, use multiple blocks to return different types of data depending on execution logic, or even use a Response block as an error handler to signal that something went wrong.

Response blocks are represented as a new block type; just drag out a block, select Response in the context menu, and your webhook will now wait until the Response block is executed to return. Check out the docs to learn more.