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.
Nesso is the engine between an external system and EspoCRM. You choose the channel, the sheet and the mapping. The passage uses only Espo's API. It is not a second CRM and it does not have an ERP's name written in the code.
Outside
Espo
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.
They are not characters. They are the people who, in a company with Espo and an ERP, have to say yes. The site does not promise they will switch it on alone on Monday.
Wants one number: today's accounts are in sync, and the balance of the totals if there is an amount. It is a check. It does not write.
Wrote a note yesterday. The field belongs to Espo: tonight's file does not clear it. The sheet shows who wrote last.
A bad file must not close customers in silence. There is the preview, a VAT number already present, and undoing the run.
Four steps, a recipe to review, a switch-on plan, a handover page without passwords. Then they can leave.
That is the default, and it is on purpose. A field can have another owner: Espo. Then the run does not touch it. Without that distinction, "sync" means deleting a person's work.
The physical channel. Webhook, database, file, or outbound HTTP. One connection can have several integrations.
Account, Contact, Lead, or a sheet Espo already has in the metadata. If it is missing, you create it: the technical name takes the prefix C.
Which column lands in which field, and who owns it. The synonym proposal does not save. The model, without an address, does not start.
By hand, every 5 minutes, every 15, every hour, or at a fixed time. The same integration does not start twice.
A site that calls, a night file, a SELECT, a PDF whose name contains the company key: they are the same shape. The account, contact and site recipes prepare a mapping to review. They are not a certified ERP connector.
The channels, one by one →Key, hash, POST or PUT. A second identical send does not call Espo again.
The source, even empty. Or Espo, and the run does not touch it.
Not a fixed list. If Product is missing, the price list stays empty.
Preview, read mode, the switch. The first close is confirmed.
And what the product refuses to be.
Synonyms call nobody. Without an address, the model does not start.
Accounts, contacts, sites, price list. Not a certified connector.
Owner, sales, finance, the person who installs.
SQL, portal, passwords, queue, trial. No brochure.
Espo on one side. Closing is not deleting. The source wins, unless an exception says otherwise.
And not a query on Espo's tables, and not a second product.
Empty Espo. No production dump. No form that asks for an email.
It starts an empty Espo. The Gruppo Meridia demo shows a run. It is not your company, and production dumps are not imported.
Nesso is not a certified connector. The manual lives in the repository, in Italian and in English.
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