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

The run

Every quarter of an hour, if you ask. Not on its own just to show movement.

On the home screen the accounts number counts only if today's run toward Account succeeded. Yesterday's success is not presented as today.

Espo on one side

The scheduler is not a quarter of an hour watched on the container.
How the cadence is proved

When it starts

The cadences are four intervals: off, 5 minutes, 15, 60. Plus a fixed time, for example 02:10. An integration on pause is skipped by the scheduler and by the webhook. Run now is not.

The fifteen minutes are proved with a fake clock: one second before, it does not start; at the deadline it starts once, and it does not start again in the same minute. It is not a quarter of an hour observed on the container.

Two runs, not only one

Two different integrations can run together. The same one does not start twice: the second is told a run is already in progress. If it is already in progress, the scheduler skips it and does not write an error every thirty seconds.

After an error the clock updates and the full interval is waited. Only with retry_failed on does the clock stay put, and the run can come back sooner.

What the home screen shows

The aligned-accounts percentage counts inbound integrations toward Account. If today's run fails, the percentage is not shown and yesterday's time is not passed off as today.

A file expected within an hour, if that hour passes without a successful run, turns the border red. A file already in the processed folder is not read again. A failed-run notice lights once, with the integration name.

The passage

Espo on one side. The external system on the other.

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.

01

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.

02

Nesso

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.

03

Espo

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 product boundary