Mem

Mem is the AI note taking app. Agents create notes and read their versions, organize collections, search across notes and attachments, capture content through Mem It, work the assistant's tasks, projects, and follow-ups, read the calendar, and poll the account's event feed.

Verified 1 trigger 39 actions API key available

Mem website Platform Documentation Capability data verified 2026-08-24

A meeting ends, a document arrives, or a thread closes with something worth keeping

Mem It hands the raw material over with instructions in plain language, and Mem decides how to file it

Find Related Notes surfaces what the account already holds on the same subject

Extended Search Notes looks inside attachments as well as note bodies, so an answer sitting in a PDF is found rather than missed

Get Note returns the current body and its version immediately before any write, because a note changed elsewhere will be refused

The owner is told what was captured and what it now connects to

When the agent wants to fold new material into a note somebody already wrote, that person approves the replacement body before it is written

What This Integration Enables

Most note connectors ask a workflow to know where something belongs before it can save it. Mem inverts that, and Mem It is the operation that says so: it takes a web page, an email, a transcript, or plain prose along with an instruction in ordinary language, and lets Mem work out how to remember it. That is the right tool when a workflow has content and no opinion about its destination, and Create Note is the right tool when it knows exactly what it wants written. FlowRunner agents use both, plus collections, two different searches, the assistant's tasks, projects and follow-ups, calendar reads, and an event feed that follows Mem's own sequence watermark so nothing is missed and nothing arrives twice. Every action is built and verified against Mem's published API.

The detail worth building on is that Mem refuses to be overwritten carelessly. Update Note takes the complete markdown and the exact version read from Get Note, and a note that changed elsewhere in the meantime is refused rather than silently replaced. There is no partial patch. Most APIs would let a workflow win that race and never mention it. Mem stops it, which is the same instinct FlowRunner's human-in-the-loop design is built on, applied at the storage layer: the write that could destroy somebody's work does not happen quietly. This page's gate takes that one step further, because a version check protects against the wrong version, not against the wrong judgment.

Without FlowRunner

Filing is the tax on capturing Anything worth keeping needs somebody to decide where it goes, so most of it is never kept

Answers hide inside files The number is in a PDF or an audio recording, and searching note titles never finds it

Blind overwrites An automated append rewrites a note somebody edited five minutes ago, and nobody notices

With FlowRunner

Capture without a filing decision Raw material is handed over with an instruction, and the destination is worked out on arrival

Search reaches inside attachments One query covers note bodies and the contents of the documents, transcripts, and emails attached to them

Writes that refuse to clobber Every update carries the version it read, so a note changed in the meantime is refused rather than overwritten

Use Case Scenarios

Meeting output that files itself

A call ends and its recording and transcript land somewhere a workflow can reach. The agent passes the transcript to Mem It with an instruction written the way a person would say it, such as extracting the decisions and the owners and relating it to the account it concerns, and Mem places the result. Context tells Mem how the material relates to what it already knows, which is what keeps a recurring meeting building one thread rather than forty disconnected notes. The agent then calls Find Related Notes on the result, which embeds the source note at request time rather than relying on a stale index, so a note created moments ago is compared on what it actually says. The links it finds go into a summary posted to Slack, and any action items become tasks in Asana.
The answer that lives inside a file

Somebody asks a question whose answer is in a contract, a slide deck, or a recorded call. The agent runs Extended Search Notes, which searches note bodies and the contents of their attachments together across PDFs, images, audio recordings, calendar events, and emails, and returns the matching excerpt from inside the file. Where the hit is a long document and the workflow needs one fact, Ask About Attachment answers a single focused question from that attachment alone rather than reading it page by page. For a recorded call, Get Audio Recording returns the transcript with each turn attributed to a participant where Mem knows the name. The reply carries the passage and the note it came from, so the asker can check it.
A working library that stays organized

Collections are Mem's shelves, and an agent can keep them straight without anyone doing it by hand. On a schedule, the agent reads collections with List Collections, uses Search Notes with structured filters to find notes that belong somewhere they are not, and calls Add Note To Collection or Move Note Between Collections to place them. Moving is safe by construction, because Mem adds the note to the target before removing it from the source, so it is never in neither. Notes that no longer belong anywhere are removed from a collection with Remove Note From Collection, which leaves the note itself and every other collection it sits in untouched. Nothing is deleted by this sweep; the recoverable removal is Trash Note, and Restore Note brings it back.

Human-in-Loop Highlight

Update Note replaces a note's entire body. There is no partial patch, so an agent adding this week's findings to a running research note must send the whole document back, and whatever structure the author built is preserved only because the agent reproduced it correctly. Mem's version check catches the case where somebody else edited the note first, which is real protection, but it cannot catch the case where the agent's rewrite is simply worse than what was there. The first line of the content becomes the note's title, so a clumsy merge can also silently rename the note out from under whoever bookmarked it. That is why the agent drafts rather than writes. It calls Get Note, produces the merged markdown, and posts the difference to the author: "Adding three findings to your note 'Q3 pricing research'. This replaces the whole body, since Mem has no partial update. The title line is unchanged and your two existing sections are intact below the new material. Approve, edit, or save this as a separate note instead?" The author answers, and only an approved body is written back with the version the agent read. The agent did the drafting and the version handling. The person kept authorship of their own note.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

39 actions

Capture

Mem It Hands raw material to Mem and lets it decide how to remember it, whether that is a web page, an email, a transcript, or plain text. Instructions steer that in ordinary language, and Context tells Mem how the input relates to what it already knows. The operation to reach for when a workflow has content but no opinion about where it belongs.

Notes

List Notes Returns notes, newest updated first. It pages with an opaque cursor, so the same filters and ordering have to be reused across pages.
Get Note Returns a note's full current state, including its version and its attachment metadata. A trashed note still comes back, marked as trashed, rather than answering not found.
Create Note Creates a note from markdown. The first line of the content becomes the title, since there is no separate title field, and collection titles can be matched by name so a note is filed without looking any ids up.
Update Note Replaces a note's whole body. It requires the version read from Get Note, and a note changed elsewhere in the meantime is refused rather than overwritten, which is the point of it and the reason this page's human gate sits here.
Set Note Created At Changes a note's visible creation time without touching its content. It can only move the date backwards, which is what an import of older material needs.
Trash Note Moves a note to the trash. This is the recoverable removal, and the right default for any automated cleanup.
Restore Note Brings a trashed note back. It only reverses the trash; a note removed with Delete Note is gone for good.
Delete Note Permanently deletes a note. Mem states it cannot be restored, so Trash Note is the operation an automated sweep should be using instead.

Search

Find Related Notes Returns notes semantically related to one note. Mem embeds the source note at request time, so a note created or edited moments ago is compared on its current content rather than a stale index.
Search Notes Searches notes by free text with structured filters. Paging past the first page needs the snapshot id from the previous answer as well as the offset, or the result set shifts underneath the workflow.
Extended Search Notes Searches notes and the contents of their attachments together, across PDFs, images, audio recordings, calendar events, and emails, returning each hit with the matching context from inside the attachment. The search to use when the answer may be in a file rather than in a note.
Search Collections Searches collections by free text. It returns a bounded, relevance ranked set with no paging cursor, so List Collections is what a complete walk uses.

Collections

List Collections Returns collections, newest updated first, with the same opaque cursor paging as the notes list.
Get Collection Returns one collection.
Create Collection Creates a collection. Supplying an id makes a retried create idempotent, since Mem answers with a conflict rather than making a second one.
Update Collection Renames a collection or changes its description. Only the fields sent change, and an empty description clears it while omitting it keeps it.
Delete Collection Permanently deletes a collection. The notes inside it survive; only the collection goes.
Add Note To Collection Files an existing note into an existing collection. It only creates the link, so neither the note nor the collection's other contents change.
Remove Note From Collection Takes a note out of a collection. The note is untouched and stays in every other collection it belongs to.
Move Note Between Collections Moves a note from one collection to another. Mem adds it to the target first and then removes it from the source, so it is never in neither.

Attachments

Read Attachment Returns the structured contents of one attachment, across kinds: a PDF as pages, an audio recording as its transcript, a calendar event and an email as their own fields.
Ask About Attachment Asks one focused question about a single attachment and gets an answer drawn only from it. The shortcut past reading a long document when a workflow needs one fact out of it.
Get Attachment Download URL Returns a temporary signed URL for a note attachment. It is short lived, so a workflow should use it immediately rather than storing it.
Get Audio Recording Returns an audio recording's transcript and metadata, with speaker labels on by default so each turn is attributed to a participant where Mem knows the name.

Assistant

List Tasks Returns the assistant's tasks, newest updated first.
Get Task Returns one of the assistant's tasks.
List Projects Returns the assistant's projects.
Get Project Returns one of the assistant's projects.
List Follow Ups Returns the assistant's follow-ups, and ordering by the soonest scheduled first is what a reminder workflow wants.
Get Follow Up Returns one follow-up.

Calendar

List Calendars Returns the calendars Mem can see.
List Calendar Connections Returns which calendar accounts are connected to Mem, and their state.
List Calendar Events Returns calendar events in a window. The filters are inclusive at both ends, so an event spanning the window is included.
Get Calendar Event Returns one calendar event.

Events

List Event Types Returns the event types the feed can carry. Run it to see what a workflow can subscribe to, since the names are what the trigger's filter takes.
List Events Returns the account's events in sequence order. It is a watermark feed rather than a time range, so keeping the sequence from each answer and passing it back means nothing is missed or repeated.
Get Event Returns one event from the feed.

Service

Get Service Info Returns Mem's own service information, which is the cheapest call available for checking that a connection is alive.

Triggers

1 triggers

Event Triggers

On Mem Event Fires for each new event in the Mem account, such as a note being created or updated. It follows Mem's own sequence watermark, so nothing is missed and nothing arrives twice, even across a restart. Mem's events are deliberately thin: each one names what changed rather than carrying it, so a workflow normally follows with Get Note to read the record itself before acting on it.

Frequently Asked Questions

What can FlowRunner do with Mem?

FlowRunner agents can run Mem It, List Notes, and Get Note in Mem, plus 36 more actions.

Does connecting Mem to FlowRunner require OAuth?

No. Mem connects to FlowRunner with an API key, no OAuth flow required.

Can Mem trigger a FlowRunner workflow automatically?

Yes. Mem supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Mem

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us