Overview
The Record node represents a single row in a database. Each record contains field values corresponding to the database’s field definitions, and can optionally have a rich text document attached.Attributes Schema
Must be
'record'ID of the parent database node
ID of the database this record belongs to (same as parentId)
The name/title of the record (displayed in the Name column)
Optional avatar URL or emoji for the record
Map of field IDs to their values in this record. Field IDs must match the database’s field definitions.
Field Value Schema
/home/daytona/workspace/source/packages/core/src/registry/nodes/field-value.ts:40-46
Permissions
canCreate
Rules:- Tree must not be empty (cannot create at root)
- User must have at least
'member'role in the parent database
/home/daytona/workspace/source/packages/core/src/registry/nodes/record.ts:24-39
canUpdateAttributes
Rules:- Tree must not be empty
- User must have at least
'member'role
/home/daytona/workspace/source/packages/core/src/registry/nodes/record.ts:40-55
canUpdateDocument
Rules:- Tree must not be empty
- User must have at least
'member'role
/home/daytona/workspace/source/packages/core/src/registry/nodes/record.ts:56-71
canDelete
Rules:- Tree must not be empty
- User must have at least
'member'role
/home/daytona/workspace/source/packages/core/src/registry/nodes/record.ts:72-87
canReact
Rules:- Always returns
false(records cannot be reacted to)
Document Schema
Records use therichTextContentSchema for their optional document content, allowing rich text notes to be attached to each record.
/home/daytona/workspace/source/packages/core/src/registry/documents/rich-text.ts
Text Extraction
/home/daytona/workspace/source/packages/core/src/registry/nodes/record.ts:91-107
Mentions
Records do not extract mentions from attributes. Always returns[].