Flow Builder Migration Guide

[#1]

Flow Builder Migration Guide

We are releasing a new version of Flow Builder, which introduces important updates.

Because of these changes, concretely, the new workflow designer and the new Lansweeper connector, previously created workflows are not compatible with the new setup.

If you’d like to learn more about all the improvements included in this release, you can find additional information here: https://community.lansweeper.com/t5/flow-builder-program/flow-builder-moves-to-preview-update-on-flo...

---

What’s Changing

• Workflows created in your current Flow Builder designer will appear with the “classic” label.

• “Classic” workflows will remain available for 2 weeks after the release to give you time to migrate.

• After 2 weeks, all classic workflows will be removed.

• Workflows with three or more steps will be automatically copied to the new version to help you transition more easily. However, you’ll still need to review and adjust them manually, as they won’t work immediately after migration.

---

Migration Steps

1. Review and clean up old workflows

• Delete any workflows that are obsolete, test-only, or no longer needed.

2. Identify auto‑migrated workflows

• For each “classic” workflow you want to keep:

  • Check if a new version already exists (without the “classic” label).

  • The automatically migrated workflows appear under the same name.

3. Update and validate each migrated workflow

For each workflow you plan to keep:

a. Upgrade connectors

• Open one step using the Lansweeper connector and upgrade to the latest version.

• We also recommend upgrading all other connectors to their latest versions.

b. Refresh external connections

• Re‑add or re‑authenticate any external application connections.

• Refresh client IDs and/or secrets to comply with the new security model.

c. Review the new data model

Some field paths and filters have changed in the new Lansweeper connector. Make sure your workflows follow the updated structure.

• Review all reference paths to the Lansweeper connector outputs.

• Adjust filters (for example, those in “List of Assets”).

• Documentation for the new data model will soon be available

Example:

• From: results.items.0.assetBasicInfo.name To: results.items.0.asset.general.name

Previous designer

New designer

d. Change the custom field "Key" in the Edit Asset action

If your workflow edits any custom fields, please note that we’ve changed how these fields are handled to improve the performance of the Edit Asset action.

• You now need to specify the custom field “key” instead of the custom field “name” in the Key field.
• To help with this, you can retrieve the list of custom field keys and names using the “List custom fields” action.

e. Fix any other steps marked in red

• Red icons indicate missing or invalid parameters.

f. Adjust regex filters in Lansweeper actions

• Filters no longer require double escaping of special characters.

Example:

• Old regex: ^[0-9]{1,3}\\\\.[0-9]{1,3}

• New regex: ^[0-9]{1,3}\\.[0-9]{1,3}

g. (Recommended) Remove deprecated Flow Builder API client

• Go to Site Configuration → API Client Management.

• Remove the Flow Builder API client, which is no longer required.

---

After Migration

After reviewing and adjusting your workflows, test each one to confirm correct behavior.

---

Need Help?

If you encounter issues during migration:

• Open a thread with your questions in our Flow builder community: https://community.lansweeper.com/t5/flow-builder-program/gh-p/FlowBuilderBetaProgram

• Or contact us through the email flowbuilderbeta@lansweeper.com.