Purpose

What the Action Node is for

The Action Node does something to iVendNext when the workflow tells it to. It is how a workflow reads data out of iVendNext or writes data into it. Think of it as your hands inside the system: fetch this order, create that customer, update this price, list those items, delete that draft.

When to use it: 

Any time a workflow needs to look something up in iVendNext or make a change to it — whether the workflow was started by a schedule, a button, another app, an AI agent, or the iVendNext Trigger.

5.1 — How it is organised

The node always asks three questions, top to bottom:

5.2 — The five operations

5.3 — Entering field values (Create & Update)

When you choose a Document Type, the node fetches that type's full field list from your tenant and shows it to you — required fields first, then optional ones. You simply fill in the boxes or map them from earlier steps in the workflow. The node automatically presents each field in the right format:

Behind-the-scenes housekeeping fields (created-on, modified-by, internal counters, and layout-only elements) are hidden automatically so you only see fields that matter.

Advanced: Meta Fields

For a less common Document Type, or a field you need to set that is not shown, expand Meta Fields and add a Field Name → Value pair. The Field Name must match the field's exact internal name in iVendNext. Values accept n8n expressions, so you can pass numbers, dates, or even nested line-item tables from earlier steps.

5.4 — Identifying a document (Get, Update, Delete)

These three operations act on one specific record, so they ask for the Document Name. You can type it, or — more commonly — map it from a previous step using an expression such as ={{ $json.customer }}.

5.5 — Get Many options

Get Many is the workhorse for reporting and bulk sync. Its options:

​

Worked example — "Today's orders over £500"

Operation : Get Many

DocType   : Sales Order

Return All: On

Filters   :

   • grand_total   EQUALS or GREATER   500

   • transaction_date   IS   ={{ $today }}

Field Names: name, customer, grand_total, status

5.6 — When something goes wrong

The node gives clear, plain-language errors. If an automation should keep going even when one record fails, switch on the node's Continue On Fail setting — failed items are passed along with an error note instead of stopping the whole run, so you can route them to a "needs attention" branch.