Help Needed: Correct URL for Zep Cloud in n8n

Questions
1

Hi everyone,

I’ve been trying to configure Zep Cloud in n8n, but I’m running into issues with the API URL. According to this FAQ link, the API URL for Zep Cloud is https://api.getzep.com.

So, I used the URL https://api.getzep.com, but I got the error message “Couldn’t connect with these settings. Not Found.” I also tried the API documentation URLs https://api.getzep.com/api/ and https://api.getzep.com/api/v2, but this resulted in the error “Couldn’t connect with these settings. Unauthorized.”

It’s worth mentioning that I generated the Project Keys from the Zep console and used this key in the connection configuration on n8n. I even tried regenerating it three times to ensure that there was no error in the process.

So, to summarize:

  • The Project Key is correctly generated (I assume this is the API key as I couldn’t find separate information for an API key).
  • I used the URL provided in the official FAQ.

I’m not sure what I’m missing. Any help or suggestions would be greatly appreciated. Thank you!

Error message

“Couldn’t connect with these settings. Not Found.” or “Couldn’t connect with these settings. Unauthorized.”

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3
  • n8n version: 1.44.1
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own
  • Running n8n via (Docker, npm, n8n cloud, desktop app): cloud
  • Operating system: Linux
4

hello @swenro

Proper URLs are described there

1 Like
5

Thanks, can I have a screenshot of your configuration? Here’s mine that doesn’t work despite the fact that the API key is valid.

image
image886×517 17.7 KB

6

I don’t have Zep, so I can’t test it.

Try without the slash in the end
https://api.getzep.com/api/v2

But maybe the n8n credential is intended for the Zep Client, not Zep Cloud. Because I see that it tries to test the connection against the uri/api/v1/collection that is not valid for the cloud Zep

7

It doesn’t work with or without the slash, it makes no difference.

8

There is currently the following PR open to add support for Zep Cloud:

1 Like
9

I am having this same issue. Updated my N8N instance to 1.52.2

1 Like
10

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.