Migrating from V1 flows to V2 flows
With the latest release, sources are an entity independent from flows. Until now the source configuration was defined inside the flow. It is now created in the Sources catalog and can be reused by several flows: fewer duplicates and simpler maintenance.
Existing flows keep working without changes. They are identified as V1 flows, they are deprecated, and they are replaced by V2 flows. Retirement happens in three phases.
What changes
| V1 flow | V2 flow | |
|---|---|---|
| Source | Embedded in the flow | Catalog source, linked from the trigger |
| Reuse | The configuration applies only to that flow | The same source can be used by several flows |
| Triggers | Webhook and scheduling configured on the flow | At most one scheduled trigger and one webhook trigger |
Creating a V2 flow requires a source and a destination. They can be created beforehand, or during flow configuration with the + button in the selection menus. The steps are in the Create a flow tutorial.
Timeline
Phase 1 — V1 and V2 coexistence
From today until the beginning of February 2027.
- V1 flows continue to run normally.
- Existing V1 flows can still be edited.
- New V1 flows can no longer be created from the UI.
- All new flows are created as V2 flows.
Phase 2 — Conversion required to make changes
From the beginning of February 2027 until the beginning of May 2027.
- V1 flows continue to run.
- A V1 flow can no longer be edited directly.
- Any change requires converting the flow to V2.
In the scheduled source configuration, a conversion button:
- retrieves the current source configuration;
- pre-fills the form of the new catalog source;
- associates it with the V2 flow.
After the new source is generated, it must be saved. Without saving, the conversion does not take effect.
Phase 3 — End of V1 flow support
From the beginning of May 2027.
- V1 flows are no longer supported.
- Features tied to V1 flows are removed from the platform.
- All flows must be migrated to V2.
Plan the migration before the retirement date, to avoid interruptions.
Converting a V1 flow
- Open the V1 flow and go to the scheduled source configuration.
- Use the conversion button: the new source form opens already filled with the current configuration.
- Check type, credentials and parameters, then save the source.
- Confirm that the flow is V2 and that the scheduled trigger points to the source just saved.
- Run a test Run and check the outcome in the flow monitoring.
If the flow also has a webhook, the webhook trigger stays on the flow together with the scheduled trigger. A V2 flow allows one of each type.