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

Decisions

Few, and they are not reopened for every file.

Nesso always has Espo on one side. The other system's name is not in the code. Mail stays in Espo.

Espo on one side

A closed decision is recognized because the default does not contradict it.
The decisions

Espo on one side

There is no run without Espo. The other side is a channel. The product does not become a generic bridge between any two systems.

The HTTP API is the only way to write on Espo. The tables are not an interface.

The source is the truth of its fields

By default an empty cell clears the field. It is annoying and it is correct. The exception is explicit: the field owner is Espo, and then the run does not touch that value.

Write-back stays off until someone turns it on, and even then only on the columns they named.

Close, do not delete

A disappeared row closes the record and keeps the history. The first close asks for confirmation. It is not a deletion and it is not a forget.

Users are not created from a master. The portal is not administered from here: the filter, off by default, does not create users and does not change roles.

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