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

Who it is for

Four people. The same run.

The owner looks at one number. The salesperson keeps the note. Administration looks at the preview. Whoever installs hands over without leaving passwords on a page.

Espo on one side

A number on the home screen is not a dashboard.
The four people

Whoever keeps the number

On the home screen there is one number that counts: accounts aligned today, and the balance if there is an amount. It counts only if today's run toward Account succeeded. It is a check. It does not write.

If the run fails, the number is not shown with yesterday's time. An expected file that does not arrive turns the border on.

Whoever has the note

The salesperson writes on the record. The note field has Espo as owner, so the night file does not clear it. The badge says who wrote last.

If the file brings a different value, that value goes into a queue to look at. It does not overwrite the note.

Whoever checks

Administration opens the preview. They see a VAT number already present before the run writes. They can undo what the run wrote.

The first close of disappeared records asks for confirmation. A truncated file does not close the list on its own.

Whoever installs

Four steps: connection, sheet, mapping, run. The recipe is a starting point to review, not a certified connector. The switch-on plan says what stays off.

The handover page does not contain passwords. Without NESSO_SECRET_KEY the volume keeps them in cleartext: it has to be said to whoever receives the trial, not hidden.

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