Research Workspace Records
Inspect object metadata before listing records.
/oo Twenty CRM: List Twenty metadata objects, then list objectNamePlural [object name] records with filter [filter] and summarize returned fields.
Discover workspace metadata objects, read filtered records, and create or update records using the tenant’s object schema. Ask your connected AI assistant to explain the results or carry out the specified operation.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Inspect object metadata before listing records.
/oo Twenty CRM: List Twenty metadata objects, then list objectNamePlural [object name] records with filter [filter] and summarize returned fields.
Read a UUID-selected record and apply explicit schema fields.
/oo Twenty CRM: Retrieve Twenty object [plural API name] record [UUID], then update data [specified fields and values].
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect with a Twenty workspace API key.
Connect Twenty CRM →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
Twenty CRM connects supported service operations to your AI assistant. Discover workspace metadata objects, read filtered records, and create or update records using the tenant’s object schema.
Read metadata objects and tenant record lists or details.
Create or update records using tenant-specific object payloads.
List Twenty metadata objects for the connected workspace.
twenty_crm.list_metadata_objects List Twenty records for one workspace object using the generated schema-per-tenant REST API.
twenty_crm.list_records Retrieve one Twenty record by object API name and record UUID.
twenty_crm.retrieve_record Create one Twenty record for a workspace object.
twenty_crm.create_record Update one Twenty record by object API name and record UUID.
twenty_crm.update_record Delete one Twenty record by object API name and record UUID.
twenty_crm.delete_record No matching tools.
No. The API schema is generated per tenant; read metadata first.
Use objectNamePlural, the plural API name from workspace metadata.
Provide the object API name and record UUID.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.