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

Disclaimer

A mapping to review. Not a certificate.

The recipes do not certify the system on the other side. That system's name is not in the code. Espo stays the CRM.

Espo on one side

This site does not write to Espo.
The limits

What it is

Nesso is an engine that moves records between a channel and EspoCRM, through Espo's HTTP API. The code is in the public repository github.com/nessocrm/nessocrm. This site tells that. It is not the program.

The demo described in the manual is the proof of a run. It is not a customer published here and it is not a second product.

What it is not

It is not a certified connector. It is not tax, accounting, or legal advice. It does not replace the ERP and it does not replace whoever checks a VAT number. It does not create Espo users from a master.

Write-back, the retry queue, the portal filter, and the secret seal stay off until whoever installs turns them on. Without the NESSO_SECRET_KEY variable the password in the engine volume stays cleartext.

What does not go into the trial

The trial Espo stays empty. Production dumps are not imported, attachments are not copied, the backup is not mounted. The Advanced Pack is not in the repository.

Closing a disappeared record is not a deletion and it is not a forget. The first close asks for confirmation in the program, not on this site.