Twenty
for LuumenAI

The #1 Open-Source CRM. Modern, powerful, affordable platform to manage your customer relationships.

Operate Twenty from the same conversation as the hosts it runs on. Check jobs, queues, and interfaces without a second console; run diagnostic reports; and restart or update with the change previewed, approved, and logged.

The Twenty toolbox

8 tools: 4 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet CRM RecordGet one company, person, opportunity, or task by its Twenty UUID, optionally including direct relations.
  • ReadList CRM FieldsList field definitions from the connected Twenty workspace to discover exact field names, types, editability, nullability, uniqueness, and relation targets for schema inspection and filters.
  • ReadList CRM ObjectsList standard and custom object definitions in the connected Twenty workspace for schema inspection.
  • ReadList CRM RecordsList companies, people, opportunities, or tasks with Twenty filter syntax, ordering, relation depth, and forward cursor pagination.
  • WriteBatch Create CRM RecordsCreate 1-60 records of one type. Approval by default
  • WriteCreate CRM RecordCreate one company, person, opportunity, or task using the supported standard fields in the parameter schema. Approval by default
  • WriteDelete CRM RecordPermanently delete one company, person, opportunity, or task by UUID. Approval by default
  • WriteUpdate CRM RecordPartially update one company, person, opportunity, or task by UUID using the supported standard fields in the parameter schema; only supplied fields change. Approval by default

Questions

How does LuumenAI connect to Twenty?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Twenty on its own?

Read actions answer immediately. Anything that writes — batch create crm records, create crm record, delete crm record, update crm record — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Twenty — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Twenty to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.