Questions on Flowise features and documentation #2423
Replies: 2 comments
-
Regarding the documentation, it's significantly behind production, with nearly a hundred nodes missing. I contacted the team last week, suggesting a temporary solution of including these nodes in the docs for basic awareness of their availability. I have documented (name, image and description) all the currect nodes here: https://toi500.gitbook.io/flowise-docs/integrations (I'm still waiting for a response to my pull request). Right now, the only way to get technical details of the new nodes is by searching on https://js.langchain.com/v0.2/docs/introduction/ |
Beta Was this translation helpful? Give feedback.
-
To a certain extend that can be covered with this https://github.com/crashr/open-adapter |
Beta Was this translation helpful? Give feedback.
-
Hi,
I have some questions regarding features of Flowise. I checked the documentation but couldn't find entries for some of the nodes and configuration options.
When creating a chatflow I find it difficult to find the right nodes and how to configure them. For example
On the landing page there's the "Document Stores" item. I couldn't find that in the documentation. From clicking around it looks like I can configure a "one-shot" data ingestion.
Do Buffer Memory nodes work only inside that specific workflow or can I use them across workflows, e.g. by specifying the same session id?
In general some kind of overview like a table with filter function would be helpful where one can look up which nodes can be connected as input/output to which other nodes.
And a more general question... is Flowise intended to be used behind a separate frontend only? To be more specific: one of my use cases is to create an OpenAI compatible API frontend in an air-gapped environment for access from IDE plugins.
Kind Regards
Christian
Beta Was this translation helpful? Give feedback.
All reactions