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.
The project
The code is at github.com/nessocrm/nessocrm. The manual is the docs folder. This site tells the product and does not replace the manual.
Espo on one side
The contact is the repository.
The engine, the page, the tests, and the bilingual manual are in the repository. The site you are reading is the presentation. It does not rebuild the manual and it is not the place where a connection is configured.
The trial starts with an empty Espo. Production dumps are not imported. The Advanced Pack is not in the repository.
It is not a certified connector. The recipes are a mapping to review. There is no service price list, there is no contact form, there is no company to cite on this page.
The Gruppo Meridia demo, in the manual, is the proof of a run. It is not a second product and it is not a customer published here.
What is done and what is not done live in the first chapter of the manual, in the repository. If a sentence on this site and a sentence in the manual diverge, the manual wins: it is the text that changes together with the code.
The passage
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.
Not us
A file, a table, a call. That ERP’s name is not in the code. Nesso is not that system.
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.
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 trial is the public repository. It starts an empty Espo. It does not import a production dump.
How the trial works