Resources · Zapier integration

MemorySync Zapier integrationAutomate MemorySync with Zapier.

MemorySync Zapier integration, read before you open the editor. Zapier offers 1 trigger, 3 actions and 3 searches: store facts about an end user, feed a conversation turn, delete memories, and pull back context for a later AI step.

Beta app Zapier still marks this integration as beta.

See the 7 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MemorySync Zapier integration does for you

The MemorySync Zapier integration links MemorySync, a memory service for AI tools, to the rest of your apps. It can store what an end user said, react when a new memory appears, or fetch a ready context block before another step writes something for that person.

Three typical results. First, a memory trail that follows a person across surfaces: New Memory starts a Zap each time MemorySync stores a fact, whether it came from your app, an agent, a voice call or another Zap, and the Zap passes it on to where your team reads. Second, transcripts that turn into facts: Add Conversation Turn sends each line a user says, and MemorySync keeps the durable details (preferences, plans) while small talk is dropped. Third, a prompt that already knows the person: Recall Context builds a grouped context block on a topic, ready for the AI step you place after it.

What Zapier does not do here. There is no instant trigger, so new memories are picked up at your plan's interval, never the moment they are stored. There is no find-or-create variant either, and nothing stored before the Zap was switched on gets replayed. Assistant turns are accepted but never become memories. To weigh other tools for the same job, see our n8n vs Zapier comparison.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event that starts the Zap. Here it is New Memory: once the Zap is on, Zapier waits for a fresh memory to show up.
Action
The step that does the work once the Zap has started, such as storing a fact or deleting memories in MemorySync.
Task
What Zapier bills: one action completed successfully. The monthly count on your plan is a count of those tasks.
Polling vs instant
Polling means Zapier checks the app on a timer; instant means the app calls Zapier itself. MemorySync's only trigger is polling.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already stored, such as an end user's memories, so the steps after it can use what it found.
Cost

What a MemorySync Zap really costs

The short version: the trigger is free, the actions are what you pay for.

  • Free plan100 tasks a month, unlimited Zaps, two steps each
  • Premium appNo, MemorySync runs on the free plan (beta)
  • Trigger costNone, only completed actions count

Checking MemorySync for new memories costs no task, however often Zapier looks. Every action that succeeds counts as one task, so a Zap with two actions uses two per run, and a failed action is not counted. MemorySync is not a premium app, so the free plan runs it, but only as two-step Zaps: one trigger, one action. Add a filter or a search such as Recall Context and the Zap becomes multi-step, which needs a paid plan. If you are still deciding on Zapier itself, see our Zapier review.

Connect

Connect MemorySync to Zapier in three steps

  1. 01

    Open Apps and start a connection

    In your Zapier account, open the Apps page and click + Add connection. A dialog opens with a search box: type MemorySync and pick it. Every MemorySync step will reuse this one connection later.

  2. 02

    Sign in on the MemorySync side

    Click Add connection. A new tab opens on MemorySync: sign in with the account that holds the end users your Zaps will read or write. Without an account on the app, there is nothing to link.

  3. 03

    Grant access to the account

    Grant Zapier access to the account when MemorySync asks. What you need up front: an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.

First Zap

Your first Zap: new memories into a spreadsheet

GoalFollow one end user and add a spreadsheet row for each new memory that passes your filter.

  1. 01

    Create the Zap and pick the trigger

    Create a new Zap, choose MemorySync as the app and New Memory as the event. Select your connection, then fill End User ID with the person whose memories you want to follow.

  2. 02

    Test the trigger on real data

    Run the test. Zapier brings back the three most recent memories of that end user, so the rest of the Zap is mapped on a real one rather than an empty shape.

  3. 03

    Add the filter

    Click the plus icon and add Filter. Set its three boxes: the field to look at, the rule, the value. Use a text rule on text. The filter makes this a multi-step Zap, so a paid plan.

  4. 04

    Add the spreadsheet action

    Add your spreadsheet tool as the action and map what the trigger returned into its columns. Run the step test and read what came back before going any further.

  5. 05

    Publish

    Click Publish to switch the Zap on. From then on Zapier checks for new memories at your plan's interval, and only memories stored after that point are picked up.

Triggers

The MemorySync trigger

1 event starts a Zap when something happens in MemorySync. Zapier checks for them at the interval your plan allows.

1

New Memory

Polling trigger

In Zapier“Triggers when a new memory is stored for an end user — from any surface: your app, an agent, a voice call, or another Zap. A conversation turn fires it once for each fact extracted from what the user said.”

Starts your Zap each time MemorySync stores a new memory for the end user you chose, whatever surface it came from: your app, an agent, a voice call or another Zap. One conversation turn can start it several times, once per fact pulled out of what the user said.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
you want each new fact about a person copied or announced somewhere your team already works.
Watch out
End User ID is required, so decide which end user this Zap watches before you run the test.
Actions

MemorySync actions

MemorySync gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Memory

Action

In Zapier“Stores a fact or note as a long-term memory for an end user (server-side extraction keeps only durable content).”

Saves a fact or a note as a long-term memory for one end user. MemorySync keeps only durable content on its side, so a passing remark may not survive the extraction.

When to use it
another app hands you a stable detail about a person, like a preference, and your AI tools should know it next time.
Watch out
End User ID and Text are both required; map the same identifier your other Zaps use.
2

Add Conversation Turn

Action

In Zapier“Sends one conversation turn to MemorySync. Durable facts from what the user said are extracted and stored as memories; assistant turns are accepted but not stored as memories. A retried Zap is recognised and not extracted twice.”

Sends one line of a conversation to MemorySync, marked as said by the User or by the Assistant. Durable facts in a User turn become memories, and a retried Zap is recognised, so the same turn is not extracted twice.

When to use it
a voice call or a chat produces transcripts and the person's preferences and plans should be kept without anyone typing them.
Watch out
Assistant turns are accepted but never stored, and small talk such as "ok" or "thanks" stores nothing.
3

Delete Memories

Action

In Zapier“Permanently deletes specific memories by ID for one end user.”

Erases chosen memories of one end user for good, picked by their IDs. There is no undo: what this step deletes is gone.

When to use it
a person asks to have something specific forgotten and an earlier step already holds the memory IDs.
Watch out
Memory IDs is a comma-separated list such as m_123, m_456; check at the test that the IDs you map are the right ones.
Searches

MemorySync searches

3 search steps look for data that already exists in MemorySync, so a later step can use it.

A search step reads without writing. MemorySync offers three, all of them tied to an End User ID. In the editor they sit at the bottom of the Action event list, under the SEARCH heading.

1

Find Memories

Search

In Zapier“Lists an end user’s stored memories, newest first.”

Lists the memories stored for one end user, newest first. It is the plain inventory of what MemorySync holds on that person.

When to use it
you want to review what is on file for someone before a later step acts on it.
Watch out
End User ID is the only required field, so the list covers that person and nobody else.
2

Recall Context

Search

In Zapier“Builds a grouped, prompt-ready context block about an end user — feed it straight into a ChatGPT/Claude step.”

Builds a context block about one end user, grouped and ready to drop into a prompt, around a topic you name. The AI step placed after it gets the background without you writing it.

When to use it
an assistant step drafts something for a person and should know their preferences first.
Watch out
Topic is required; describe what the next step is about, for example drafting a reply to their email.
3

Search Memories

Search

In Zapier“Semantic search over an end user’s memories by natural-language query.”

Searches one end user's memories by meaning, from a question written in everyday words rather than an exact keyword.

When to use it
you need one precise detail, such as a stated preference, rather than the full list.
Watch out
Query is required, and how close a match has to be is decided by MemorySync, so read the results at the test.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that depend on it are skipped. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking this box turns a search into a find-or-create. MemorySync offers no find-or-create variant, so this box plays no part in its three searches.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks

When a MemorySync Zap breaks

Zapier attaches no help article to MemorySync and lists no limit of its own for it. What breaks here is what breaks on any Zap.

Four cases are worth knowing before you publish. If one of them hits you, see our Zapier troubleshooting guide.

  • Old memories are not replayed

    A Zap only reacts to what happens after it is switched on. Memories stored before that are never picked up; moving that backlog is a separate job.

  • A Zap that sets itself off

    A Zap that writes where its own trigger watches can start itself again and burn tasks. Before publishing, look at where each action writes and where the trigger watches.

  • Flood protection on big batches

    After a bulk import or a migration, a trigger can suddenly return a huge batch. Zapier's flood protection can then hold those items back instead of running them.

  • The same memory twice? No

    On a polling trigger, Zapier keeps track of what it has already seen, so one memory does not start the Zap a second time.
Need help

Need help automating MemorySync with Zapier?

A person reads every message.

FAQ

MemorySync and Zapier: frequent questions

01Is the MemorySync Zapier integration free?
Yes, on the free plan. MemorySync is not a premium app, so Zapier lets every plan use it, and it is currently marked as beta. The free plan gives 100 tasks a month and an unlimited number of Zaps, but each Zap stops at two steps: one trigger and one action. Storing a conversation turn, or copying new memories to a spreadsheet, fits in that. Once you add a filter, a search such as Recall Context or a second action, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a MemorySync Zap use?
One per action that succeeds, and nothing for the trigger. Zapier never bills the checks it runs on New Memory, however often it looks. A Zap with one action costs one task each time it runs; with three actions it costs three. An action that fails is not counted. One point specific to MemorySync: New Memory starts the Zap once per extracted fact, so if MemorySync pulls two facts out of one conversation turn, the Zap runs twice and bills its actions twice.
03Does MemorySync trigger Zaps in real time?
No. New Memory is a polling trigger: Zapier asks MemorySync for new memories at a fixed interval. That interval depends on the plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On paid plans you can change how often it checks and run a check by hand from the editor. The type of a trigger is set by the app itself, so no setting in Zapier turns this one into an instant trigger.
04What does connecting MemorySync to Zapier require?
An account on MemorySync, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection is made once from the Apps page with + Add connection, then reused by every MemorySync step. Sign-in happens in a tab that MemorySync opens, where you grant Zapier access to the account. Have your End User ID logic ready as well: every operation requires it, so know which identifier your own app gives each person, such as customer-42.
05Why can one conversation turn start a MemorySync Zap several times?
Because New Memory fires once for each fact MemorySync extracts, not once per turn. If a user line holds two durable facts, the Zap runs twice, and each run bills its own actions as tasks. Small talk such as thanks extracts nothing, and assistant turns are never stored, so neither starts anything. When you size a task budget, count facts rather than messages, and check at the test how many memories a typical turn of yours produces.
06What if the MemorySync action you need is missing?
Then it is not part of this integration today: Zapier offers 7 operations for MemorySync, 1 trigger, 3 actions and 3 searches. The MemorySync page on Zapier shows the current list. Look at the action-event list again as well, because searches sit under their own heading at the bottom and are easy to miss. If the step really does not exist, that work has to happen in MemorySync itself or in another tool. Steer clear of workarounds that write where your trigger watches, since such a Zap can set itself off.
07Zapier, Make or n8n for MemorySync?
It depends on the criterion, not on a winner. On Zapier you get 7 ready operations, a free plan that runs two-step Zaps, and a polling trigger checked every 15 minutes on Free and faster on paid plans. Whether MemorySync exists as a ready module in Make or n8n is not covered here, so check their catalogues before deciding. Then compare how each tool counts usage: Zapier bills every successful action as a task and never the trigger. Pick the one whose catalogue and billing match how often your memories move.
Same platform

Other docs you might need on this stack.

Browse all integrations