Overview
Starting with Bizagi Summer 2026, the Connector Service introduces support for two Node runtimes running side by side. This change allows Bizagi to evolve to a modern and secure Node runtime, while keeping all existing connectors working without interruption.
For most users, this upgrade is completely transparent. Your existing connectors continue to work exactly as before. At the same time, Bizagi gives you the option to gradually adopt the newer runtime when it makes sense for your project.
This article explains what changes, what stays the same, and when you need to take action.
Why this change is needed
Node version 12 reached its end of life in 2022 and no longer receives security patches or official support. This limits security improvements and prevents the use of modern libraries required by newer integrations.
Node version 22 is the current long term support version and provides:
•Ongoing security patches.
•Support for modern npm libraries.
•Better performance and stability.
•Full compatibility with modern JavaScript syntax.
The main challenge is that some existing connectors were built specifically for Node version 12 and cannot be automatically upgraded. The new architecture solves this by allowing both runtimes to coexist.
What changes in Summer 2026
Bizagi runs the Connector Service using three internal components:
1.A routing service that receives all connector requests.
2.A legacy runtime that uses Node version 12.
3.A modern runtime that uses Node version 22.
The routing service automatically sends each connector request to the correct runtime based on its configuration. This process is invisible to end users and does not change how connectors are invoked.
What does not change
The following remains exactly the same:
•Existing connectors keep working without modification.
•No changes are required in deployed environments.
•Connector calls from processes and the Work Portal are not affected.
•Performance and response times remain the same.
If you upgrade to Summer 2026 and do nothing else, your system continues to work exactly as it did before.
How connector runtimes are selected
Each connector runs on a specific Node runtime. This is handled automatically or through configuration, depending on the scenario.
Existing connectors
All connectors created before Summer 2026 are considered legacy connectors. They run on Node version 12 by default, and you do not need to take any action.
New connectors
Any connector created from Summer 2026 onward automatically uses Node version 22. You do not need to select a version manually, as Bizagi detects that the connector is new and assigns the modern runtime automatically.
Migrating an existing connector to Node version 22
If you want to run an existing connector on Node version 22, you can do so manually.
To do this:
1.Open the connector in Bizagi Studio.
2.Go to System Configuration.
3.Locate the NODE_VERSION setting.
4.Choose Latest.
5.Save and deploy the connector.
After this change, the connector runs on Node version 22.
Rolling back to Node version 12
If you test a connector on Node version 22 and encounter issues, you can easily revert.
1.Open the connector in Bizagi Studio.
2.Go to System Configuration.
3.Change NODE_VERSION back to 12.
4.Save and deploy again.
This rollback is immediate and safe.
When should you move to Node version 22
You should consider moving a connector to the modern runtime if:
•You are building a new connector.
•Your connector uses newer npm libraries.
•You want improved security and long term support.
•You plan future enhancements that require modern JavaScript features.
You may keep a connector on Node version 12 if:
•It is stable and working correctly.
•It does not require new functionality.
•You are not ready to test changes yet.
The migration is optional and fully under your control.
What happens in the long term
Bizagi will gradually phase out Node version 12 over multiple releases.
The plan is:
1.Summer 2026 introduces dual runtime support.
2.Future releases promote migration through documentation and guidance.
3.Node version 12 will be deprecated only after sufficient time and communication.
4.Eventually, only a modern long term support version will remain.
There is no forced migration in Summer 2026.
Visibility and monitoring
Each connector execution is clearly identified according to the Node runtime used.
Bizagi applies the following labels:
•[LEGACY_V12] when the connector runs on Node version 12
•[MODERN_RUNTIME] when the connector runs on Node version 22
These labels appear in the Traces logs, making it easy to confirm which runtime processed each request and to troubleshoot or validate migration scenarios when needed.
Frequently asked questions
1.Will my connectors stop working after upgrading to Summer 2026?
No. All existing connectors continue running on Node version 12 by default.
2.Do I need to update all my connectors immediately?
No. Migration is optional and can be done gradually.
3.Can different connectors use different runtimes?
Yes. Each connector has its own configuration and can run independently.
4.Do new connectors require extra configuration?
No. New connectors automatically use Node version 22.
5.Is there any performance impact?
No noticeable impact. The routing layer adds negligible overhead and connector performance remains the same.
Last Updated 7/21/2026 12:10:50 AM