Hello everyone,
I’m having an issue while trying to use Zep Memory in n8n. I’m connecting to Zep Cloud via https://app.getzep.com/.
In the n8n Zep tool, I’ve entered my API key and API URL, but when I use the API URL, I get the error:
Couldn’t connect with these settings
Could someone please guide me on how to resolve this issue? Even after Turning Cloud on when the API not there only api token was there the issue remain same
Hey @ianujrajpurohit hope all is good. Welcome to the community.
When you click on More Details, are there any … more details?
In zep tool there is no ‘More Details’ option but if you are talking about side detail menu then there is nothing but basic details like created and last modified nothing else
Message that i got :- The resource you are requesting could not be found
We’re also seeing the “Couldn’t connect with these settings — The resource you are requesting could not be found” error when adding Zep credentials in n8n. This appears to be a known issue and may be tied to ongoing changes/bug fixes around the credential flow.
In the meantime, you can still use Zep by calling the same endpoints via the HTTP Request node. This avoids the credential validation step and lets you directly target the correct API version and paths.
Method: GET/POST (as required by the endpoint)
URL: Your Zep endpoint (ensure you use the correct base URL and version, for example: /api/v3 or /v3)
Headers:
Authorization: Bearer YOUR_ZEP_API_KEY
Content-Type: application/json
Query/body: As per the endpoint requirements
You can find the request/response schema and parameters in Zep’s docs and Swagger:
Zep v3 SDK/Swagger reference (Threads – list all):
Note: This approach may require manual configuration and a bit of familiarity with the Swagger details in the link above.
Method: GET
URL: YOUR_ZEP_BASE_URL/api/v3/threads
Headers:
Authorization: Bearer YOUR_ZEP_API_KEY
Accept: application/json
If your Zep instance uses a different base/route (Cloud vs self-hosted), adjust the base URL and version accordingly.
The built-in credential checker can fail while the underlying API remains accessible.
Using HTTP Request lets you precisely match the current Zep API version and endpoints, bypassing the credential test.
I am having the same problem using version 1.106.3
If Zep integration is not working, please file a bug here. In the meantime, use HTTP Request node to send requests manually.
I’d encourage to include this to the ticket. If the integration is no longer supported, probably it needs to go.
Surely n8n support as far as Zep is concerned is to provide a stable SDK / production endpoint. n8n integration is calling the same APIs, just wrapping an easy to use node around it. Not so?
I’ve just fallen victim to this too, after trying to replicate something I saw online - surely this just needs an n8n team member to update the module? After all, it’s probably just a HTTP request in the backend?
