v1.12 — December 2025
This release broadens the integration scope with new Amazon SQS and FTP nodes, refines the level of trace detail to better balance diagnostics and performance, and brings many ergonomics improvements to workflows, dictionaries and navigation.
Documentation: Workflows · Traces
New features
New nodes and capabilities
- Send AWS SQS node: send messages to SQS queues from your workflows, to orchestrate asynchronous processing and event-driven architectures without leaving the editor.
- FTP nodes (file operations): chain move, delete, read and list operations on files on your FTP servers — useful for batch exchanges, archiving or post-integration cleanup; complete with the File trigger.
- Performance mode for traces: a new trace recording setting where only the nodes in error keep an actionable detail, reducing the load and the volume stored in day-to-day production. To see how it compares with Complete and Standard modes, see Tracing modes and Workflow version management.
- Emails without attachments: ability to send messages without attachment when your scenario does not need one — see the Send an email node.
Improvements
- Navigation: the active environment is preserved while you browse screens — see Introduction to environments.
- Dictionaries: the value of an entry is visible on hover in triggers and workflows, avoiding the need to open each detail screen to check a label or code — see Variable management.
- Traces: bulk replay is possible, with the ability to change the workflow version on replay — see Replay a trace and Workflow version management.
- Workflow and deployment: automatic suggestion of the version number on fork; production deployment remains restricted to the expected main version to secure the release chain; overhaul of the HTTP(S) Request node and simplified GraphQL request for more direct input — see Deploy a workflow.
- File trigger: support for reading files based on the modification date — File trigger.
- Google Pub/Sub event trigger: event attributes are available in the trigger and in the associated Send Google Pub/Sub node, to enrich the business context without workarounds.
- Node catalog: new group-based presentation — see Use the workflow editor.
Fixes and stabilization
- Cartography: fixes on the cartography module — see Cartography.
- Error display: messages and highlighting of errors in workflows are more readable, to identify the node or configuration at fault faster — see Analyze an execution.
- Version fork: when forking, Apps and authentication methods are now duplicated correctly when expected — see Workflow version management and Authentication methods.
- Polling trigger: fixed extractor behavior in edge cases.
- File / XML trigger: correct support for XML files containing only one root element — File trigger.
- Cron: fixed handling of the
Lletter (last business day of the month) in scheduled expressions — Scheduler trigger.