Lowering the barrier of collaboration is indeed a major goal for us. In the DRAKON analogy, Flowcode might help technical product managers collaborate with developers on LLM-heavy logic.
Re: vibe-coding - that matches our vision 100%. Let AI build the nodes while a human (even if heavily AI-assisted) oversees
>Given a folder of scanned files, create a .bat file with move commands which renames each file using the information from the scan of the form and superimposed check using the naming convention: $<amount of check>_<date of check in YYYY-MM-DD format>_<Invoice ID>_<PWS ID>_<name of company from population line>.pdf
https://app.getflowcode.io/api/run/7344545b-116c-44f1-83e0-2...
and when I run it, I get:
>{"message":"No matching HTTP trigger found"}
but I was expecting to be prompted for a folder.
The AI should have explained that local scripting isn't supported by Flowcode. Our copilot is under active development and has a lot of room for improvement.
Flowcode is built for cloud-based use cases - you can think of it as a "visual serverless" platform
Perhaps working directly with Flyde https://github.com/flydelabs/flyde + some AI assistant to build the custom nodes you'll need might work for that use case.
My problem has been to find a front-end which will actually work with local files....
It reminds me of Node-RED which seems very similar but is aimed at IIoT applications.
I’m working on a version that is based on Erlang and not NodeJS which isn’t a true concurrent language.
For me, flow based programming makes the most sense with languages which are truly concurrent and message passing is baked in, ie Erlang.
One thing I’ve come to realise is that visual programming is a hard sell, hence my effort to create a visual environment for Erlang - to introduce visual programming to a different set of developers.
I feel that something like BPMN should be the starting point becomes at it from the business person or business analyst's point of view and then us more developer types can fill in the missing pieces, rather than starting from the developer POV and trying to foist that on the less technical stakeholders.