| Term | Meaning |
|---|---|
| iVendNext Node | The connector that links your iVendNext tenant to n8n. Installs as an Action node and a Trigger node. |
| n8n | A visual workflow automation tool. Workflows are built by joining nodes on a canvas. |
| Tenant | Your dedicated iVendNext environment, e.g. acme.ivendnext.com. |
| Document | Any single record in iVendNext — an order, a customer, an item. |
| Document Type (DocType) | The category a document belongs to — Sales Order, Customer, Item, etc. |
| Document Name | A document's unique identifier. |
| Action Node | Reads or changes iVendNext data on demand. |
| Trigger Node | Starts a workflow when an iVendNext event occurs. |
| Credential | The saved API key/secret + tenant address that lets nodes connect securely. |
| Execution | A single run of a workflow, fully logged. |
| AI Agent / Tool | An n8n node that exists in natural language; the iVendNext node can be attached to it as a data tool. |
| MCP server | A bridge that lets AI coding assistants build and edit n8n workflows for you. |
iVendNext Node for n8n — User Guide & Consultant Playbook · Example tenant acme.ivendnext.com © iVendNext. For internal use by iVendNext consultants, partners, and customers.
Last updated 1 month ago
Was this helpful?