Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Mem0 memory support #13691

Closed
wants to merge 2 commits into from
Closed

Mem0 memory support #13691

wants to merge 2 commits into from

Conversation

Mikefluff
Copy link

Summary

This PR adds Mem0 Memory integration to n8n's LangChain nodes.

Mem0 is a memory service for AI applications that allows storing and retrieving messages based on semantic search. This integration enables users to:

  • Store conversation history between user and assistant in Mem0
  • Retrieve relevant past conversations using semantic search
  • Support contextual memory for AI workflows in n8n

The implementation follows a similar pattern to the existing Zep memory module, adapting for Mem0's specific API requirements and authentication methods.

Testing Instructions

  1. Add Mem0 API credentials (requires API key from mem0.ai)
  2. Add Mem0 Memory node to a workflow
  3. Configure with session ID and user ID
  4. Connect to an AI Agent node and test conversation memory persistence

Related Linear tickets, Github issues, and Community forum posts

Review / Merge checklist

  • PR title and summary are descriptive
  • Docs updated or follow-up ticket created
  • Tests included
  • PR Labeled with release/backport (if needed)

@CLAassistant
Copy link

CLAassistant commented Mar 4, 2025 •
edited
Loading

CLA assistant check
All committers have signed the CLA.

@n8n-assistant n8n-assistant bot added the community Authored by a community member label Mar 4, 2025
@Joffcom
Copy link
Member

Joffcom commented Mar 4, 2025

Hey @Mikefluff,

Thanks for the PR, We have created "GHC-1053" as the internal reference to get this reviewed.

One of us will be in touch if there are any changes needed, in most cases this is normally within a couple of weeks but it depends on the current workload of the team.

@n8n-assistant n8n-assistant bot added the in linear Issue or PR has been created in Linear for internal review label Mar 4, 2025
@Joffcom
Copy link
Member

Joffcom commented Mar 5, 2025

Hey @Mikefluff

Thanks for the contribution, We have now created a Community Node Repository which is our preferred method for new node submissions.

Once a node has been published to the Community Node Repository users will be able to install the node from their n8n interface and will be able to use your node quicker, You will also be able to update the node as needed without needing to wait for the review process.

In the future we may reach out to you about including your node in our main release, But for now I am going to close this PR.

You can find more information in the links below, If you have any questions about this or need any help let us know.

Building Community Nodes: https://docs.n8n.io/integrations/community-nodes/build-community-nodes/
Submitting Community Nodes: https://docs.n8n.io/integrations/creating-nodes/deploy/submit-community-nodes/
Published Nodes: https://www.npmjs.com/search?q=keywords:n8n-community-node-package

@Joffcom Joffcom closed this Mar 5, 2025
@Mikefluff
Copy link
Author

Mikefluff commented Mar 5, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
community Authored by a community member in linear Issue or PR has been created in Linear for internal review
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@Mikefluff @CLAassistant @Joffcom