CONNECT APP
Build with Zep
Artificial Intelligence (AI)
- API key
MCP
Give your agent Zep tools
Every Zep action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Zep account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "zep",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Add Memory to Session:
const result = await mcp.callTool({
name: "zep-add-memory",
arguments: {
sessionId: "Session ID",
messages: ["Messages"],
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "zep",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Add Memory to Session:
result = await session.call_tool("zep-add-memory", {
"sessionId": "Session ID",
"messages": ["Messages"],
})API PROXY
Call the Zep API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Zep API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.getzep.com/api/v2/users-ordered",
})
// Any allowed Zep endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.getzep.com/api/v2/users-ordered
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZ2V0emVwLmNvbS9hcGkvdjIvdXNlcnMtb3JkZXJlZA?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Zep actions from your backend
Connect a user's Zep account once, then run Add Memory to Session on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "zep-add-memory",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
zep: { authProvisionId: "apn_xxxxxxx" },
sessionId: "Session ID",
messages: ["Messages"],
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="zep-add-memory",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"zep": {"authProvisionId": "apn_xxxxxxx"},
"sessionId": "Session ID",
"messages": ["Messages"],
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "zep-add-memory",
"configured_props": {
"zep": { "authProvisionId": "apn_xxxxxxx" },
"sessionId": "Session ID",
"messages": ["Messages"]
}
}'TOOLS
Zep actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Add Memory to Session
actionAdds memory to an existing session in Zep. See the documentationWritev0.0.4 -
Add User
actionAdds a user in Zep. See the documentationWritev0.0.3 -
Create Session
actionCreates a new session in Zep. See the documentationWritev0.0.3 -
Get Thread Messages
actionReturns messages for the thread with the specified ID. See the documentationRead-onlyv0.0.2 -
Get Threads
actionReturns a paginated list of threads. See the documentationRead-onlyv0.0.2 -
List Session ID Options
actionRetrieves available options for the Session ID field.Read-onlyv0.0.1 -
List Thread ID Options
actionRetrieves available options for the Thread ID field.Read-onlyv0.0.1 -
List User ID Options
actionRetrieves available options for the User ID field.Read-onlyv0.0.1 -
Update Session
actionUpdates an existing session in Zep. See the documentationWritev0.0.3
-
New Message in Session
triggerEmit new event when a message is added to a session. See the documentationv0.0.3 -
New Session Created
triggerEmit new event when a new session is created in Zep. See the documentationv0.0.3 -
New Session Updated
triggerEmit new event when an existing session is updated. See the documentationv0.0.3
MULTI-APP
Use Zep with other popular apps
Most products don't stop at one integration. Pair Zep with the other apps your users rely on, and ship use cases that span both.
- App slug
- zep
- Authentication
- API key
- Categories
- Artificial Intelligence (AI)
- Actions
- 9
- Triggers
- 3
- API proxy
- Available