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

Journal

Four chapters. The same run.

These are not customer stories. They are the reasoning of decisions already in the engine. If a sentence here and a sentence in the manual diverge, the manual wins: it changes together with the code.

Espo on one side

Sheets on one side, four squares in the middle, a dark archive on the other.

Chapter 1

Espo on one side

Nesso always has Espo on one side and a channel on the other: the connection is the channel and the integration is the rule.

 Key, hash and cursor on the night accounts file.

Chapter 2

The key, the hash and the cursor

The key joins the integration id to the external value, the hash remembers the inbound row already seen, and the cursor remembers the last record that left.

 An empty city cell, and a note that stays on the record.

Chapter 3

The empty cell

At night an empty cell clears the field the source owns, and the note written on Espo stays.

 Four switches left off beside a sheet still to be read.

Chapter 4

What stays off

The fourth chapter names the brakes that exist, why the trial leaves them off, and what a person sees before the first write.

The manual is the docs folder of the repository github.com/nessocrm/nessocrm. This site does not rebuild it.

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