Add member to project
Adds an existing user to a project (identified by `project_id` within organization `org_id`), assigning a valid system role.
ActionTry it
Integrate Mem0
with your AI CRM
Mem0 is an universal, self-improving memory layer for LLM applications.
Explore Triggers and Actions
Add new memory records
Stores new memory records from a list of messages, optionally inferring structured content; requires association via `agent_id`, `user_id`, `app_id`, or `run_id`.
ActionTry it
Add organization member
Adds a new member, who must be a registered user, to an organization, assigning them a specific role.
ActionTry it
Create a new agent
Creates a new agent with a unique `agent_id` and an optional `name`; additional metadata may be assigned by the system.
ActionTry it
Create a new agent run
Creates a new agent run in the mem0.ai system.
ActionTry it
Create a new application
Creates 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.
ActionTry it
Create a new organization entry
Creates a new organization entry using the provided name and returns its details.
ActionTry it
Create a new user
Creates a new user with the specified unique `user_id` and supports associating `metadata` (not part of the request schema fields).
ActionTry it
Create memory entry
Lists/searches existing memory entries with filtering and pagination; critically, this action retrieves memories and does *not* create new ones, despite its name.
ActionTry it
Create project
Creates a new project with a given name within an organization that must already exist.
ActionTry it
Create webhook
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.
ActionTry it
Delete an organization
Permanently deletes an existing organization identified by its unique ID.
ActionTry it
Delete entity by type and 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.
ActionTry it
Delete memories
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.
ActionTry it
Delete memory batch with uuids
Deletes a batch of up to 1000 existing memories, identified by their UUIDs, in a single API call.
ActionTry it
Delete memory by id
Permanently deletes a specific memory by its unique ID; ensure the `memory_id` exists as this operation is irreversible.
ActionTry it
Delete project
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.
ActionTry it
Delete project member
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.
ActionTry it
Delete webhook
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.
ActionTry it
Export data based on filters
Creates 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.
ActionTry it
Fetch details of a specific organization
Fetches comprehensive details for an organization using its `org_id`; the `org_id` must be valid and for an existing organization.
ActionTry it
Get entity by id
Fetches detailed information for an existing entity (user, agent, app, or run) identified by its type and unique ID.
ActionTry it
Get event status by event 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.
ActionTry it
Get list of entity filters
Retrieves predefined filter definitions for entities (e.g., by type, creation/modification date); returns definitions only, not filtered entity data.
ActionTry it
Get memories by entity
Tool 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.
ActionTry it
Get memory export
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.
ActionTry it
Get organization members
Fetches a list of members for a specified, existing organization.
ActionTry it
Get project details
Fetches comprehensive details for a specified project within an organization.
ActionTry it
Get project members
Retrieves all members for a specified project within an organization.
ActionTry it
Get project webhooks
Retrieves all webhooks configured for a specific project. Use this to list webhook configurations including their event types, URLs, and active status.
ActionTry it
Get projects
Retrieves all projects for a given organization `org_id` to which the caller has access.
ActionTry it
Get user memory stats
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.
ActionTry it
List entities
Retrieves 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.
ActionTry it
List organizations
Retrieves a summary list of organizations for administrative oversight; returns summary data (names, IDs), not exhaustive details, despite 'detailed' in the name.
ActionTry it
Perform semantic search on memories
Searches 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
ActionTry it
Remove a member from the organization
Removes a member, specified by their username, from an existing organization of which they are currently a member.
ActionTry it
Retrieve all events for the currently logged in user
Retrieves 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).
ActionTry it
Retrieve list of memory events
Retrieves 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.
ActionTry it
Retrieve memory by id
Retrieves a complete memory entry by its unique identifier; `memory_id` must be valid and for an existing memory.
ActionTry it
Retrieve memory history by id
Retrieves the complete version history for an existing memory, using its unique `memory_id`, to inspect its evolution or audit changes.
ActionTry it
Retrieve memory list
Retrieves 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.
ActionTry it
Search memories with filters
Semantically 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.
ActionTry it
Update memory batch with uuid
Updates text for up to 1000 memories in a single batch, using their UUIDs.
ActionTry it
Update memory text content
Updates the text content of an existing memory, identified by its `memory_id`.
ActionTry it
Update organization member role
Updates the role of an existing member to a new valid role within an existing organization.
ActionTry it
Update project
Updates 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.
ActionTry it
Update project member role
Updates the role of a specific member within a designated project, ensuring the new role is valid and recognized by the system.
ActionTry it
How the Mem0 integration works
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.
Set up Mem0 in Dench
- 1
Sign in to your Dench workspace and open Integrations.
- 2
Find Mem0 and click Connect — you'll authorize access through Mem0's own sign-in flow. No API keys or code required.
- 3
Ask an agent to use Mem0 in chat, or call it from an automation.
- 4
Manage or disconnect the connection any time from workspace settings.
Frequently asked questions
How does the Mem0 integration work with Dench?
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.
What actions can AI agents perform with Mem0 via Dench?
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.
Do I need to write code to connect Mem0 to Dench?
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.
Is the Mem0 integration secure?
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.