Content & Documents · Integration
Mem
Add Mem to your product for your customers, and give your AI agents governed access to it.
Mem is an AI note-taking and knowledge tool, and its current API is at api.mem.ai/v2 with a bearer API key; the older v0 mems endpoints now return an explicit deprecation response, so anything written against them must be moved. POST /v2/notes creates a note directly from Markdown content, while POST /v2/mem-it hands raw captured material to Mem to be summarised, titled and filed into collections automatically, which is the distinction implementers usually miss. Notes carry Markdown rather than rich text, and internal links between notes use Mem's own reference syntax rather than URLs. Collections behave as tags with a hierarchy rather than folders, so one note can sit in several collections at once. Auto-organisation is asynchronous, so a note created through mem-it may not show its final collections immediately after the call returns. fastn stores each customer's Mem key separately and keeps the connection working as the API version moves on.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Mem account so notes created in your product land in their knowledge base
Push meeting notes, call summaries or research output into Mem and let it file them into collections
Read back notes in a given collection to show related context inside your own interface
Keep a record in your app linked to the Mem note that was created from it
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent write a summarised note into a named collection while a human reviews the content first
Have an agent search the customer's notes for prior context before answering, audited per tenant
Restrict an agent to reading a single collection so unrelated personal notes stay out of scope
Example prompt
Save these meeting notes to Mem and file them under the customer research collection.
Set up Mem in 4 steps
- 01Enable the Mem connector from your fastn dashboard.
- 02Have each customer authorise their own Mem account, so calls run under their credentials rather than a shared key.
- 03Decide which files, documents and versions your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Mem integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Mem integration without building it. Your customers connect their own Mem account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Mem update is not your on-call problem.
- One integration serves your product and your agents. The same governed Mem connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Notion
Box
DocusignOften used alongside
Tools the same teams tend to run next to Mem, across other categories.
Shopify
Stripe
Jira
AsanaMem integration FAQ
How do I add a Mem integration to my product?
Enable the Mem connector in your fastn dashboard, then let each customer authenticate their own Mem account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Mem client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Mem account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Mem account and only ever sees their own files, documents and versions. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Mem integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent write a summarised note into a named collection while a human reviews the content first
Who maintains the Mem integration?
fastn does. When Mem changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose permissions does the Mem integration run under?
Each customer's own Mem grant. Where Mem holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Mem automatically?
Where Mem supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Mem integration?
A common starting point: let a customer connect their own Mem account so notes created in your product land in their knowledge base. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Mem integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Mem does not change your per-connector cost. You can start free with 3 connected accounts.
Add Mem to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.