Connect Mem0 to Definable AI

Mem0 is an universal, self-improving memory layer for LLM applications.

About Mem0

Mem0 is a productivity tool. Connect it to Definable AI with one-click OAuth2 — no API keys or custom code required.

What you can automate with Mem0

Use Definable AI's agent platform to trigger workflows from Mem0, process results with 50+ AI models, and sync data across 900+ connected apps.

Tools & Actions (49 available)

  • Add member to project: Adds an existing user to a project (identified by `project_id` within organization `org_id`), assigning a valid system role.
  • 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`.
  • Add organization member: Adds a new member, who must be a registered user, to an organization, assigning them a specific role.
  • 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.
  • Create a new agent run: Creates a new agent run in the mem0.ai system.
  • 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.
  • Create a new organization entry: Creates a new organization entry using the provided name and returns its details.
  • 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).
  • Create an export job with schema: Initiates an asynchronous job to export memories, structured by a schema provided in the request body and allowing optional filters.
  • 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.
  • Create project: Creates a new project with a given name within an organization that must already exist.
  • 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.
  • Delete an organization: Permanently deletes an existing organization identified by its unique ID.
  • 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.
  • 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.
  • Delete memory batch with uuids: Deletes a batch of up to 1000 existing memories, identified by their UUIDs, in a single API call.
  • Delete memory by id: Permanently deletes a specific memory by its unique ID; ensure the `memory_id` exists as this operation is irreversible.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Get entity by id: Fetches detailed information for an existing entity (user, agent, app, or run) identified by its type and unique ID.
  • 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.
  • 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.
  • 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.
  • 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.
  • Get organization members: Fetches a list of members for a specified, existing organization.
  • Get project details: Fetches comprehensive details for a specified project within an organization.
  • Get project members: Retrieves all members for a specified project within an organization.
  • 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.
  • Get projects: Retrieves all projects for a given organization `org_id` to which the caller has access.
  • Get user memory stats: Retrieves a summary of the authenticated user's memory activity, including total memories created, search events, and add events.
  • 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.
  • List organizations: Retrieves a summary list of organizations for administrative oversight; returns summary data (names, IDs), not exhaustive details, despite 'detailed' in the name.
  • 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
  • Remove a member from the organization: Removes a member, specified by their username, from an existing organization of which they are currently a member.
  • 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).
  • Retrieve entity-specific memories: Retrieves all memories (e.g., user preferences, chat history) for a specific entity from the mem0 platform. You can specify the entity either by: 1. Using entity_type + entity_id (e.g., entity_type='user', entity_id='john') 2. Using the specific ID field directly (e.g., user_id='john', agent_id='bot1') At least one entity identifier is required.
  • 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.
  • Retrieve memory by id: Retrieves a complete memory entry by its unique identifier; `memory_id` must be valid and for an existing memory.
  • 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.
  • 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.
  • 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.
  • Update memory batch with uuid: Updates text for up to 1000 memories in a single batch, using their UUIDs.
  • Update memory text content: Updates the text content of an existing memory, identified by its `memory_id`.
  • Update organization member role: Updates the role of an existing member to a new valid role within an existing organization.
  • 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.
  • 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.

How to connect Mem0

  1. Sign in to Definable AI and go to Apps
  2. Search for Mem0 and click Connect
  3. Authorize via OAuth2 — takes under 30 seconds
  4. Use Mem0 actions in your AI agents and workflows