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.
Channels
A channel is a way to receive or send rows. The rule lives in the integration, not in the name of the system on the other side.
Espo on one side
Mail is not a Nesso channel.
Channels ยท an ERP's name is not in the code
The channels the engine already has are the ones on show. Write-back, the queue and the portal filter stay off until they are turned on. Mail, the Advanced Pack and Espo users do not pass through here.
Inbound: webhook, a SELECT on the external database, CSV, Excel, SFTP, FTPS, PDF, document. Outbound: HTTP, with the cursor. Direction follows the channel. An HTTP integration does not become a load.
The external database is read. Its tables are not written from here, until write-back is on, and even then only the named columns.
Write-back, retry queue, portal filter, secret seal: the code is there, the default switch is off. Turning them on is a choice of whoever installs, not a behavior of the trial.
The trial does not set NESSO_SECRET_KEY, does not turn the queue on, does not turn the portal on, does not turn write-back on.
CRM mail stays in Espo. The Advanced Pack is not rewritten. Espo users are not created from a master. There is no bridge without Espo on one side. A production dump is not imported.
The external system calls an address. The engine checks the token and sends the row to that connection's inbound integrations.
MySQL, MariaDB, Postgres, SQL Server or Oracle. The engine reads one SELECT. Without TLS, MySQL stays the connection it was.
A file in a folder. A semicolon is fine. If a required column is missing the file stays put. If the rows enter, the file moves to elaborati.
Espo is the source. The cursor moves only after the POSTs that succeeded. If the address is empty, the engine inbox keeps the rows.
The same columns as CSV. It is not a different channel: it is the same inbound, another sheet.
The file sits on a server, not in the local folder. After the read it moves to elaborati, and it is not read again.
The file name contains the company key. It becomes a document on the customer. Without the whole key, the file stays.
A document in an Espo folder, with a team if you name one. Folder and team are optional.
Writing back to the ERP stays off until you turn it on for that integration. Then it touches only the columns you named.
The queue is off. On, it applies to an inbound row with an external identity, not to outbound and not to the same run.
Nesso does not create portal users and does not change roles. The rule, if on, keeps another team's records out of outbound.
Without NESSO_SECRET_KEY the database password stays in clear text on the volume. With the variable, new saves are sealed.
STAYS OUT
NOT NESSO
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