Just found Zep and it looks neat but it seems that the built in node to n8n doesnt work with the newer Zep CE version(from September onwards). n8n looks like it might support the previous OSS version of Zep.
the Zep logs show a 404 error when n8n trys to do the credential test.
Is n8n still going to support Zep CE?
I’ll try the cloud version in the mean time.
thanks,
It looks like your topic is missing some important information. Could you provide the following if applicable.
Hey @rjodwyer,
We do have a dev ticket open for this, I think we were waiting for the Zep dev team to update LangChain to add support for it. At the moment you are correct though we don’t support CE only the older version and Zep Cloud.
Hello @Jon ,
I see that your integration is using the endpoint /api/v1/collection which returns 404 on the community edition of zep. Just switch to /api/v2/collection 
It looks like the latest versions of langchain support much newer versions of Zep now:
@getzep/zep-cloud: ^1.0.6@getzep/zep-js: ^0.9.0How can I tell if this is on the roadmap.
I’d really like to use a more advanced memory system, Zep looks to be one of the best. @Mariusz_Kreft how can I change that URL?
I’m having real issues with the Zep node here, using the cloud version of the memory. It significantly under-performs Windows Buffer, which is not exactly what I’d envisioned. In a chat application, using Tools Agent and a Pinecone VDB I can get Windows Buffer to hang tight to the system instructions for 15 or so interactions before it flakes out. Zep, about half of that.
Really frustrating, as Zep’s cloud version looks superb in all the ways. But unusable if there’s an issue with the n8n node, which Zep just told me they don’t support. Ack.
I also find it frustrating to Use Zep memory. Right now I want to switch to Zep CE, and no can do 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.