The Flow Designer, where you build and manage your integration flows, has been migrated from Ember.js to React. This significantly modernizes the Flow Designer’s underlying technology and provides a modern foundation for maintaining and extending the flow-building experience.
The Flow Designer now supports copying and pasting action steps, making it easier to build and extend integration flows without configuring similar steps from scratch.
Each action step in the flow graph has a Copy button to the left of its component. Clicking this button copies the step’s configuration details and saves them to the browser’s local storage, allowing you to paste the copied step into the flow.
When a step has been copied, a red Cancel button appears on the left side of the Designer header. Click Cancel to clear the copied step details and discard the pending copy operation.
To reuse a copied step, use the paste functionality in the Designer. A new step is created using the copied configuration, so you can reuse existing settings instead of manually configuring the same component again. After the step is pasted, the copied data is automatically cleared from the buffer.
This functionality helps reduce repetitive configuration work, speeds up flow development, and makes it easier to reuse existing step configurations when building integration workflows.
Note: Only action steps can be copied and pasted. To use this functionality your flow must be in Draft mode. The Error Handler step can’t be copied.
Previously, mappings referenced the previous step’s body directly. If a new step was inserted between the original step and the mapping step, the mapping could break.
Mapping data is now always taken from passthrough, even when the data originates from the previous step. With this improvement, mappings use passthrough as the data source, helping preserve existing mappings when steps are inserted into a flow.
Added a new auth type for Auth Clients - oauth2_client_credentials. To use it, specify "authClientTypes": ["oauth2_client_credentials"] in component.json. It can be used together with the oauth2 type to let users choose which authentication to work with.
Example of component.json:
"authClientTypes": [
"oauth2",
"oauth2_client_credentials"
]
Credential IDs are now fully displayed on the Credentials page, regardless of the credential name length. Previously, IDs could be truncated with three dots when the credential name was too long.
FileTextView view in the credentials widgetA new FileTextView view has been introduced with the following additional parameters:
accept - a comma-separated list of allowed file extensions in the format .fileExt,.fileExt2, for example, .txt,.crt. Default value: *, which allows files with any extension.maxlength - the maximum allowed file size in MB. Default value: 5.Example of the component.json credentials object:
"requiredFileField": {
"viewClass": "FileTextView",
"accept": ".txt,.crt,.jpg,.png",
"maxlength": "5",
"required": true,
"label": "Required File Field"
}
mandrillApiKey when sending emails, even when the platform-level SMTP adapter is enabled. Tenants without their own Mandrill configuration continue to use the platform SMTP configuration as before.1.7.2/oauth/v3/token in the documentation to comply with HubSpot’s v1 OAuth API deprecation@elastic.io/component-commons-library version from 4.0.0 to 4.0.3axios version from 1.17.0 to 1.20.0elasticio-sailor-nodejs version from 2.7.8 to 2.7.92.0.324.x@elastic.io/maester-client version to 6.0.3@elastic.io/component-commons-library version to 4.0.3elasticio-sailor-nodejs version to 2.7.92.0.018.x to 24.xmongodb version from 3.5.9 to 7.6.0 (unified driver supporting MongoDB 4.0+)uuid version from 8.2.0 to 11.1.1elasticio-sailor-nodejs version from 2.7.1 to 2.7.9elasticio-node dependency and transitioned to local utilitiesObjectId support to the Delete By Unique Criteria actionnull or undefined fieldsObjectId handling across all actions:
ObjectId('...') template wrappersObjectIds, nested filter operators ($eq, $in, $or, $and) and double-quote syntaxObjectId template conversion to Aggregate pipelines and Bulk Write operationsmongoVersion selection (now handled automatically by the unified driver)1.2.0Number of retry attempts (retryCount) configuration field (default: 3, max: 5)Initial delay between retries (in seconds) (initialDelay) configuration field (default: 1s, max: 10s)Retry 404 (Not Found) (retryOn404) checkbox to optionally retry 404 Not Found responses for eventual consistency workflowsDo not throw error on failed calls (dontThrowErrorOnFailedCalls) checkbox to the Trigger another flow action:
statusCode on non-2xx HTTP responses without failing the stepstatusCode alongside the result on successful calls when enabled@elastic.io/component-commons-library version from 3.2.0 to 4.0.3elasticio-sailor-nodejs version from 2.7.2 to 2.7.9axios version from 0.27.2 to 1.20.0elasticio-node dependency and replaced it with a local message envelope utilityelasticio-rest-node dependency1.1.024.x@elastic.io/component-commons-library version from 4.0.0 to 4.0.3elasticio-sailor-nodejs version from 2.7.7 to 2.7.9axios version from 1.12.2 to 1.20.0fast-xml-parser version from 5.3.2 to 5.11.11.0.0Get New and Updated Events Polling triggerGet Canceled Events Polling triggerGet New and Updated Registrations Polling triggerCreate or Update Event actionDelete Event actionGet Attendees actionGet Calendar Info actionGet Event by ID actionGet Events actionMake Raw Request action1.4.0SMTP_URI environment variableelasticio-sailor-nodejs version to 2.7.9@elastic.io/component-commons-library version to 4.0.3axios version to 1.20.02.0.10elasticio-sailor-nodejs version from 2.7.7 to 2.7.9test.yml and publish_release.yml)1.3.124.xelasticio-sailor-nodejs version from 2.7.5 to 2.7.9axios version from 1.8.4 to 1.20.0elasticio-node and elasticio-rest-node and replaced them with native local message utilities5.0.2HttpUtils.createHttpClient). This resolves infinite thread blocking during large message (Object Storage / Maester) uploads when network sockets stallGuava version from 33.2.1-jre to 33.6.0-jreLogback version from 1.2.13 to 1.3.14commons-logging pinned to 1.4.0 to mitigate transitive log4j 1.x CVEs from httpclientlogback-contrib dependencies (logback-json-classic, logback-jackson)BunyanJsonLayout reimplemented as a standalone LayoutBase using Jackson directly, replacing the removed logback-contrib JsonLayout