---
title: "Discussion on \"n8n Zep memory: fixing 'The resource you are requesting could not be found' (and replacing the deprecated node)\" | Hashnode"
description: "Discussion on \"n8n Zep memory: fixing 'The resource you are requesting could not be found' (and replacing the deprecated node)\". The Zep credential test calls an endpoint Zep retired, so it fails even with a good key. Saving anyway can look like it works while history quietly stays empty. Here's what's happening and how to move the agent to a maintained memory node."
url: "https://hashnode.com/posts/n8n-zep-memory-resource-you-are-requesting-could-not-be-found/6af887322c1b2855faeedf8b"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [n8n Zep memory: fixing 'The resource you are requesting could not be found' (and replacing the deprecated node)](https://memorysync.hashnode.dev/n8n-zep-memory-resource-you-are-requesting-could-not-be-found?utm_source=hashnode&utm_medium=feed)

The Zep credential test calls an endpoint Zep retired, so it fails even with a good key. Saving anyway can look like it works while history quietly stays empty. Here's what's happening and how to move the agent to a maintained memory node.

2h ago · 13 min read · memorysync.hashnode.dev  
Read the article

-   [#n8n](https://hashnode.com/tag/n8n)
-   [#ai](https://hashnode.com/tag/ai)
-   [#automation](https://hashnode.com/tag/automation)
-   [#agents](https://hashnode.com/tag/agents)
-   [#debugging](https://hashnode.com/tag/debugging)

## Written by

[MemorySync](https://hashnode.com/@memorysync)

@memorysync · San Francisco, USA

  
[View profile](https://hashnode.com/@memorysync)

Building MemorySync (memorysync.io) — persistent memory infrastructure for AI agents, Cursor, and Claude Code.

Building MemorySync (memorysync.io) — persistent memory infrastructure for AI agents, Cursor, and Claude Code.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
