Flowise

Is the original Flowise project still maintained?

Flowise announced a July 29, 2026 code freeze and an August 31 end of life for the upstream project.

The code remains available. The repository license applies Apache 2.0 to covered community code and has separate rules for identified enterprise and third-party material. A fork has its own maintenance and release history. Current access and pricing for the hosted service remain unverified.

How can you understand an existing Flowise workflow?

Read the boxes as a sequence of decisions. A model box can propose text or a label. A tool box can perform a specific action, and a Human Input box can pause the flow for a person.

The archived docs describe checkpoints that can hold a paused flow. Check whether an outside destination already changed before repeating any action.

1. 1
   Trace one made-up example

   On paper, write the note “Would like a demo.” Mark where the old flow took the note and where a model would return a suggested label.
2. 2
   Find the point where it can change something

   Mark any place the flow would save a record, call another service or wait for a person. Write down the inputs the action expects.
3. 3
   Plan the same check for a replacement

   Use the invented note with external actions disconnected. Have a person accept or decline the proposed label before anything could write.

What can you recover from an old Flowise setup?

Start with the workflow definition if you can still access it. The historical Cloud migration exported selected items as JSON and left credentials out. Check your own account or deployment before counting on that export.