Overview

The iVendNext Node for n8n opens two distinct capabilities beyond basic data transfer: it enables complex multi-step automation patterns that combine real-time event reactions with scheduled batch jobs, and it makes iVendNext data available to AI agents that can answer plain-language questions about your business. Together, these capabilities let retailers build automations that range from simple one-step notifications to full end-to-end process orchestration — all without writing code.

This article covers the practical automation patterns that matter most in retail, how iVendNext data feeds AI agents, how execution is logged, and how to approach the connection between real-time and scheduled operations.

Real-Time vs. Scheduled Automations

The two nodes in the iVendNext connector serve different temporal patterns, and most mature retail automations combine them.

Real-time automations use the Trigger Node. They react to events the moment they occur — a new order, a submitted invoice, a stock change. The reaction happens within seconds of the event. Real-time automations are appropriate for anything where delay reduces value: order confirmations, carrier notifications, low-stock alerts, customer communications.

Scheduled automations use a Schedule Trigger (an n8n built-in trigger) combined with the iVendNext Action Node. They run at defined intervals — hourly, daily, weekly — and use Get Many to read a set of records, then process or export them. Scheduled automations are appropriate for bulk jobs: stock level synchronisation with an online store, daily export of sales figures to an accounting platform, weekly customer segment refresh.

Combined automations use both patterns in the same system. A real-time Trigger on Sales Order / On Submit handles the immediate post-sale flow — carrier notification, customer email, CRM update — while a separate scheduled automation runs every night to reconcile stock levels across all channels. Each automation handles the type of work it is designed for, and together they cover the full operational picture.

Common Retail Automation Patterns

E-commerce Synchronisation

An online store and iVendNext must stay in step: items, prices, and stock flowing outward to the store; orders and new customers flowing back into iVendNext. This is typically four sub-flows:

• Item sync: a Trigger on Item / After Insert and On Update pushes product changes to the store's product API.

• Price sync: a Trigger on Item Price / After Save pushes price changes to the store.

• Stock sync: a Schedule Trigger running every 10–30 minutes uses Get Many on the stock balance DocType and pushes quantities to the store's inventory endpoint.

• Order and customer ingest: the store's webhook delivers new orders and new customers to n8n, which maps the fields and uses Action Node Create operations to write Sales Orders and Customer records into iVendNext.

The result is that iVendNext remains the single source of truth for product, price, and stock, while the store operates as a sales channel that stays in sync automatically.

Shipping Automation

When a Sales Order is submitted in iVendNext, a Trigger / On Submit fires the workflow. An Action Node Get fetches the full customer record for the shipping address. The workflow maps the order and customer data into the carrier's payload format, posts it to the carrier API via an HTTP Request node, receives the tracking number back, and writes it onto the Sales Order using an Action Node Update. An email node then sends the customer their tracking link.

This entire sequence — from order submission to customer notification — happens without any manual steps and typically completes in under 30 seconds.

Operational Alerts

A Schedule Trigger running at regular intervals uses Action Node Get Many to check for conditions that warrant attention: stock below a threshold, high-value orders awaiting action, overdue invoices, or documents sitting in a particular status past a deadline. When matching records are found, a Slack or email node sends the relevant details to the appropriate person. These automations effectively give operations managers a live pulse on the things they would otherwise have to remember to check manually.

Handling Line Items and Complex Documents

Retail transactions involve line items — orders, invoices, and purchase orders all have item tables with multiple rows. The iVendNext Node handles these through the Meta Fields section on the Action Node.

When creating a Sales Order from an external source (a web order, for example), the items table is passed as an array via a Meta Field expression:

={{ $json.line_items.map(li => ({

     item_code: li.sku,

     qty:       li.qty,

     rate:      li.price

   })) }}

n8n expressions can map, reshape, and transform the data from any earlier step in the workflow into the exact array format iVendNext expects. This means a web order arriving in one format can be translated into a properly structured Sales Order in iVendNext without any intermediate database or manual intervention.