Add member to project
Adds an existing user to a project (identified by `project_id` within organization `org_id`), assigning a valid system role.
Mem0 is an universal, self-improving memory layer for LLM applications.
Adds an existing user to a project (identified by `project_id` within organization `org_id`), assigning a valid system role.
Adds memory records from messages, optionally inferring structured content. Requires an agent, user, app, or run ID; processing defaults to asynchronous and can be requested synchronously.
Adds a new member, who must be a registered user, to an organization, assigning them a specific role.
Creates a new agent with a unique agent ID and a required name; additional metadata may be assigned by the system.
Creates a new agent run in the mem0.ai system.
Creates a new application with an application ID and name; ensure the app ID is unique to avoid potential errors or unintended updates.
Creates a new organization entry using the provided name and returns its details.
Creates a new user with the specified unique user ID and optional metadata.
Lists or searches existing memory entries using required nonempty filters and optional pagination. Despite its name, this action retrieves memories rather than creating them.
Creates a new project with a given name within an organization that must already exist.
Creates 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.
Permanently deletes an existing organization identified by its unique ID.
Call to permanently and irreversibly hard-delete an existing entity (user, agent, app, or run) and all its associated data, using its type and ID.
Deletes 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.
Deletes a batch of up to 1000 existing memories, identified by their UUIDs, in a single API call.
Permanently deletes a specific memory by its unique ID; ensure the `memory_id` exists as this operation is irreversible.
Permanently 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.
Removes an existing member, specified by email address, from a project, immediately revoking their project-specific access; the user is not removed from the organization.
Deletes 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.
Creates a memory export job requiring organization and project IDs and at least one user, agent, app or run filter. Returns a job ID and confirmation message; uses a default memory schema if none is specified.
Fetches comprehensive details for an organization using its `org_id`; the `org_id` must be valid and for an existing organization.
Fetches detailed information for an existing entity (user, agent, app, or run) identified by its type and unique ID.
Retrieves 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.
Retrieves entity filters from the entity filters endpoint, with a response modeled as a list of entities.
Retrieves memories associated with a specified user, agent, app, or run by entity type and ID, with optional pagination.
Retrieves 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.
Fetches a list of members for a specified, existing organization.
Fetches comprehensive details for a specified project within an organization.
Retrieves all members for a specified project within an organization.
Retrieves all webhooks configured for a specific project. Use this to list webhook configurations including their event types, URLs, and active status.
Retrieves all projects for a given organization `org_id` to which the caller has access.
Retrieves 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.
Retrieves entities with optional organization and project filters; results may be summaries and subject to limits. Organization and project IDs must be supplied together and are preferred over deprecated name filters.
Retrieves a list of organizations with their details, including IDs, names, ownership, members and plan information.
Searches memories using a natural language query and optional filters, or requests metadata-only search. At least one user, agent, or run ID and a query string are required; the query may be blank for metadata-only search.
Removes a member from an organization using the organization ID and member's email address.
Retrieves a paginated list of events for the authenticated user in a read-only operation.
Retrieves memory events from the Mem0 platform, providing interaction history and context for AI assistants. The response can include pagination information.
Retrieves a complete memory entry by its unique identifier; `memory_id` must be valid and for an existing memory.
Retrieves the version history of a Mem0 memory by its ID, allowing you to inspect its evolution and audit changes.
Retrieves a paginated list of memories filtered by IDs, metadata, keywords, dates, and other criteria. At least one of agent_id, user_id, app_id, or run_id is required; org_id and project_id must be supplied together or both omitted.
Searches memories using a required nonempty set of structured filters and an optional natural language query, which defaults to '*'. Supports reranking, field selection, similarity thresholds, and keyword search.
Updates text for up to 1000 memories in a single batch, using their UUIDs.
Updates the text and/or metadata of an existing memory identified by its memory ID.
Updates the role of an existing member to a new valid role within an existing organization.
Updates a project within an organization using the provided name, description, custom instructions, or custom categories. Category objects are submitted without their input fields; an empty category list can be sent to clear them.
Updates the role of a specific member within a designated project, ensuring the new role is valid and recognized by the system.
The Mem0 integration connects your Dench AI CRM directly to Mem0, so agents can read and act on your Mem0 data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
47 actions are available for agents to invoke on your behalf. Every call runs through Mem0's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Mem0 and click Connect — you'll authorize access through Mem0's own sign-in flow. No API keys or code required.
Ask an agent to use Mem0 in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Mem0 integration connects your AI CRM to Mem0, so AI agents can work with your Mem0 data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Mem0 integration currently exposes 47 actions, including Add member to project, Add new memory records, Add organization member, Create a new agent, Create a new agent run, and Create a new application. Agents invoke them on your behalf from chat or from automations.
No. You connect Mem0 from your Dench workspace using Mem0's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Mem0's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Mem0 connection from your workspace settings at any time.