Changelog

Checklists are a great way to nudge users to take actions in your app. With our new Floating Checklist example you can add one into your product in minutes. The UI is fully customizable to fit your brand and like all our examples it comes with full source code. See it in action here.

Flows 1.0 shutdown

As of March 31, 2025, Flows 1.0 has officially been shut down, marking the end of an important chapter. We are grateful to all our early users who helped shape the product. Flows 2.0 is a complete rewrite of the product and we are excited to continue building the future of product adoption with you.

Improved design of built-in Tooltip and Modal

Our built-in Tooltip and Modal components have been refreshed with a more polished design. The new design includes transition animations that make the components feel more fluid and responsive. Update your SDKs to enjoy these improvements, but watch out for possible breaking changes in CSS.

Other improvements

• Added an indicator to the user detail page to show if the user counts toward MTUs for the current billing period
• Added recent workflows widget to the Home page
• Improved performance of block template form when editing larger templates
• Optimized periodic usage notifications to reduce backend load and response times

Bug fixes

• Fixed a bug where default values were not properly set for all block properties when adding a new block to a workflow

Manual start block allows you to start a workflow manually from the SDK by calling startWorkflow function. Learn more in docs.

Set state memory from SDK

You can now set the state memory value from the SDK by calling setValue function in the active block. We've also added more information about the memory configuration to the block properties. Learn more in docs.

Other improvements

• Workflow environments dialog now shows the frequency next to the active version.

SDK improvements

• Added workflow ID to active block response.
• Sped up exit node execution - now it doesn't wait for network requests to finish.

Bug fixes

• Fixed a bug where the workflow editor could save a broken page targeting condition, resulting in the block never showing.
• Every block property now shows its description in the editor.
• Fixed a bug where the tooltip sometimes didn't render in the right place when showing on animated elements.
• Fixed modal overlay z-index sometimes not overlaying all elements.

Block key allows you to define a persistent, unique identifier for a block, making it easier to reference in your code. Learn more in the docs.

Better tables

Workflow, User, and Block tables now display more detailed information. You can track workflow statuses, the number of active workflows for a user, and the last updated date for block templates among other things.

We've also improved the pagination in the Users table, now even with a lot of users, you can easily navigate through them.

Tour wait delay

Setup a delay between tour steps to give users time to process content or wait for elements to load. Learn more in the docs.

SDK improvements

• Added resetWorkflowProgress and resetAllWorkflowsProgress functions to the JS and React SDKs.
• Added useCurrentFloatingBlocks and useCurrentSlotBlocks hooks in the React SDK. Use them to track active blocks and trigger actions in your product.
• Fixed an issue where the tooltip rendered even when the target element didn't exist on the page.

Other improvements

• Paths with identical origins and destinations are now grouped in the workflow editor, preventing overlapping exit node labels.
• Added equals and not equals operators to page targeting.
• Tour steps can now be reordered with drag-and-drop.
• Added unique key validation for block template properties and exit nodes.

Bug fixes

• Fixed an issue where the Environments dialog sometimes failed to load fully.
• The workflow updated at column now displays the correct date.
• Improved performance when publishing a new workflow with a lot of users.

These new block properties finally enable building onboarding checklists and hubs.

State memory property

Use a boolean value stored in the block’s state to keep track of user progress. This lets you mark whether someone has finished a certain task or seen a particular message. State memory is perfect for onboarding flows or checklists where you need to remember the user’s progress.

Block trigger property

With the block trigger property, you can launch one block directly from another without exiting the current block. This is useful for starting a tour or opening a modal from an onboarding checklist or hub.

SDK improvements

• Added a template for using the Flows JS SDK in Angular applications. Check out the Angular template in the Flows SDK repository.

Bug fixes

• When adding a wait step to a tour, the add popup now closes right after the step is added
• Workflows no longer display to active users once the workflow live status is turned off

Create checklists or collections of useful links with the Array block property.

With arrays, you define a fixed structure that every item in your list follows. This is ideal for dynamic lists where each entry has consistent attributes like a title and a URL. To learn more about setting up and using the Array block property in your workflows, visit our array block property documentation.

This block property brings us one step closer to supporting onboarding checklists and hubs.

Improved documentation

After the dust settled from the Flows 2.0 release, we took a step back to improve our documentation. We've restructured the content to make it easier to navigate and added more step by step guides to help you get started with Flows.

We also took the opportunity to switch from Nextra to Fumadocs, a more flexible and feature-rich documentation framework. This change will allow us to create better documentation that also looks great.

Other improvements

• Added reset password functionality
• Adding blocks to the workflow is now faster
• When adding a new block, they will no longer hide an existing block
• String input in blocks now overflows to multiple lines, making it easier to edit long strings
• Improved how the number property input behaves when entering negative values

Bug fixes

• Fixed an issue where duplicate paths could sometimes be created when connecting blocks.

To make Flows 2.0 more accessible to a wider range of developers, we have introduced a JavaScript SDK. This new SDK offers functionality similar to the React SDK but is designed to be framework-agnostic, allowing it to integrate with any JavaScript application.

To see how it works, check out our Nuxt template, which demonstrates how the JavaScript SDK can replicate the functionality of the React SDK example. For additional details, refer to the JavaScript SDK documentation.

Workflow Examples

Saying "you can build anything with Flows" is one thing, but showing it is another. That’s why we’ve released an examples library showcasing various workflows built with Flows.

The examples are open-source and can be used as a starting point for your own workflows. We will be adding more examples in the future, so stay tuned.

Other improvements

• The right sidebar in the workflow editor is now resizable, enhancing the editing experience
• Workflow validation now checks for slottable blocks missing a slot ID
• The React SDK has improved test coverage
• Websocket event handling in the React SDK has been optimized

Bug fixes

• Removed extra bottom spacing when no footer buttons are present in built-in components

To make it easier for new users to get started with Flows, we've added a getting started guide that will walk you through the basic setup of Flows and creating your first workflow. The guide is powered by Flows and will be shown to everyone on their newly added Home page. We are planning to add more content to the Home page in the future, so stay tuned for more updates.

Workflow validation

We've added basic workflow validation when publishing a new version of a workflow. Now you get warned when publishing a workflow without a start block or with a block that is not connected to anything. This should help you catch some common mistakes before they happen.

Bug fixes

• Fixed a bug where when a step in a tour block was deleted out of sequence, no new steps could be added
• Fixed a few text overflow issues throughout the app
• Fixed a bug where clicking on sidebar links right after logging in would result in a broken state

This release is all about cleaning up and fixing bugs after the Flows 2.0 release.

• Tour-specific blocks now display built-in exit nodes when creating a tour block template.
• Added validation to environment key to make creating valid keys easier
• Workflow auto-save now retains focus on the field you’re typing in, so you don’t lose your place

Bug fixes

• Resolved an issue where the checkout link pointed to the wrong subscription plan
• Various small fixes and improvements following the Flows 2.0 release

We're thrilled to announce the launch of Flows 2.0! This release marks a significant step forward for us, and we can't wait to see what you'll create with it.

What's new

We've completely rebuilt Flows, transforming it from a basic onboarding tool into a powerful platform for crafting fully custom in-app experiences. Here are the key features:

• Workflow: Create complex, multi-step experiences that span multiple sessions or even the entire user lifecycle.
• Tour: Step-by-step guides that lead users through processes.
• Custom UI components: Build and integrate your own UI components within Flows.
• Slottable components: Dynamically embed components into your application.

Read the full announcement on our blog.

How to migrate

Unfortunately, existing Flows cannot be automatically migrated to the new version. However, we’ve prepared a migration guide in our documentation to help you transition to Flows 2.0. If you have any questions or need assistance, our team is here to support you.

The old version of Flows will be shut down on March 31, 2025. Please ensure your Flows are migrated before this date. To ease the transition, Flows 1.0 usage will be free for everyone during this period.

PS: We've removed most of the old changelog entries, as they are not relevant after this release. You can still find them in the public GitHub repository.

To better reflect our mission and values, we've updated our branding. We wanted to reflect that Flows is a tool for builders to create anything they can imagine. We are excited to share this new look with you!

Today is the day... We're finally launching our Beta for Flows! This has been in the works for the past 6 months, and we appreciate all the support and feedback you've provided while we've been building. ❤️

The beta is open to anyone, so go ahead and sign up!

We need feedback! Please ping us in the app and let us know what you liked and what we could improve.

Again, thanks for being part of this journey. It really means the world to us to have you onboard.

We are starting on the journey of creating Flows - the next generation tool for creating onboarding flows and product tours. Read about our mission and the principles we use to build Flows in our first blog post.