Resources · Make integration

Zep Make integrationAutomate Zep with Make.

Need your chatbot to remember what each user already said? The Zep Make integration gives you 5 modules: 4 actions and 1 search. This page shows how to link your Zep account, then walks you through a first scenario that saves conversation memory into a session.

Try the Zep integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Zep Make integration do for you?

The Zep Make integration lets a Make scenario, the automation you build as a chain of bricks called modules, write to and read from Zep without code. You can create users, open sessions for them, add memories to a session and pull that memory back when a conversation needs context.

A support assistant that keeps context. When a customer writes through your help desk app, Add a Memory to a Session stores the exchange, and Get Memory from a Session hands it back before the next reply is drafted. Each item that travels between modules is called a bundle, here one message.

Clean onboarding for new accounts. A signup in your CRM can run Add a User, then Add a Session with that User ID, so every new customer starts with a place for their history. If your contacts live in a table, the Airtable Make integration can feed those records in.

Anything the list does not cover. Make an API Call reaches any endpoint of the Zep API with the same connection, which is the way to go past the four ready-made actions.

Be clear on the limits: Zep has no trigger in Make, so a scenario starts from another app or from a schedule. Zep also has a node in n8n; the Zep n8n integration page and the n8n vs Make comparison help you weigh the two tools.

Connect

How do you connect your Zep account to Make?

  1. 01

    Open the connection window

    Add any Zep module to your scenario and click Create a connection. A connection is your Zep account linked to Make once, then reused by every Zep module you add later.

  2. 02

    Name it and authorize Make

    Give the connection a name if you run several Zep projects, so you can tell them apart. Then follow what the window asks: either approve Make on the Zep page that opens, or paste the key Zep gives you.

  3. 03

    Save and check

    Click Save. The module now shows your connection in its dropdown, and you can fill its fields. If the save fails, the key or the authorization is the first thing to look at again.

First scenario

Build your first scenario with Zep

GoalWhen a new message comes in through another app, Make stores it as memory in the matching Zep session.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to place the first module. This first spot goes to the app where your messages arrive, not to Zep.

  2. 02

    Pick the starting app

    Search for the app that receives the conversation, choose its module and link your account with Create a connection. Its output, one bundle per message, is what Zep will store.

  3. 03

    Add the Zep action

    Click the + on the right of that module, search for Zep and choose Add a Memory to a Session. Give it the session ID, then map the message coming from the previous module.

  4. 04

    Test with Run once

    Click Run once, send a test message in the starting app, then open the bubbles to read the bundles each module received. Confirm in Zep that the memory landed in the right session.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and turn the scenario on. From now on, every run counts operations, one per module and per bundle, on your Make plan.

Modules

What the Zep modules do in Make

Zep gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Zep1

Add a Memory to a Session

Action

In Make“Adds a new memory to a session.”

Saves a new piece of memory inside an existing Zep session, so the conversation history grows with each message your scenario passes along.

When to use it
right after a chat, ticket or form reply arrives in another app and you want Zep to keep that exchange for later answers.
Watch out
the session has to exist first; run Add a Session earlier in the flow when you are not sure it does.
Zep2

Add a Session

Action

In Make“Creates a new Session with the specified User ID.”

Opens a fresh session in Zep for a given User ID, giving that person a container where every future memory of the conversation will sit.

When to use it
at the start of a new conversation or a new support case, before any memory is written.
Watch out
it needs the User ID of someone who already exists in Zep, so place Add a User before it for brand new contacts.
Zep3

Add a User

Action

In Make“Adds a User.”

Registers a person in Zep so sessions and memories can be attached to them, which keeps each customer's history separate from everyone else's.

When to use it
when a signup, a new CRM contact or a first chat shows up and that person is not yet known to Zep.
Watch out
it runs on every bundle it receives, so filter out people you already added to avoid duplicates.
Zep4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Zep API with the connection you already set up, which opens up everything the four ready-made modules leave out.

When to use it
when you need a Zep operation that has no dedicated module, for example a call you found in the Zep API reference.
Watch out
you write the request yourself, so keep the Zep API reference open and test the call with Run once before switching the scenario on.
Zep5

Get Memory from a Session

Search

In Make“Retrieves the memory from a specified session ID.”

Reads back the memory stored in a session you point to by its ID, so the next module can answer with the full context of the conversation.

When to use it
just before an AI module or a reply step drafts a response to a returning customer.
Watch out
as a search, it can return zero, one or several bundles; plan what the next module should do when nothing comes back.
Need help

Need help automating Zep with Make?

A person reads every message.

FAQ

Zep and Make: frequent questions

01Is the Zep Make integration free?
Yes. Zep is a standard app, so its modules work on the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations each month.
02What do you need to connect Zep to Make?
A Zep account and a Make account. Make does not publish a dedicated documentation page for Zep, so no specific prerequisite is listed. The connection follows the generic Make steps: add a Zep module, click Create a connection, optionally name it, authorize Make on the Zep page or paste the key Zep gives you, then click Save. Every Zep module in your scenarios then reuses that same connection. The Zep app itself is available from the Free plan, so you can test the connection before paying anything.
03Does the Zep Make integration have a real-time trigger?
No. Zep has no trigger module in Make, neither scheduled nor instant. A scenario therefore starts elsewhere: from an instant trigger of another app, which that app calls through a webhook as soon as something happens, or from the schedule set on the first module, every 15 minutes by default. Zep modules then come in as the second or third step of the flow. In practice, pick the app where the conversation actually happens and let it hand each message to Add a Memory to a Session.
04What if the Zep module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Zep API with the connection you already created, so an operation without its own module stays within reach. You write the request yourself, which calls for the Zep API reference. Make does not publish documented limits for this app, so test each call with Run once before activating the scenario, and read what Zep sends back. Run once shows the bundle each module received, so you can read Zep's answer to your request right in the editor.
05Should you use Make or n8n for Zep?
It depends on the tool your team already works in. Zep is available in both: in Make through 5 modules, 4 actions and 1 search, and in n8n through its own node. If your other scenarios already run in Make, keeping Zep there avoids a second tool to maintain. If your stack sits in n8n, the node there is the natural choice. Compare what each one offers for your exact use case before deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations