The Trigger Node listens to iVendNext and starts a workflow the instant something happens. Where the Action Node waits to be told what to do, the Trigger Node is the doorbell — it fires the moment a sale is made, an order is submitted, a stock figure changes, or any other chosen event occurs.
Whenever you want an automation to react in real time to activity in iVendNext, rather than checking on a schedule. It is always the first node in such a workflow.
When you activate a workflow that begins with the Trigger Node, it quietly registers a private notification inside your iVendNext tenant. From then on, whenever the chosen event happens to the chosen Document Type, iVendNext instantly hands the document over to your workflow, which springs into action. Deactivate the workflow and — if you ask it to — the notification is cleanly removed.
When the event fires, the Trigger Node outputs the full document as data. The next node can read any field from it — for example ={{ $json.customer }} or ={{ $json.grand_total }} — and act on it.
Worked example
Set DocType to Sales Order, Event to After Insert, and name it New Sale → Slack. Activate the workflow. Now every new sale in iVendNext instantly pushes its details into the rest of your automation — no polling, no delay.