BluBees Beta v4.1.0: See Inside Every Flow, Build Smarter Workflows

Beta is where we ship and learn. v4.1.0 is our latest update, focused on two things that matter a lot when you're running automation in real workflows: visibility into what's happening inside every Flow, and smarter control over how complex data moves through them.

Here's what shipped.

Step Execution Status: Your Flow, Live

This is the most immediately visible change in this release, and it's one of those things that, once you have it, you can't imagine working without.

Every node on your Flow canvas now shows its execution status in real time. Success, failure, running, waiting, you can see the state of every step at a glance, without opening a separate log window or navigating away from the canvas. Click any node to inspect the full execution details right there.

Integration status is also visible on the node itself, whether a connection is active, synced, or in an error state. When something goes wrong, you know immediately which step it happened on and what the state was at that point.

Visibility isn't a debugging feature. It's a confidence feature. When you can see what your Flow is doing, you trust it more.

Flow Variables: Stop Rebuilding Logic You've Already Built

This one solves a real frustration. In complex Flows, you often need to use the same value in multiple places, a record ID captured early in the Flow that needs to be referenced several steps later, for example. Until now, that meant duplicating field mappings or restructuring your Flow to pass values through.

Flow Variables let you store any field value against a named variable at the point it's captured, then reference that variable anywhere else in the same Flow, across any step, in any field mapping. Manage your variables from a dedicated dialog launched directly from the flow canvas. Define, edit, and delete them as your Flow evolves.

Variable names are unique within a Flow (case-insensitive), and variables are scoped to a single Flow execution, so they stay clean and predictable.

Array Splitter: Process Lists the Right Way

A lot of real-world data arrives as arrays, a list of test results, a batch of customer records, a set of tickets from an API call. The question is always: how do you process each item individually without rebuilding your entire Flow around it?

The Array Splitter node answers that. Drop it into any Flow, point it at an array field, and it handles the rest, routing each item through the logic you define, then triggering a completion step once every item has been processed.

Two modes give you control over how that processing happens:

• Sync mode: items are processed one at a time, in order. Use this when sequence matters.

• Async mode: items are processed in parallel. Use this when speed matters and order doesn't.

A "Continue on error" option means one failed item doesn't stop the entire batch; it gets skipped and the Flow carries on. For production workflows handling real-world data, that resilience matters.

Response Processing: Control How Steps Handle Incoming Data

This is a more technical capability, but an important one for teams building production-grade Flows.

Every step after the first in a BluBees Flow is triggered by the response from the previous step. Response Processing gives you explicit control over what happens at that moment — does the Flow wait for this step to fully process its response before moving on, or does it continue immediately while this step handles its response in the background?

• Async (default): the Flow continues immediately. The step processes its response independently. More scalable, production-safe.

• Sync: the Flow pauses until this step's response is fully processed. Use this when order and completion genuinely need to be guaranteed.

Async is the right default for most workflows. Sync is a deliberate choice for specific situations where you can't afford to move on until a step is done.

Forge Runtime Upgrade

We've upgraded the underlying Forge runtime from Node.js 22 to Node.js 24. This brings performance improvements and long-term support to the platform layer. No changes needed on your end — your Flows benefit automatically.

Bug Fixes

• Visual Conditional Builder: fixed an issue where a saved SpEL expression did not render correctly after saving

• Field Mapping: fixed an issue where the last saved mapping value was incorrectly retained when starting a new field mapping configuration

What's Coming Next

We're continuing to move toward General Availability. The next major capability being built will automatically discover your enterprise tech stack and map out recommended configuration Flows across your tools simultaneously, significantly reducing the time from "I want to automate this" to "this is running."

We continue to ship regularly through Beta. If you'd like to be part of the Beta cohort, reach out, and if you're already with us, everything in this release is live now.

Found a bug or have a suggestion? Our support portal is open: blubees.atlassian.net/servicedesk/customer/portal/1

Interested in joining the BluBees Beta? Visit blubees.ai or install the app from the Atlassian Marketplace to get started.