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

Terms

The pages tell. The code is in the repository.

There is no service contract on this site. There is no form. A certified connector is not promised.

Espo on one side

The license notice is read in the repository.
The repository

The pages

You can read these pages. They do not describe a service hosted here: there is no account, no fee, no form. The host is GitHub Pages.

The marks of EspoCRM and of the other named systems stay with their owners. Naming them is not a partnership and is not a certification.

The code

The program is in the repository github.com/nessocrm/nessocrm. The notice of what you may do with it is read there, in the repository, not in a formula repeated on this page.

The program is an integration engine. It is not advice. These pages do not warrant that a run against a production Espo suits your case. The intended trial is an empty Espo.

What is not transferred

No right is transferred to import production dumps, to publish the Advanced Pack, or to treat this site as support. Writes toward Espo, in the program, go through the API. This site does not write.

The recipes are a mapping to review. Turning on write-back, the queue, the portal, or the seal is a choice of whoever installs, off by default.