Mem0 is an universal, self-improving memory layer for LLM applications.
Mem0 is an universal, self-improving memory layer for LLM applications. On Nagent, Mem0 is exposed as a fully-configurable artificial intelligence integration that any agent can call — 47 actions, and API key authentication. No code is required to wire Mem0 into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Mem0 to automate the kinds of tasks artificial intelligence teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Mem0 into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Mem0, with input parameters and output schema. Drop these into any step of an agent built in Helix.
MEM0_ADD_MEMBER_TO_PROJECTAdds an existing user to a project (identified by `project_id` within organization `org_id`), assigning a valid system role.
Input parameters
Role defining the new member's project permissions. Must be either 'OWNER' or 'READER'.
Email address of the user to add to the project.
Identifier of the organization owning the project.
Identifier of the project to add the member to.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_ADD_NEW_MEMORY_RECORDSStores new memory records from a list of messages, optionally inferring structured content; requires association via `agent_id`, `user_id`, `app_id`, or `run_id`.
Input parameters
If true, infers structured memories from messages; otherwise, stores messages directly.
Unique identifier for the application associated with this memory. At least one of agent_id, user_id, app_id, or run_id must be provided.
Optional unique identifier for the organization associated with this memory.
Unique identifier for the run associated with this memory. At least one of agent_id, user_id, app_id, or run_id must be provided.
Unique identifier for the user associated with this memory. At least one of agent_id, user_id, app_id, or run_id must be provided.
Unique identifier for the agent associated with this memory. At least one of agent_id, user_id, app_id, or run_id must be provided.
Comma-separated keywords to exclude specific topics, aiding in filtering out irrelevant information.
Comma-separated keywords to include specific topics, aiding filtering and prioritization.
List of message objects forming the memory's content. Each message should have 'role' (e.g., 'user' or 'assistant') and 'content' (text content). Alternative: You can also provide 'records' with 'text' field which will be automatically converted to messages format.
The name of the organization for this memory. Deprecated: use `org_id` instead.
Whether to process memories asynchronously (default: true). When true, returns event_id/status/message for tracking background processing. When false, processes synchronously and returns id/event/memory fields. Most clients use the default async mode.
Optional unique identifier for the project associated with this memory.
The name of the project for this memory. Deprecated: use `project_id` instead.
Specifies the response output format. 'v1.1' offers enhanced detail; 'v1.0' (default) will be deprecated.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_ADD_ORGANIZATION_MEMBERAdds a new member, who must be a registered user, to an organization, assigning them a specific role.
Input parameters
The role (should be in uppercase) to be assigned to the user within the organization (allowed values: 'OWNER' and 'READER'). This dictates the user's permissions.
The email of the user to be added to the organization.
Unique identifier of the organization to which the member will be added.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_CREATE_A_NEW_AGENTCreates a new agent with a unique `agent_id` and an optional `name`; additional metadata may be assigned by the system.
Input parameters
Human-readable name for the agent, used for display or easier identification. This field is required by the API.
Unique identifier for the agent, used for referencing in subsequent API calls.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_CREATE_A_NEW_AGENT_RUNCreates a new agent run in the mem0.ai system.
Input parameters
Human-readable name for the agent run. Required by the API.
Client-defined identifier for the agent run. Should be unique for distinct identification.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_CREATE_A_NEW_APPLICATIONCreates a new application, allowing metadata to be passed in the request body (not an explicit field in this action's request model); ensure `app_id` is unique to avoid potential errors or unintended updates.
Input parameters
A required, human-readable name for the application. The API requires this field to be provided.
The unique identifier for the application to be created. This ID will be used to reference the application in subsequent API calls.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_CREATE_A_NEW_ORGANIZATION_ENTRYCreates a new organization entry using the provided name and returns its details.
Input parameters
The name for the new organization.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_CREATE_A_NEW_USERCreates a new user with the specified unique `user_id` and supports associating `metadata` (not part of the request schema fields).
Input parameters
The unique identifier for the new user. This ID will be used for future references to this user.
Additional metadata to associate with the user
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_CREATE_MEMORY_ENTRYLists/searches existing memory entries with filtering and pagination; critically, this action retrieves memories and does *not* create new ones, despite its name.
Input parameters
Page number for paginated results (1-indexed).
Unique organization ID to filter memories. Preferred over the deprecated `org_name`.
Required filters to retrieve memories (CANNOT be empty - must specify at least one filter condition). Logical operators (`AND`, `OR`, `NOT`) must be UPPERCASE and take a list of conditions. Comparison operators must be lowercase: `in` (matches any value), `gte` (>=), `lte` (<=), `gt` (>), `lt` (<), `ne` (not equal), `contains`, `icontains` (case-insensitive). Use `*` as wildcard to match any value for a field. ONLY the following 8 fields are supported (no other fields like 'status', 'tags', 'metadata', 'timestamp', 'feedback', etc. are allowed): user_id, agent_id, app_id, run_id, created_at, updated_at, categories, keywords.
DEPRECATED: Organization name to filter memories. Use `org_id` instead for improved stability and future compatibility.
Number of memory entries per page.
Unique project ID to filter memories. Preferred over the deprecated `project_name`.
DEPRECATED: Project name to filter memories. Use `project_id` instead for improved stability and future compatibility.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_CREATE_PROJECTCreates a new project with a given name within an organization that must already exist.
Input parameters
The name to be assigned to the new project.
The unique identifier of the organization under which the new project will be created.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_CREATE_WEBHOOKCreates a new webhook for a specific project to receive real-time notifications. Use when you need to set up event-driven integrations that trigger on memory operations.
Input parameters
URL endpoint where webhook events will be sent. Must be a valid HTTPS URL.
Human-readable name for the webhook to help identify its purpose.
Whether the webhook should be active immediately after creation. Defaults to true if not specified.
Unique identifier of the project to create the webhook for.
List of event types to subscribe to. If not specified, webhook will receive all event types.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_DELETE_AN_ORGANIZATIONPermanently deletes an existing organization identified by its unique ID.
Input parameters
The unique identifier of the organization that is to be deleted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_DELETE_A_SPECIFIC_MEMORY_BY_IDPermanently deletes a specific memory by its unique ID; ensure the `memory_id` exists as this operation is irreversible.
Input parameters
The unique identifier of the memory to be deleted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_DELETE_ENTITY_BY_TYPE_AND_IDCall to permanently and irreversibly hard-delete an existing entity (user, agent, app, or run) and all its associated data, using its type and ID.
Input parameters
Unique identifier (ID) of the entity for deletion. Can be an integer ID or a string identifier.
Type of the entity to be deleted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_DELETE_MEMORIES_ENDPOINTDeletes all memories matching specified filter criteria. IMPORTANT: At least one filter (agent_id, user_id, app_id, or run_id) must be provided to prevent accidental deletion of all memories. Requires delete permissions on the organization/project.
Input parameters
Deletes all memories associated with this app ID. At least one of user_id, agent_id, app_id, or run_id is required.
Organization ID to scope the deletion. Preferred over org_name.
Deletes all memories associated with this run ID. At least one of user_id, agent_id, app_id, or run_id is required.
Deletes all memories associated with this user ID. At least one of user_id, agent_id, app_id, or run_id is required.
Deletes all memories associated with this agent ID. At least one of user_id, agent_id, app_id, or run_id is required.
Optional additional filter: deletes memories matching this metadata criteria.
Organization name to scope the deletion. Deprecated: use `org_id` instead.
Project ID to scope the deletion. Preferred over project_name.
Project name to scope the deletion. Deprecated: use `project_id` instead.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_DELETE_MEMORY_BATCH_WITH_UUIDSDeletes a batch of up to 1000 existing memories, identified by their UUIDs, in a single API call.
Input parameters
A list of memory objects, each containing a memory_id field with the UUID of the memory to be deleted. Maximum of 1000 memories can be deleted in a single request. Also accepts 'memory_ids' as a simple list of UUID strings.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_DELETE_PROJECTPermanently deletes a specific project and all its associated data from an organization; this action cannot be undone and requires the project to exist within the specified organization.
Input parameters
The unique identifier of the organization to which the project belongs.
The unique identifier of the project to be deleted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_DELETE_PROJECT_MEMBERRemoves an existing member, specified by email address, from a project, immediately revoking their project-specific access; the user is not removed from the organization.
Input parameters
Email address of the member to be removed from the project.
Unique identifier of the organization containing the project.
Unique identifier of the project from which the member will be removed.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_DELETE_WEBHOOKDeletes a webhook and stops receiving notifications for the specified webhook ID. Use this when you no longer need webhook notifications or want to remove a specific webhook configuration.
Input parameters
Unique identifier of the webhook to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_EXPORT_DATA_BASED_ON_FILTERSCreates a new memory export job with optional entity filters (user_id, agent_id, app_id, run_id). Returns export job ID and confirmation message. Requires org_id and project_id. Uses default schema for memory structure if not specified.
Input parameters
Filter to export memories for a specific App ID. At least one of user_id, agent_id, app_id, or run_id must be provided.
Organization ID for the memory export.
Filter to export memories for a specific Run ID. At least one of user_id, agent_id, app_id, or run_id must be provided.
Schema definition for the export structure. Defaults to {"type": "object", "properties": {"memory": {"type": "string"}}} if not provided.
Internal field used to structure filters for the API. Automatically populated from user_id, agent_id, app_id, and run_id fields.
Filter to export memories for a specific User ID. At least one of user_id, agent_id, app_id, or run_id must be provided.
Filter to export memories for a specific Agent ID. At least one of user_id, agent_id, app_id, or run_id must be provided.
Project ID for the memory export.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_FETCH_DETAILED_LIST_OF_ORGANIZATIONSRetrieves a summary list of organizations for administrative oversight; returns summary data (names, IDs), not exhaustive details, despite 'detailed' in the name.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_FETCH_DETAILS_OF_A_SPECIFIC_ORGANIZATIONFetches comprehensive details for an organization using its `org_id`; the `org_id` must be valid and for an existing organization.
Input parameters
Unique identifier of the organization.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_FETCH_LIST_OF_ENTITY_FILTERSRetrieves predefined filter definitions for entities (e.g., by type, creation/modification date); returns definitions only, not filtered entity data.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_FETCH_SPECIFIC_ENTITY_DETAILS_WITH_OPTIONAL_FILTERSFetches detailed information for an existing entity (user, agent, app, or run) identified by its type and unique ID.
Input parameters
The unique integer identifier (ID) of the entity to retrieve. Must be a positive integer.
The type of the entity (user, agent, app, or run).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_GET_EVENT_STATUS_BY_EVENT_IDRetrieves a single async event by ID to check its current status and results. Use this after operations that return event IDs (e.g., add_new_memory_records) to poll for completion before proceeding with dependent operations.
Input parameters
Unique identifier of the event to retrieve (UUID format).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_GET_MEMORIES_BY_ENTITYTool to retrieve all memories associated with a specific entity (user, agent, app, or run). Use when you need to fetch memories for a known entity type and ID combination.
Input parameters
Page number for paginated results (1-indexed). Default: 1.
The unique identifier of the entity whose memories to retrieve.
Number of memories to return per page. Default: 100.
Type of the entity. Must be one of: 'user', 'agent', 'app', 'run'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_GET_MEMORY_EXPORTRetrieves the status and results of a memory export job by its ID. Use this after creating an export job to fetch the processed memory data. The response structure matches the schema defined during export creation.
Input parameters
Organization ID filter. Can be an empty string if not filtering by organization.
Project ID filter. Can be an empty string if not filtering by project.
The unique identifier (UUID format) of the memory export job to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_GET_ORGANIZATION_MEMBERSFetches a list of members for a specified, existing organization.
Input parameters
The unique identifier of the organization for which members are to be listed.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_GET_PROJECT_DETAILSFetches comprehensive details for a specified project within an organization.
Input parameters
The unique identifier for the organization to which the project belongs.
The unique identifier for the project whose details are to be retrieved.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_GET_PROJECT_MEMBERSRetrieves all members for a specified project within an organization.
Input parameters
Unique identifier of the organization.
Unique identifier of the project.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_GET_PROJECTSRetrieves all projects for a given organization `org_id` to which the caller has access.
Input parameters
The unique identifier of the organization for which to retrieve projects.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_GET_PROJECT_WEBHOOKSRetrieves all webhooks configured for a specific project. Use this to list webhook configurations including their event types, URLs, and active status.
Input parameters
Unique identifier of the project.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_GET_USER_MEMORY_STATSRetrieves a summary of the authenticated user's memory activity, including total memories created, search events, and add events. Note: This endpoint is undocumented in the official mem0 API specification but is functional.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_LIST_ENTITIES_WITH_OPTIONAL_ORG_AND_PROJECT_FILTERSRetrieves a list of entities, optionally filtered by organization or project (prefer `org_id`/`project_id` over deprecated `org_name`/`project_name`), noting results may be summaries and subject to limits.
Input parameters
Filter entities by the unique identifier of the organization. Must be provided together with project_id (both or neither).
Filter entities by organization name; this field is deprecated, prefer using `org_id` for more stable filtering.
Filter entities by the unique identifier of the project. Must be provided together with org_id (both or neither).
Filter entities by project name; this field is deprecated, prefer using `project_id` for more stable filtering.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_PERFORM_SEMANTIC_SEARCH_ON_MEMORIESSearches memories semantically using a natural language query and metadata filters. IMPORTANT: - At least one of 'user_id', 'agent_id', or 'run_id' MUST be provided - A non-empty 'query' string is REQUIRED for semantic search - To retrieve memories without a search query, use 'retrieve_memory_list' action instead
Input parameters
Natural language search query for semantic search. Must be a non-empty string. IMPORTANT: If you need to retrieve all memories for a user/agent without a specific search query, use the 'retrieve_memory_list' action (GET /v1/memories/) instead, which supports filtering by user_id, agent_id, metadata, and other parameters without requiring a semantic search query.
Maximum number of relevant memory results to return.
Filter by application ID. Optional additional filter.
Specific field names for inclusion in response for each memory; if empty/unprovided, all fields are returned.
Filter memories by organization ID.
If true, applies an additional reranking step to search results for potentially improved relevance.
Filter by run ID. REQUIRED: At least one of 'user_id', 'agent_id', or 'run_id' must be provided.
Filter by user ID. REQUIRED: At least one of 'user_id', 'agent_id', or 'run_id' must be provided. This is the most commonly used filter.
Filter by agent ID. REQUIRED: At least one of 'user_id', 'agent_id', or 'run_id' must be provided.
A dictionary of key-value pairs to filter memories. Only memories matching all key-value pairs in the provided metadata will be returned.
Filter memories by organization name (deprecated; use `org_id` instead).
Filter memories by a list of categories; returns memories matching at least one category.
Filter memories by project ID.
Filter memories by project name (deprecated; use `project_id` instead).
Specifies the output format for results. 'v1.0' is used if not provided. Supported: 'v1.0', 'v1.1'.
If true, strictly applies all provided metadata filters (e.g., `user_id`, `agent_id`, `categories`).
If true, search uses only the 'metadata' parameter for filtering (query is ignored for semantic matching). When true, the 'metadata' parameter must be provided. NOTE: This parameter may not be supported in all API versions. For simple retrieval of all memories without semantic search, use the 'retrieve_memory_list' action instead.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_REMOVE_A_MEMBER_FROM_THE_ORGANIZATIONRemoves a member, specified by their username, from an existing organization of which they are currently a member.
Input parameters
The email address of the member to be removed from the organization.
Unique identifier of the organization from which the member will be removed.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_RETRIEVE_ALL_EVENTS_FOR_THE_CURRENTLY_LOGGED_IN_USERRetrieves a paginated list of events for the authenticated user, filterable and paginable via URL query parameters. This is a read-only operation that does not modify data. Supported Query Parameters (applied directly to the request URL): - `event_type` (str, optional): Filters events by their type (e.g., 'ADD', 'SEARCH'). - `start_date` (str, optional): Filters events on or after this date (format: YYYY-MM-DD). - `end_date` (str, optional): Filters events on or before this date (format: YYYY-MM-DD). - `page` (int, optional): Specifies the page number for paginated results. - `page_size` (int, optional): Number of events per page (default: 50, max: 100).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_RETRIEVE_LIST_OF_MEMORY_EVENTSRetrieves a chronological list of all memory events (e.g., user inputs, AI responses) from the Mem0 platform, providing interaction history and context for AI assistants.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_RETRIEVE_MEMORY_BY_UNIQUE_IDENTIFIERRetrieves a complete memory entry by its unique identifier; `memory_id` must be valid and for an existing memory.
Input parameters
Unique identifier of the memory to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_RETRIEVE_MEMORY_HISTORY_BY_IDRetrieves the complete version history for an existing memory, using its unique `memory_id`, to inspect its evolution or audit changes.
Input parameters
Unique identifier of the memory for which history is to be retrieved.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_RETRIEVE_MEMORY_LISTRetrieves a list of memories, supporting pagination and diverse filtering (e.g., by IDs, metadata, keywords, date ranges); ensure dates are ISO 8601 and `page`/`page_size` (if used) are positive integers. REQUIRED: At least one of agent_id, user_id, app_id, or run_id must be provided.
Input parameters
The page number for pagination, starting from 1. Default: 1.
The unique identifier of the application associated with the memories. At least one of user_id, agent_id, app_id, or run_id is required.
A list of specific field names to consider during filtering. This might involve checking for the existence of these fields or scoping other filters (e.g., keywords) to them.
The unique identifier of the organization to filter memories by. Must be provided together with project_id, or both must be omitted.
The unique identifier of a specific run or session to filter memories by. At least one of user_id, agent_id, app_id, or run_id is required.
The unique identifier of the user whose memories are to be retrieved. At least one of user_id, agent_id, app_id, or run_id is required.
The unique identifier of the agent associated with the memories to be retrieved. At least one of user_id, agent_id, app_id, or run_id is required.
The end date (inclusive) for filtering memories, typically in ISO 8601 format (e.g., 'YYYY-MM-DDTHH:MM:SSZ' or 'YYYY-MM-DD').
Keywords to search for within the memories. The search might be across all text fields or restricted by the `fields` parameter if specified.
A dictionary of key-value pairs to filter memories. Only memories matching all key-value pairs in the provided metadata will be returned.
The name of the organization to filter memories by. This field is deprecated and will be removed in a future version; please use `org_id` instead.
The number of memories to return per page. Default: 100.
A list of categories to filter memories by. Memories matching any of the specified categories will be returned.
The unique identifier of the project to filter memories by. Must be provided together with org_id, or both must be omitted.
The start date (inclusive) for filtering memories, typically in ISO 8601 format (e.g., 'YYYY-MM-DDTHH:MM:SSZ' or 'YYYY-MM-DD').
The name of the project to filter memories by. This field is deprecated and will be removed in a future version; please use `project_id` instead.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_SEARCH_MEMORIES_WITH_QUERY_FILTERSSemantically searches memories using structured filters with an optional natural language query. If query is omitted, defaults to '*' (wildcard) for filter-only searches. Offers options to rerank results, select specific fields, and adjust similarity threshold; any provided `org_id` or `project_id` must reference a valid existing entity.
Input parameters
Natural language query for searching memories. The API requires this field to be non-blank, so it defaults to '*' for filter-only searches. Omit or use '*' to retrieve memories matching only the filters without semantic search constraints.
Maximum number of most relevant search results to return.
Specific field names to include in returned memory objects (e.g., 'text', 'source', 'metadata.custom_field'). If omitted, all fields are returned.
UUID of the organization to scope the memory search; preferred over `org_name`.
If true, applies a secondary reranking model to initial search results for improved relevance.
REQUIRED and cannot be empty - must contain at least one filter condition. Available filter fields: user_id, agent_id, app_id, run_id, created_at, updated_at, categories, keywords. Filters can be provided in two formats: (1) Simple key-value pairs: `{"user_id": "alice"}` for equality matching or `{"created_at": {"gte": "2023-01-01T00:00:00Z"}}` with comparison operators. (2) Wrapped in logical operators: `{"AND": \[{"user_id": "alice"}\]}` for combining multiple conditions. Comparison operators (lowercase): `in` (matches any value in list), `gte` (>=), `lte` (<=), `gt` (>), `lt` (<), `ne` (not equal), `contains`, `icontains` (case-insensitive). Logical operators (`AND`, `OR`, `NOT`) must be UPPERCASE and take a list of conditions. Use `*` as wildcard to match any value for a field (e.g., `{"user_id": "*"}` to match all users).
Deprecated: Name of the organization to scope the memory search. Use `org_id` instead for improved accuracy and stability.
Minimum similarity threshold for search results (0.0 to 1.0). Higher values return more relevant but fewer results.
UUID of the project to scope the memory search; preferred over `project_name`.
Deprecated: Name of the project to scope the memory search. Use `project_id` instead for improved accuracy and stability.
Whether to search for memories based on keywords instead of semantic similarity.
Whether to strictly apply all provided metadata filters.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_UPDATE_MEMORY_BATCH_WITH_UUIDUpdates text for up to 1000 memories in a single batch, using their UUIDs.
Input parameters
The organization ID for the batch update operation. If not provided, defaults to the user's default organization.
List of memory update operations, each specifying a memory ID and its new text.
The project ID for the batch update operation. If not provided, defaults to the user's default project.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_UPDATE_MEMORY_DETAILS_BY_IDUpdates the text content of an existing memory, identified by its `memory_id`.
Input parameters
New text content to replace the memory's existing text. At least one of 'text' or 'metadata' should be provided.
Supplementary metadata to update for the memory. Can be used to add or modify key-value pairs associated with the memory.
The unique identifier of the memory whose text content is to be updated.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_UPDATE_ORGANIZATION_MEMBER_ROLEUpdates the role of an existing member to a new valid role within an existing organization.
Input parameters
New role to assign to the member. Valid values are 'OWNER' and 'READER' (must be uppercase).
Email address of the existing member or invitee whose role will be updated.
Identifier of the existing organization.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_UPDATE_PROJECTUpdates a project by `project_id` within an `org_id`, modifying only provided fields (name, description, custom_instructions, custom_categories); list fields are fully replaced (cleared by `\[\]`), other omitted/null fields remain unchanged.
Input parameters
New name for the project.
Organization's unique identifier.
Project's unique identifier to be updated.
New description for the project.
New list of custom category objects. Fully replaces existing categories; an empty list (`\[\]`) clears them.
Custom instructions to guide memory processing as a single string. Pass an empty string ('') to clear existing instructions. If you have multiple instructions, combine them into one string separated by periods or newlines.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MEM0_UPDATE_PROJECT_MEMBER_ROLEUpdates the role of a specific member within a designated project, ensuring the new role is valid and recognized by the system.
Input parameters
The new role to assign to the member within the project. Must be either 'OWNER' or 'READER'.
The email address of the member whose role is to be updated within the specified project.
Unique identifier of the organization where the project resides.
Unique identifier of the project where the member's role will be updated.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 57 agents privately built on Nagent that already use Mem0.
Build on Nagent
Connect Mem0 to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Mem0, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Mem0 is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Mem0 is connected, you configure its 47 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Mem0 steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Mem0 event fires, the agent kicks off automatically.
Every Mem0 action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Mem0 ships with 47 pre-built artificial intelligence actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Mem0 together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Mem0-based workflows tailored to your business.