Flowise

Add a GoodMem Tool node to Flowise's visual builder so agents and flows can store, retrieve, and manage memories.

Stub· JavaScript/TypeScript

n/a (built into the fork)PAIR-Systems-Inc/igoodmem_flowise

This integration lives in a fork of Flowise and is still being finalized. The fork's top-level README is the upstream Flowise README and contains no GoodMem-specific instructions, so the details below are drawn directly from the integration source. Check the fork for the current status: PAIR-Systems-Inc/igoodmem_flowise.

Overview

Flowise is an open-source visual builder for LLM apps and agents. This fork adds a GoodMem Tool node to Flowise's node palette so that agents and flows can use GoodMem — a memory layer that handles semantic storage, vector retrieval, and LLM-powered summarization — without writing code. The node is registered under the Tools category and, when connected to an agent, exposes a set of goodmem_* tools the agent can call to manage spaces and memories.

The GoodMem addition is a single feature commit (feat(tools): add GoodMem integration) on top of upstream Flowise, consisting of a GoodMem Tool node and a GoodMem API credential.

Installation

There is no published package for this integration yet. It ships inside the fork, so you run Flowise from source:

git clone https://github.com/PAIR-Systems-Inc/igoodmem_flowise.git
cd igoodmem_flowise
pnpm install
pnpm build
pnpm start

The GoodMem node and credential are bundled in the flowise-components package (packages/components/nodes/tools/GoodMem and packages/components/credentials/GoodMemApi.credential.ts). Once Flowise is running, the GoodMem node appears in the Tools section of the node palette.

Configuration

Configuration is done through a GoodMem API credential in the Flowise UI (Credentials → add new → GoodMem API), not through environment variables. The credential exposes these fields:

Field	Credential key	Description
Base URL	`goodMemBaseUrl`	Base URL of your GoodMem API server, e.g. `https://your-goodmem-server.example.com`.
API Key	`goodMemApiKey`	API key issued by GoodMem. Sent as the `X-API-Key` header.
Verify SSL	`goodMemVerifySsl`	Verify the server's TLS certificate (default `true`). Disable only for self-signed local installs.

Quick start

Start the fork (see Installation) and open the Flowise UI.
Create a GoodMem API credential with your Base URL and API key.
Drag the GoodMem node from the Tools palette onto a flow and connect the credential.
(Optional) Pick which operations to expose via the Actions field — leave it on All Operations to expose every supported operation. You can also set a Default Embedder and Default Space, which are loaded live from your server.
Connect the GoodMem node to an agent node. The agent can now call the GoodMem tools.

Operations

When attached to an agent, the node exposes the following tools (each operation can be toggled on or off individually via the node's Actions field):

Tool	Operation
`goodmem_list_embedders`	List available embedder models
`goodmem_list_spaces`	List all spaces accessible to the API key
`goodmem_get_space`	Fetch a space by ID
`goodmem_create_space`	Create a new space (reuses an existing space with the same name)
`goodmem_update_space`	Update mutable fields on a space (name, `publicRead`, labels)
`goodmem_delete_space`	Permanently delete a space and all its memories
`goodmem_create_memory`	Store text or a file as a new memory in a space
`goodmem_list_memories`	List memories in a space with optional pagination and filters
`goodmem_get_memory`	Fetch a memory by ID, optionally including its original content
`goodmem_retrieve_memories`	Semantic similarity search across one or more spaces
`goodmem_delete_memory`	Permanently delete a memory and its chunks/embeddings

The Default Embedder is used when goodmem_create_space is called without an embedder_id, and the Default Space is used when goodmem_create_memory, goodmem_list_memories, goodmem_get_space, or goodmem_retrieve_memories are called without an explicit space_id. Update and delete operations always require an explicit ID.

Documentation for this integration is being finalized. For the current node behavior, supported operations, and setup, refer to the source on GitHub: PAIR-Systems-Inc/igoodmem_flowise.