feat(flowise): add Flowise integration with Hindsight memory tools#1436
Open
benfrank241 wants to merge 4 commits into
Open
feat(flowise): add Flowise integration with Hindsight memory tools#1436benfrank241 wants to merge 4 commits into
benfrank241 wants to merge 4 commits into
Conversation
benfrank241
force-pushed
the
feat/flowise-integration
branch
from
b13d8ec to
fb26688
Compare
benfrank241
force-pushed
the
feat/flowise-integration
branch
from
5af4ae6 to
7b2232d
Compare
Adds three Flowise Tool nodes — Hindsight Retain, Hindsight Recall, Hindsight Reflect — that drop into any chatflow or agent flow alongside the standard LangChain tools. Each node returns a DynamicStructuredTool from init(), so it slots into Flowise's tool sockets and any LangChain agent. - One shared hindsightApi credential (apiUrl + optional apiKey) for all three nodes - Source files use upstream-relative imports (`../../../src/Interface` and `../src/Interface`) and copy 1:1 into Flowise's packages/components/ tree at submission time. A local src/Interface.ts shim mirrors the upstream API so the files compile and unit-test outside the Flowise monorepo. - 17 vitest unit tests covering INode metadata, credential shape, and init() returning a Tool that forwards to the Hindsight client with the expected arguments - test-flowise-integration CI job (Node 22, npm install + tsc + vitest), flowise added to release-integration.sh, docs page at /sdks/integrations/flowise, integrations.json listing, real Flowise logo Distribution model: Flowise has no community-node mechanism, so the user-facing ship event is an upstream PR to FlowiseAI/Flowise (same path Mem0 used). This commit prepares the source-of-truth copy and standard wiring; the upstream submission is a follow-up.
benfrank241
force-pushed
the
feat/flowise-integration
branch
from
7b2232d to
4ee6b45
Compare
Replaces the placeholder gradient-square hindsight.svg shipped in the HindsightRetain/Recall/Reflect node directories with the canonical Hindsight favicon (transparent PNG, square-padded to 186x186 so Flowise's icon slot renders it without distortion). Updates this.icon in the three node classes from "hindsight.svg" to "hindsight.png" and the matching test assertion in tests/nodes.test.ts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Three Flowise Tool nodes — Hindsight Retain, Hindsight Recall, Hindsight Reflect — that drop into any chatflow or agent flow. Each node returns a LangChain
DynamicStructuredToolfrominit(), so it slots into Flowise's tool sockets and any LangChain agent. One sharedhindsightApicredential for all three.Source files use the upstream-relative imports verbatim (
../../../src/Interface,../src/Interface) so they copy 1:1 intoFlowiseAI/Flowise/packages/components/for the submission PR. A localsrc/Interface.tsshim mirrors the upstream API so the files compile and unit-test outside the Flowise monorepo.Distribution
Flowise has no n8n-style community-node mechanism — every node lives inside
FlowiseAI/Flowise/packages/components/of the main repo. The user-facing ship event is an upstream PR (same path the existing Mem0 integration used). This PR is the source-of-truth copy in our monorepo plus the standard wiring; the upstream submission is a follow-up tracked separately.Test plan
npm install && npm test— 17/17 vitest tests passnpx tsc --noEmit— cleantest-flowise-integrationjob (Node 22, npm install + tsc + vitest)FlowiseAI/Flowise/packages/components/,pnpm build,pnpm start, build a chatflow with all three tools, verify retain/recall via the Hindsight APIFlowiseAI/Flowise(follow-up issue)BaseChatMemory(direct competition with Mem0's existing Memory node)Files
hindsight-integrations/flowise/— source-of-truth copy (3 tool nodes, 1 credential, vitest setup, README, CHANGELOG).github/workflows/test.yml— paths-filter, outputs,test-flowise-integrationjob, summary needsscripts/release-integration.sh—flowiseadded toVALID_INTEGRATIONShindsight-docs/docs-integrations/flowise.md— new docs pagehindsight-docs/src/data/integrations.json— listing entryhindsight-docs/static/img/icons/flowise.png— real Flowise logo🤖 Generated with Claude Code