Product How it works Channel, sheet, the record's run Architecture Espo on one side, the API on the other The model It proposes the mapping. It does not save. The run Cadence, and this morning's number Rules Owner, key, reject Sheets The ones Espo already has The field Who wins if the cell is empty The record How it enters and how it leaves What can go wrong Preview, read mode, the switch
Channels Channels File, table, call, outbound Recipes A mapping to review The trial The repository, an empty Espo
Nesso Why Nesso Not SQL, not a second CRM Who it is for Who has to trust the run Decisions The ones the code keeps The project The public repository
FAQ The trial
Italiano English

Sheets

A new sheet has the prefix C. Fields do not take a second one.

Account, Contact, Lead, Opportunity, Case, Task, Meeting, Call, Document are standard sheets. The key sits in cExternalKey.

Espo on one side

The price list looks at Product. If the sheet is missing, the fields stay empty.
The sheets

The ones Espo already has

The engine does not invent entity names. It reads the sheets this installation exposes. On a standard sheet the external key is the custom field cExternalKey.

Two integrations on the same sheet do not step on each other: the key contains the integration id. An accounts file and a sites file can both land on Account, with different keys.

The ones created here

If the sheet does not exist, Nesso creates it through the API. Singular and plural are given. Espo adds the prefix C. Fields on the new sheet do not receive a second prefix. The key is called externalKey.

A sheet created here is not a second CRM. It is an Espo sheet, visible to whoever has the team. The team and the assigned person come from a column or from a fixed team.

The ones that are not touched

Espo users are not created from a master. A column of people does not become a list of logins.

The recipe price list points at Product. If this installation does not have the sheet, the price-list fields stay empty and the recipe does not invent the catalog.

Sheets Espo already has

9 entries

Account Contact Lead Opportunity Case Task Meeting Call Document

When the page opens, the engine asks Espo for the list. It is not a fixed catalogue of fifty names. If the sheet is there, it can be mapped. Lead, Account and Contact are the common case, not the only one.

Sheets born here

2 entries

C… externalKey

The form asks for the singular and the plural. Espo assigns the technical name with the prefix C. Fields on that sheet do not get a second prefix. The key, on a sheet created here, is called externalKey.

What is not invented

2 entries

Product User

If Product is missing, the price-list recipe leaves the fields empty. Users are not born from a file. A sheet that is not in the metadata is not named just to show movement.

The passage

Espo on one side. The external system on the other.

Nesso stands in the middle. It reads the channel, applies the mapping, and writes through Espo’s API. It does not open the CRM tables.

01

The external system

Not us

A file, a table, a call. That ERP’s name is not in the code. Nesso is not that system.

02

Nesso

This is us

Channel, sheet, fields. If the write switch is off, it does not write. If the field belongs to Espo, it does not clear it.

03

Espo

The sheet

The record, if it is born, is born there. CRM mail stays in Espo. The Advanced Pack is not rewritten.

Nesso always has Espo on one side. It is not a bridge between any two systems.

The product boundary