Resources · Zapier integration

Memara Zapier integrationAutomate Memara with Zapier.

The Memara Zapier integration gives you 3 triggers, 2 actions and 2 searches. Your Zaps can write memories into Memara, update them, look them up by ID or by meaning, and react when a memory appears, changes or matches a query you wrote.

See the 7 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Memara Zapier integration is for

Memara is a memory system, driven by AI, that lets your automations keep information and find it again across workflows. With Zapier, any Zap can store something in Memara, change it later, read it back by ID or by meaning, and start when a memory is created, updated or matches a query.

An alert when a topic comes up. Memory Search Match watches for memories that match a query written in plain language, so a message reaches your team chat when something on that topic is stored.

A memory that stays current. Create Memory stores text or data from any app, and Update Memory changes it later from its Memory ID, so one record follows a subject over time instead of piling up copies.

Context for the next step. One Find Memory search reads a memory by its ID, the other finds memories by meaning, which lets a Zap fetch what it already knows before it writes or sends anything.

What Zapier does not do here: all three triggers are polling, so nothing starts the moment a memory changes, and no action deletes a memory. Two searches share the same name, Find Memory, which is easy to mix up: one asks for a Memory ID, the other for a Search Query. If you are weighing tools, see our n8n vs Zapier comparison.

Vocabulary

Zapier words in one minute

Eight words come back across this page. Here they are, once, 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 in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does once started: the step that writes, sends or moves something for you, such as a new memory.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling vs instant
Zapier checks a polling trigger on a timer that depends on your plan. An instant trigger is reported by the app the moment it happens.
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 that already exists in an app, so the steps after it can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A filter, a search or a second action makes it one, and it needs a paid plan.
Cost

What a Memara Zap really costs

Memara is not a premium app, so it works on the free plan. You pay in tasks, and only the actions that succeed make them.

  • Free plan100 tasks a month, unlimited Zaps
  • Steps per Zap on Free2 (one trigger, one action)
  • Trigger checks0 tasks
  • Premium appNo

The trigger never costs a task, and the regular checks Zapier runs on the Memara triggers cost nothing, however often they happen. Each action that goes through counts once; an action that fails is not counted. A Zap that searches, then updates a memory, then posts a message is multi-step, which needs a paid plan, since the free plan stops at two steps. All three Memara triggers are polling, so the interval grid below decides how soon a new or updated memory is picked up.

Connect

Connect your Memara account

  1. 01

    Open the Apps page

    In your Zapier account, open the Apps page and click + Add connection. A dialog with a search box opens: type Memara, then pick it from the list of results.

  2. 02

    Sign in to Memara

    Click Add connection. A tab opens on Memara: sign in with the account whose memories your Zaps will read and write. You need a Memara account before you start.

  3. 03

    Grant access

    Allow Zapier to use the account. The connection is saved once and reused by every Memara step, triggers, actions and searches alike, so the next Zap picks it up straight away.

First Zap

Your first Zap: share selected new memories with the team

GoalWhen a new memory appears in Memara and passes the condition you set in a filter, a message with its content goes to your team chat.

  1. 01

    Create the Zap

    Start a new Zap, pick Memara as the trigger app and New Memory as the event, then select the Memara connection you made earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent memories of the connected account, so you see what a memory carries before mapping it.

  3. 03

    Add a filter

    Click the plus icon, add Filter, then choose the field to look at, the rule and the value. A text rule only works on text, a number rule on numbers.

  4. 04

    Add the chat step

    Add your chat app with its send-message action, and map the memory content you saw at the test into the message your team will read.

  5. 05

    Test, then publish

    Test each step and read the message. The filter makes this a multi-step Zap on a paid plan. Click Publish to switch it on.

Triggers

Memara triggers

3 events start a Zap when something happens in Memara. Zapier checks for them at the interval your plan allows.

1

Memory Search Match

Polling trigger

In Zapier“Triggers when memories match a search query.”

Starts a Zap when memories match a query you write in plain language, such as the subject you want to track. It turns Memara into a watch on a topic rather than on every single memory.

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 only care about memories on one subject and want a message each time one shows up.
Watch out
Search Query is required and is written in natural language, so check at the test which memories come back before you publish.
2

Memory Updated

Polling trigger

In Zapier“Triggers when a memory is updated.”

Runs when an existing memory is changed. It lets another tool follow a memory over time rather than only at the moment it was first stored.

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
log each change to a memory in a spreadsheet, one row per update, so you can see how it evolved.
Watch out
as a general precaution, a Zap that writes back where its own trigger looks can set itself off again; check at the test what your actions change.
3

New Memory

Polling trigger

In Zapier“Triggers when a new memory is created.”

Fires when a new memory is created in Memara, whatever stored it. It is the broadest of the three triggers and the natural start for a log of everything Memara keeps.

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
share new memories with your team, with a filter to keep only the ones that matter.
Watch out
if the same Zap also writes into Memara, check at the test that it does not start itself again. Memories created before the Zap was switched on are never picked up.
Actions

Memara actions

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

1

Create Memory

Action

In Zapier“Create a new memory.”

Stores a new memory in Memara. Memory Content is required and can be text, data or anything else you want kept.

When to use it
save the gist of an email, a form entry or a call note so later Zaps can recall it.
Watch out
a Zap that writes where its own trigger looks can restart itself, so check at the test which trigger sits in front of it.
2

Update Memory

Action

In Zapier“Update an existing memory.”

Changes a memory that already exists. The Memory ID is required, so the Zap must know which memory to change.

When to use it
follow a subject with one memory that you refresh, rather than adding a new one each time.
Watch out
get the ID from an earlier step, such as a trigger or the Find Memory search by ID, and check it at the test.
Searches

Memara searches

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

A search step reads what Memara already holds and hands it to the steps that follow. Searches sit at the bottom of the event list, under SEARCH. Both Memara searches are called Find Memory: tell them apart by the field they ask for. Three settings decide what happens when the result is not the one you expected.

1

Find Memory

Search

In Zapier“Find a specific memory by ID.”

Reads one specific memory from its Memory ID, the single required field. This is the exact lookup of the pair.

When to use it
an earlier step gives you an ID, and you need the full memory before you update it or send it on.
Watch out
the editor shows two searches named Find Memory; this one asks for a Memory ID, the other for a Search Query.

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 and skips the steps that relied on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Memara exposes no find-or-create variant, so a missing memory has to be created by its own step.
  3. If multiple search results are found?
    Keep the first match, which is the default, stop the Zap, or hand all the matches on at once.
When it breaks

When a Memara Zap breaks

Zapier attaches no help article to Memara and lists no limit of its own for it. What breaks is what breaks on every app.

These cases cover the general limits worth knowing. If a Zap misbehaves for another reason, see our Zapier troubleshooting guide.

  • No backlog

    A Zap only reacts to memories created or updated after you switch it on. Older ones are never picked up; moving them is a separate job.

  • Loops between triggers and actions

    A Zap that writes into the very place its own trigger watches can set itself off again and again and burn through your tasks. Check at the test what each action writes.

  • Flood protection

    If a bulk import suddenly returns a huge batch of memories, Zapier can hold it back with its flood protection, whatever app it comes from.

  • No double start

    On these polling triggers, Zapier keeps track of what it has already seen, so the same memory does not start the Zap twice.
Need help

Need help automating Memara with Zapier?

A person reads every message.

FAQ

Memara Zapier integration: questions

01Is the Memara Zapier integration free?
Yes. Memara is not a premium app, so its triggers, actions and searches all work on the free Zapier plan. That plan gives 100 tasks a month and an unlimited number of Zaps, each limited to two steps: one trigger and one action. A Memory Search Match Zap that posts in your chat fits. Add a filter, a search or a second action, as in the first Zap above, and you need a paid plan.
02How many tasks does a Memara Zap use?
One per action that succeeds, nothing for the trigger. The checks Zapier runs on the Memara triggers are free however often they happen. A Zap that creates a memory from each new email costs one task per email. A Zap that updates a memory and then posts a message costs two per run, since each successful action counts on its own. An action that fails is not counted. Watching costs nothing at all.
03Do Memara triggers work in real time?
No. All three Memara triggers are polling: Zapier goes and looks at regular intervals, and the interval depends on your plan. That is every 15 minutes on Free, 2 minutes on Professional and 1 minute on Team and Enterprise. On paid plans you can change how often the check runs and trigger one by hand from the editor. The type is set by the app and cannot be switched to instant.
04What does connecting Memara to Zapier take?
A Memara account. Open the Apps page of your Zapier account, click + Add connection, pick Memara, sign in in the tab that opens and grant access. Every Memara step then reuses that connection. Since Update Memory and one of the searches work from a Memory ID, you also need read or write access on anything you do not own yourself and want the Zap to touch. The connection is made once, not per Zap.
05Why are there two Find Memory searches?
Because Memara offers two ways to look a memory up, and Zapier shows both under the same name. One asks for a Memory ID and returns that exact memory. The other asks for a Search Query, written in plain language, and finds memories by meaning; it can also search all your memory spaces. Pick the first when an earlier step gives you an ID, the second when you only know the subject.
06What if the Memara operation you want is not there?
Then this integration does not offer it. The Memara page on Zapier shows the current list of operations, so check there first. The list read for this page covers creating and updating memories, two ways of finding them and three triggers, but nothing deletes a memory. An update can sometimes stand in, for example by rewriting a memory's content instead of removing it. If it cannot, see whether another automation tool covers that step for Memara before you build around the gap.
07Zapier, Make or n8n for Memara?
Choose on criteria, not on a ranking. Coverage: on Zapier, Memara brings 3 polling triggers, 2 actions and 2 searches; compare that with what the other tools list for Memara. Timing: those triggers are checked on your plan's interval, every 15 minutes on Free, so ask how soon your process needs to react. Size and upkeep: Zapier's free plan stops at two steps, and the tool your team already knows is the easiest to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations