Google Docs integration
Retool now supports an integration to Google Docs, which utilizes the Google Docs API and the Google Drive API. Use this integration to retrieve, create, and update documents.
Updates, changes, and improvements at Retool.
Retool now supports an integration to Google Docs, which utilizes the Google Docs API and the Google Drive API. Use this integration to retrieve, create, and update documents.
Retool can record user behavior and interactions with apps using Fullstory. 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.
The backend runtime in self-hosted Retool 3.163 and later has been upgraded to use Node.js v20.18. This change may result in memory and CPU usage of containers to increase. Without sufficient resources, this could impact the performance of Retool Workflows. If necessary, you can increase the memory limits for workflows using the WORKFLOW_MEMORY_LIMIT_MBS environment variable.
If your organization uses Source Control, Retool sometimes creates an automatic commit, called a catch-up commit, which keeps your branches up to date. If you want to ensure that developers in your organization retain complete control of changes within their feature branches, you can now disable catch-up commits using the following steps:
If you disable catch-up commits, users in your organization must manually, outside of Retool, rebase their branch and resolve conflicts in order to keep their branch up to date.
To avoid issues with catch-up commits and other merge control mechanisms, refer to Retool's Merge conflict prevention strategies.
Multi-step functions are now generally available 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:
Existing users of functions can continue using their functions as normal. Functions that were created previous to this release are now treated as single-step functions.
You can now connect your organization to Sentry and Datadog for workflow error monitoring and event logging.
To set up error reporting, go to the Settings and navigate to Configuration > Observability. Enter your Sentry and Datadog credentials to emit workflow errors and run events to either or both providers.
Connecting to external observability providers is especially useful for your organization if:
Retool updated the Export to Module feature for usability improvements. This feature allows you to select components on the canvas and “refactor” them into a module.
The following key changes were made:
Access Export to Module in one of the following ways:
When publishing your workflows, you can now choose to publish any changes to child workflows. This update streamlines workflow publishing by eliminating the need to manage releases separately. If you make a change to a referenced workflow, these changes are automatically detected when publishing the parent.
Retool recently made a series of improvements to the Run panel and other mechanisms that are commonly used to debug workflows. These changes include:
workflowRunContext
to the Input tab of block outputs.endedAtEpochMs
to workflowRunContext
in the Input tab of block outputs.To take advantage of these improvements, use the following best practices:
workflowContext.currentRun.workflowRunId
and workflowContext.lastRun.endedAtEpochMs
. You can also emit both properties by default by connecting your Retool organization to Datadoog or Sentry. Having the workflowRunId
and timestamp
handy at debug time will allow you to quickly filter workflow runs to the errored workflow run.Retool no longer requires NsJail to use custom JavaScript libraries and custom Python libraries in workflows on Self-hosted Retool. If your team is unable to grant privileged container access, this change enables you to still use custom libraries.
While no longer required, Retool still strongly recommends using NsJail with privileged container access, as it provides sandboxing and remains the most secure option.