Memento Database Zapier integrationAutomate Memento Database with Zapier.
The Memento Database Zapier integration gives you 2 triggers, 2 actions and 1 search. Both triggers are instant: Memento tells Zapier when an entry is added or a watched field changes. Here is what each step does, what it costs, and where it trips.
Verified Trustpilot reviews · AI, automation & growth agency
What the Memento Database Zapier integration does
The Memento Database Zapier integration links your Memento libraries to the rest of your tools through Zaps, the automations you build on Zapier. Memento Database is a tool for organizing, storing and analyzing data, on mobile as well as desktop. On Zapier, it can start a Zap, receive entries and look one up.
Three results you can build, each on a real step. A copy of every new record somewhere else: Entry Created starts the Zap when an entry is added to a library, and the next step writes it where your team reads it. A reaction to a status change: Field Value Changed watches one field you pick and starts the Zap when its value moves. And a record kept in sync from another tool: Find an Entry locates the right entry by a field value, then Update Entry rewrites the fields you choose.
Say entries are logged in a Memento library from a phone. Each new one can be copied into a shared sheet that others read on a desktop, with nobody retyping it (and nobody waiting for someone to sync by hand).
What Zapier does not do here. It does not watch the whole library for any edit: Field Value Changed follows one field per Zap. It offers no delete step, so removing an entry stays a manual job. And it does not offer a find-or-create shortcut on Find an Entry, so a missing entry needs its own Create Entry step.
Weighing other tools first? See our n8n vs Zapier comparison and our Make vs Zapier comparison.
Zapier words, in one minute
A handful of Zapier terms run through this page. One plain line each, then they are used without a reminder.
- Zap
- The automation itself: 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 on, Zapier waits for it, here a new entry or a changed field.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like creating an entry.
- Task
- The unit Zapier bills: one action that completes successfully. The count on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked on a timer set by your plan. An instant trigger is reported by the app itself the moment the event happens.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, 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 one, and it needs a paid plan.
What a Memento Database Zap costs
Memento Database is not a premium app, so it works on the free plan. The trigger itself never costs a task, and looking for new data costs nothing either.
- Free plan100 tasks a month, unlimited Zaps of two steps each
- Premium appNo, Memento Database runs on the free plan
- BilledEach action that succeeds, one task each
- Search or filterMakes the Zap multi-step, paid plan needed
Only a completed action is billed: each Create Entry or Update Entry that succeeds counts as one task, and one that fails is not counted. The free plan stops at a trigger plus one action, so adding Find an Entry or a filter makes the Zap multi-step and paid. The interval grid below is Zapier's polling schedule per plan; it does not apply to Memento's two triggers, which are both instant and start the Zap right away on every plan.
Connect your Memento Database account
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your Memento account linked once, then reused by every step that works with Memento.
- 02
Pick Memento Database
Search Memento Database in the dialog, pick it, then click Add connection. You need a Memento account first, plus read or write access on any library you do not own yourself and want the Zap to touch.
- 03
Sign in and allow access
A tab opens on Memento. Sign in and grant Zapier access to the account. From then on, any Memento trigger, action or search in your Zaps can use that connection.
Your first Memento Database Zap
GoalWhen the status field of an entry changes and matches your rule, send a message to the person in charge.
- 01
Create the Zap
Start a new Zap in the editor. It will have three steps: the field change, a filter, then the email. The filter makes it a multi-step Zap, which needs a paid plan.
- 02
Set the trigger
Choose Memento Database, then Field Value Changed. Pick the Library and, in Field to Monitor for Changes, the one field that matters, such as the status.
- 03
Test the trigger
Run the test. Zapier brings back the three most recent items of the connected account, so map the next steps on a real entry rather than an invented one.
- 04
Add the filter
Add a Filter step and fill its three boxes: the field to look at, the rule, the value to compare with. A text rule only works on text, so pick the right kind.
- 05
Add the email, test, publish
Add your email tool's action and map the entry's values into it. Test each step and read what came back, then publish the Zap to switch it on.
The 2 Memento Database triggers
2 events start a Zap when something happens in Memento Database, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
Entry Created
Instant triggerIn Zapier“Triggers when there's a new entry.”
Starts your Zap each time a new entry is added to the library you chose, so whatever someone records in Memento can travel on to another tool without being retyped.
Field Value Changed
Instant triggerIn Zapier“Triggers when an entry's field value changes.”
Watches one field of the entries in a library and starts your Zap when its value changes, rather than reacting to every edit on the entry.
The 2 Memento Database actions
Memento Database gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Entry
ActionIn Zapier“Creates a new entry.”
Adds a fresh entry to a Memento library, filled with values the earlier steps carried in.
Update Entry
ActionIn Zapier“Update the values of specific fields in an entry.”
Rewrites the values of chosen fields on an entry that already exists, leaving the rest as it is.
The Memento Database search
1 search step looks for data that already exists in Memento Database, so a later step can use it.
A search step looks up something that already exists and hands it to the steps after it. On Memento, it is how a Zap finds the entry to update. Three settings decide what happens around it.
Find an Entry
SearchIn Zapier“Finds an entry by field values.”
Looks up an entry in a library by matching one field against a value you pass, then hands the entry to the next steps.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there, and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?On apps that offer it, this box turns the search into a find-or-create. Memento Database exposes no such variant on Zapier, so a missing entry needs its own Create Entry step.
- If multiple search results are found?Three ways out when several entries match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When a Memento Database Zap breaks
Zapier ties no help article to Memento Database and lists no limit of its own. What goes wrong is what goes wrong on any Zap, applied to your libraries.
Three cases to know before you switch the Zap on. If a run fails and the reason is not obvious, see our Zapier troubleshooting guide.
Past entries stay where they are
A Zap only reacts to what happens after it is published. Entries already in the library are not picked up; moving that backlog is a separate job.A Zap can wake itself up
A Zap that writes into the very place its trigger watches can set itself off again and again, and burn through tasks. Keep the written field away from the watched one.Big imports can be held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.
Need help automating Memento Database with Zapier?
A person reads every message.
