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 model
Without an address, no call starts. With the address, the model does not see passwords and does not enter the export.
Espo on one side
A mapping is confirmed. It is not delegated.
The synonym proposal is in the engine and does not go out on the network. The model, if an address is set, fills only the columns that are still empty and does not save. This is not a vendor's model list.
Propose the mapping reads the column names, in the language of the page, and proposes the Espo field, including the VAT number if the sheet has a fiscal field. An unrecognized column stays empty, to be filled by hand.
Synonyms are a list per language. They do not go on the network. They do not save the integration. A person reviews, then saves.
Fill the empty columns calls a model only if the address is set. It fills columns that are still empty, among the fields the sheet knows. It does not touch a column already mapped. It does not save.
The call sends the column names, at most three short cells, and the field name. It does not send the connection password. The model address does not enter the configuration export.
It is not an assistant that creates sheets, it does not choose the channel, it does not turn write-back on. If the address is missing, the button says so and the synonym proposal remains.
A run journal and the scheduler stay in the language of the run. The model does not rewrite them.
It reads the column names, in Italian or in English, and proposes the Espo field. An unknown column stays empty. It does not save until a person confirms.
The list is per language. It is not a model. If the column name is already a known synonym, the proposal comes from there.
"Fill the empty columns" calls a model only if the address is set. It fills columns that are still empty. It does not save. Without an address, no call starts.
Neither the synonyms nor the model write the integration. The mapping is reviewed, and then it is saved.
The call, if it starts, sends column names and a few cells. It does not send the connection password. The model address does not enter the configuration export.
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