Three Demo Workflows
Three complete, demo-ready scenarios. Each lists the goal, the nodes, the configuration, and the talk track.
11.1 — Magento 2 ↔ iVendNext: full commerce sync
Goal: keep an online store and iVendNext perfectly in step — items, prices, stock and customers — and pull web orders into iVendNext as the system of record. iVendNext is the master for product, price and stock; the webstore is the sales channel; orders and new shoppers flow back into iVendNext.
The four sub-flows
| Sub-flow | Direction | How it is built |
|---|---|---|
| Item Master | iVendNext → Store | iVendNext Trigger on Item (After Insert / On Update) → format → HTTP Request to the store's product API to create/update the product. |
| Pricing | iVendNext → Store | iVendNext Trigger on Item Price → map to the store's price field → HTTP Request to update price. |
| Stock Levels | iVendNext → Store | Schedule Trigger (e.g. every 10 min) → iVendNext Get Many on the stock balance DocType → HTTP Request to update store inventory. |
| Customer Master | Store → iVendNext | Store sends new-customer webhook → iVendNext Create on Customer. |
| Orders | Store → iVendNext | Store sends new-order webhook → map line items → iVendNext Create on Sales Order. |
Build it — Orders sub-flow (the headline)
Webhook node — receives the new order from the store. Copy its URL into the store's webhook settings.
(Optional) Get / Create Customer — iVendNext Get on Customer by email; if not found, iVendNext Create a new one. Ensures every order has a valid customer.
Map line items — a Set/Edit Fields node builds the order lines: for each product, item_code, qty, rate.
iVendNext Create — DocType Sales Order; map customer, transaction_date, delivery_date, and the items table from step 3 (via a Meta Field expression for the line-item array).
Respond / notify — send the new iVendNext order number back, and post a Slack confirmation.
Sales Order — items mapping (Meta Field value, n8n expression)
={{ $json.line_items.map(li => ({
item_code: li.sku,
qty: li.qty,
rate: li.price
})) }}
Build it — Stock sub-flow
Schedule Trigger — every 10 minutes.
iVendNext Get Many — stock balance DocType; Return All on; Field Names: item code, warehouse, actual qty.
HTTP Request — push each item's quantity to the store's inventory endpoint.
Demo line
"Change the stock of one product in iVendNext, wait for the next sync, and watch the website update — no one touched the website."
Talk track
"iVendNext" is the single source of truth. Products, prices and stock are published outward; orders and customers flow back in. Your team manages one system — the rest stays in sync by itself."
⬇ Download workflow JSON — 01-iVendNext-Magento2-Integration.json
11.2 — AI Agent answers questions from live iVendNext data
Goal: let a non-technical user ask plain-English questions and get answers drawn from real iVendNext data — because the iVendNext Node can be attached to an AI Agent as a tool.
The workflow
| Node | Role |
|---|---|
| Chat Trigger | Provides a chat box for the user's question. |
| AI Agent | The brain. Interprets the question and decides what data it needs. |
| Chat Model (e.g. Claude) | Powers the agent's reasoning and natural-language replies. |
| iVendNext node (as Tool) | Attached to the agent. The agent calls it to read live data — list items, get orders, query customers. |
Build it
Add a Chat Trigger.
Add an AI Agent node and connect a Chat Model credential.
On the agent, add a Tool and choose the iVendNext node. (It advertises itself as an AI tool automatically.)
Give the agent a system instruction: "You are Acme's retail data assistant. Use the iVendNext tool to look up items, stock, orders and customers. Answer concisely."
Activate and open the chat.
Sample questions to ask on stage
"What were Acme's top 3 selling items yesterday?"
"Is product SKU-1042 in stock, and where?"
"How many orders over £500 did we take today?"
"Give me the contact details for the customer on order SAL-ORD-2026-00148."
Demo line
"No dashboards, no reports to configure. They just ask — and the agent reads the live answer straight from iVendNext."
Why it lands
This reframes iVendNext as AI-ready today. It's the segment prospects talk about after the meeting.
⬇ Download workflow JSON — 02-iVendNext-AI-Agent.json
11.3 — Vibe-code a ShipStation integration with Claude Code + the n8n MCP server
Goal: show that even building a brand-new integration is now effortless — describe it in English and have an AI coding assistant assemble the workflow for you. Here we connect iVendNext shipments to ShipStation.
How the pieces fit
| Piece | Role |
|---|---|
| n8n MCP server | Exposes n8n's building blocks to AI coding assistants over the Model Context Protocol, so the assistant can create and edit workflows. |
| Claude Code | The AI coding assistant. Connected to the MCP server, it builds the workflow from your instructions. |
| iVendNext node | Reads the order/shipment to fulfil. |
| ShipStation | The shipping carrier platform that creates the label and returns tracking. |
Build it
Connect Claude Code to the n8n MCP server (point it at your n8n instance per the MCP setup).
Give Claude Code a single, plain-English brief (below).
Let it assemble the workflow; review the canvas it produces.
Plug in your iVendNext API and ShipStation credentials.
Test with one order, then activate.
Paste the full brief below into Claude Code once it is connected to your n8n instance via the n8n MCP server. It is deliberately detailed — it tells the assistant exactly which iVendNext nodes to use, the ShipStation calls to make, the field mapping, the error handling, and how to finish — so the result is production-shaped, not a toy.
The prompt to give Claude Code
ROLE
You are an n8n automation engineer. You are connected to my n8n instance through
the n8n MCP server, so you can list available nodes, create the workflow, set node
parameters and connections, validate it, and save it. Use the MCP tools — do not
hand me raw JSON to paste.
GOAL
Build a production-ready n8n workflow named "iVendNext -> ShipStation — Auto
Fulfilment" that automatically creates a shipment in ShipStation whenever a Sales
Order is submitted in iVendNext, writes the tracking number back onto that order,
and emails the customer their tracking link. iVendNext is the system of record.
KEY FACTS YOU NEED
- iVendNext is reached through two community nodes installed on this instance:
* Trigger node type: @ivendnext/n8n-nodes-ivendnext.iVendNextTrigger
* Action node type: @ivendnext/n8n-nodes-ivendnext.iVendNext
The action node uses: Resource = "document", an Operation (create / get / getAll
/ update / delete), and a "docType" (the Document Type, e.g. "Sales Order",
"Customer"). To set field values on create/update, use the node's "Meta Fields"
(a Field Name -> Value list). To fetch/update one record, set the document name in
"fallbackDocumentName".
- Both iVendNext nodes use the saved credential named
"iVendNext - acme.ivendnext.com" (credential type iVendNextApi).
- ShipStation V1 REST API, base URL https://ssapi.shipstation.com, HTTP Basic Auth
with API Key (username) and API Secret (password). Use an HTTP Request node with a
saved "HTTP Basic Auth" credential named "ShipStation API".
BUILD THESE STEPS, IN ORDER
- Trigger — node type @ivendnext/n8n-nodes-ivendnext.iVendNextTrigger.
* docType: "Sales Order"
* event: ["on_submit"]
* triggerName: "ShipStation Auto Fulfilment"
* Additional Options -> Respond Immediately: true
Output: the submitted Sales Order document.
- Get the customer — iVendNext action node, Operation "get", docType "Customer",
fallbackDocumentName = the order's customer field
(={{ $json.customer }}). This gives the shipping name, email and address.
- Build the ShipStation order payload — a Set node (raw/JSON mode) that maps:
* orderNumber = the Sales Order name
* orderDate = the order's transaction_date
* orderStatus = "awaiting_shipment"
* customerEmail = customer email_id
* billTo / shipTo = customer name + address fields
* items[] = map the Sales Order items: sku=item_code,
name=item_name, quantity=qty, unitPrice=rate
* weight = total order weight if available, else a sensible default
Use safe fallbacks for any missing address fields.
- Create the ShipStation order — HTTP Request node:
POST https://ssapi.shipstation.com/orders/createorder
Auth: ShipStation API (Basic). Body = JSON from step 3.
Capture the returned orderId.
- Create the shipping label to obtain tracking — HTTP Request node:
POST https://ssapi.shipstation.com/orders/createlabelfororder
Body includes the orderId from step 4, plus carrierCode, serviceCode and
packageCode (use sensible demo defaults and note that these are configurable).
Capture trackingNumber and labelData.
- Write tracking back to iVendNext — iVendNext action node, Operation "update",
docType "Sales Order", fallbackDocumentName = the order name. In Meta Fields set:
* a tracking field (e.g. "tracking_no") = trackingNumber
* optionally a status field marking it as shipped
(If unsure of the exact field name, use "tracking_no" and note that I must
confirm the field on my tenant.)
- Email the customer — Email/Gmail/SMTP node (whichever is available):
To = customer email, Subject = "Your Acme order {{orderNumber}} has shipped",
Body includes the tracking number and a tracking URL.
ERROR HANDLING (IMPORTANT — do not let failures vanish silently)
On the ShipStation create-order and create-label nodes, enable retry-on-fail.
Add an error branch: if any step fails, route the item to a node that posts an
alert (Slack if available, otherwise a flag) including the order number and the
error message, so a human can act. A failed shipment must be flagged, never lost.
- Use "Continue On Fail" where appropriate so one bad order does not stop the queue.
FINISH
Lay the nodes out left-to-right with clear names.
Add a sticky note summarising the flow, the two credentials, and the ShipStation
carrier/service defaults I need to confirm.
Validate the workflow with the MCP validation tool and fix any issues.
Save it (leave it deactivated) and summarise what you built, which credentials it
expects, and exactly which placeholder values I must confirm before going live.
Credentials to set up first: iVendNext - acme.ivendnext.com (iVendNext API), ShipStation API (HTTP Basic Auth), and an email credential. Confirm before going live: the tracking field name on your tenant and your ShipStation carrier / service / package codes.
⬇ Download the Claude Code prompt — 03-ShipStation-ClaudeCode-Prompt.md
Demo line
"I described what I wanted in five sentences. The AI built the integration. This is the speed at which iVendNext customers can now move."
Demo safety
Have this workflow pre-built and tested. Live AI generation is impressive but unpredictable on stage — show the result instantly, and narrate the prompt that produced it.
**