Release Notes

New Features

HTTP Integration Node

Add Integration HTTP Node: Introduces a new Integration Node that allows users to make HTTP requests to external services or APIs. This Flow node enables seamless integration with third-party systems, facilitating data exchange and expanding the capabilities of the platform.

With this new HTTP Integration Node you have the ability to:

• Use GET, POST, PATCH, and DELETE methods.
• Dynamically or statically provide the URL.
• Configure static or dynamic key value pairs in the Headers and Search Parameters.
• Structure a static or dynamic body that can be structured as text or JSON.
• Structure the expected results to be available to rest of your Flow.
• Receive the Status of the call by default.

Showing the new Integration HTTP Flow Node.

Scheduled Flows

Add ability to schedule a Flow execution for a later date: You can now schedule a Flow to execute at a specific date and time in the future. This allows you to automate processes and tasks without having to manually trigger the Flow. When scheduling a Flow, you can select the desired execution date and time, and the Flow will run automatically at the scheduled time. This new scheduling capability provides more flexibility and control over your automated workflows.

Showing the new scheduled configuration on the Flow Execute Node.

When a Flow has been scheduled but not yet executed you can see it in the Flow Executions table with a status of scheduled and a timer icon in the started/scheduled column.

Showing an example of a scheduled Flow in the Flow Executions Table.

Data Expression Node

Add data:expression node: Introduces a new Flow node that allows you to write an expression with dynamic inputs to compute a result. This feature enables you to perform calculations and data transformations within the Flow using a flexible expression syntax.

Showing the new Data Expression Node with an example two inputs and mathematical calculation.

Add addDuration function to the Expression Node: Introduces a new addDuration function to the new Expression Node, allowing users to add a specified duration to a dateTime input. The function takes three parameters: a dateTime value, an integer value, and a time unit (e.g., hours, minutes, seconds). This enhancement provides a convenient way to perform date/time calculations within the Expression Node, enabling more complex and dynamic data transformations. Note; this function currently takes in time units only not date units (days, months, years).

Showing the new Data Expression Node with an example addDuration that is taking a dateTime as input and adding 5 minutes to it.

Enhancements

LLM Chat Node - Repeated Message Templates for Multi-turn Conversational History

LLM Chat Node - Repeating message templates: Adds the ability to define sets of repeating messages within the message templates section of the LLM Chat Message Flow Node. This introduces support for proper turn-based conversations with a Large Language Model (LLM) by allowing a dynamic number of messages to be exchanged.

Showing the new Add Repeating Group configuration option on the LLM Chat Message Node with an example of looping through the history of the conversation with the User Query and Assistant Responses.

Flows

Add support for specifying Content as a Flow return type: The Flow editor now allows you to configure the Flow Result to return a Content property, enabling you to extract and return content-based data from within your Flows. This enhancement provides greater flexibility in designing Flows that process and return content-based data, streamlining content-related operations and integrations within the platform.

Add object:unlink node: This new node removes an existing relationship by supplying the fromId and toId into the Node. This is the counterpart to the object:link Node.

Add In and Not In operators to the Filter Builder: This update enhances the Filter Builder by introducing two new operators: In and Not In. These operators allow you to query whether single or multiple data points are included or excluded from a dataset. For example, you can use the "In" operator to retrieve all entities whose IDs are included in a provided list, or the "Not In" operator to exclude entities with specific IDs from the results. This improvement streamlines the process of filtering and retrieving data based on lists of identifiers, enabling more efficient and flexible querying capabilities within the Flows.

Add isNull and isNotNull operator types to the query filter: This work item introduces two new operator types, isNull and isNotNull, for the query filter. These operators allow users to filter results based on whether a specified field has a null or non-null value, respectively. This enhancement provides more flexibility and control when constructing complex queries, enabling users to better refine their search criteria and retrieve more relevant data.

Flow Execution Logs

Add defaultLogLevel and log level selection to flow editor and flow execution respectively: This update introduces the ability to set a default log level for Flows in the Flow editor, as well as the option to select a specific log level when executing a Flow. The log level determines the amount of logging information that will be captured during Flow execution, allowing users to control the verbosity of the logs based on their needs. This enhancement provides greater control and flexibility over the logging process, enabling more efficient debugging and troubleshooting of Flows. Additionally, API endpoints have been updated to support this new functionality. You can read more about this update in the Flows: Understanding Execution Logs Knowledge Base Article.

Improve Flow Execution log details for list:map node: The update enhances the Flow Execution log by surfacing the list:map node ID on the subItemContext in the Span column. This improvement provides more detailed information about the execution of list:map nodes, allowing for better visibility and troubleshooting capabilities within the Flow Execution logs.

Quality of Life

• Improve API Datetime Handling for UTC Timestamps.
• Fix Pathname Parameters for UX Action Navigate.
• Fix media resizing handle visibility in content area.
• Resolve Copy Inputs to New Execution Functionality Issue.
• Resolve Content Rendering Issues in Entity Table.
• Update the "Experience" parameter type from "object" to "string".
• Update default API body limit to 16mb.