Iteration: enable Expert to populate pre-built flows in Node-RED editor

[gstout52]

Epic

No response

Description

As a FlowFuse Expert user

I want to have the Expert provide built flows to import

So that I can go from natural language input to nodes on the canvas with minimal effort

This iteration is to allow the Expert to surface pre-built flows that match the user's use case and put them in the Node-RED editor.

The sources for these flows are:

• Expert recommends Blueprint, asks user if they'd like to deploy
• Recommends example flows that already exist in core NR
• Node-RED cookbook
• (least reliable) flows.nodered.org

Which customers would this be available to

None

Acceptance Criteria

• [ ] criteria 1
• [ ] criteria 2
• [ ] criteria 3
• ...

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

[gstout52]

Per conversation on November 14: first step of this will be enabling the surfacing of a preview of a flow to be imported to the Node-RED editor along with a 'click to copy' button that can then be pasted into the Editor.

[Steve-Mcl]

As discussed in call:

• Core flows will be ingested ready for RAG in the agent
• I have stepped @cstns through the backend of where things happen
• Remaining tasks to get flows ready for "Copy Flow" button will require the "Query LLM" code to follow a similar pattern to moduleStore
  • I have already added utility functions to load/save store global utilityFunctions.loadFlowStore utilityFunctions.saveFlowStore
  • I will have completed work for ingestion of core node-red flows, the task will be to query the store and return an appropriately shaped data that the front-end can recognise and handle
  • These are only present in the new backend on prod

I will update this status as the day/weekend progresses.

[Steve-Mcl]

@cstns @knolleary

On prod there is now a dev and a prod instance & 2 pipelines have been setup (dev->prod, prod->dev)

• The website still needs moving over to (PR here)
• Once merged, the staging instance should be shut down

Additionally, I have complete RAG ingestion of NR flows (this is live as API v4 on -dev instance)

• It can be tested within the instance similar to the docs and modules can be.
• I have also raised a draft PR that consumes the messages on website here NOTE See the readme for TODOs