The iVendNext Trigger Node
What the Trigger Node is for
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.
When to use it:
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.
6.1 — How it works, in plain terms
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.
6.2 — Settings
| Setting | Meaning |
|---|---|
| DocType | The Document Type to watch — e.g. Sales Order or Item. Loaded live from your tenant. |
| Trigger Name | A friendly, unique label for this listener (e.g. New Web Order → ShipStation). It identifies the notification inside iVendNext. |
| Event | One or more moments to react to (see below). Pick exactly the events you care about. |
| Auto Delete | If on, the listener is removed from iVendNext when you deactivate the workflow. Leave off to keep it in place between edits. |
| Respond Immediately Additional Options | Acknowledge iVendNext the instant the event arrives (recommended) so the platform never waits on the workflow. |
6.3 — Events you can react to
| Event | Fires when… |
|---|---|
| After Insert | A new document is created (e.g. a new order). |
| After Save | A document is saved. |
| On Update | An existing document is changed. |
| On Submit | A document is submitted/confirmed (e.g. an invoice is finalised). |
| On Cancel | A submitted document is cancelled. |
| Value Changed | A watched field's value changes. |
| On Change / On Trash / Custom Method | Additional lifecycle moments for advanced scenarios. |
6.4 — What your workflow receives
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.