Flowise

​

Overview

1. 🧠 Provides persistent memory storage for Flowise chatflows
2. 🔄 Seamless integration with existing Flowise templates
3. 🚀 Compatible with various LLM nodes in Flowise
4. 📝 Supports custom memory configurations
5. ⚡ Easy to set up and manage

​

Prerequisites

1. Flowise installed (NodeJS >= 18.15.0 required):

npm install -g flowise
npx flowise start

2. Access to the Flowise UI at http://localhost:3000
3. Basic familiarity with Flowise’s LLM orchestration concepts

​

Setup and Configuration

​

1. Set Up Flowise

1. Open the Flowise application and create a new canvas, or select a template from the Flowise marketplace.
2. In this example, we use the Conversation Chain template.
3. Replace the default Buffer Memory with Zentry Memory.

​

2. Obtain Your Zentry API Key

1. Navigate to the Zentry API Key dashboard.
2. Generate or copy your existing Zentry API Key.

​

3. Configure Zentry Credentials

1. Enter the Zentry API Key in the Zentry Credentials section.
2. Configure additional settings as needed:

{
  "apiKey": "m0-xxx",
  "userId": "user-123",  // Optional: Specify user ID
  "projectId": "proj-xxx",  // Optional: Specify project ID
  "orgId": "org-xxx"  // Optional: Specify organization ID
}

​

Memory Features

​

1. Basic Memory Storage

1. Save your Flowise configuration
2. Run a test chat and store some information
3. Verify the stored memories in the Zentry Dashboard

​

2. Memory Retention

1. Clear the chat history in Flowise
2. Ask a question about previously stored information
3. Confirm that the AI remembers the context

​

Advanced Configuration

​

Memory Settings

1. Search Only Mode: Enable memory retrieval without creating new memories
2. Zentry Entities: Configure identifiers:
   • user_id: Unique identifier for each user
   • run_id: Specific conversation session ID
   • app_id: Application identifier
   • agent_id: AI agent identifier
3. Project ID: Assign memories to specific projects
4. Organization ID: Organize memories by organization

​

Platform Configuration

1. Custom Instructions: Define memory extraction rules
2. Expiration Date: Set automatic memory cleanup periods

​

Best Practices

1. User Identification: Use consistent user_id values for reliable memory retrieval
2. Memory Organization: Utilize projects and organizations for better memory management
3. Regular Maintenance: Monitor and clean up unused memories periodically

​

Help & Resources

• Flowise Documentation
• Flowise GitHub Repository
• Flowise Website
• Zentry Platform
• Need assistance? Reach out through: