Setup and Credentials
Prerequisites
Before setting up the iVendNext Node, you need:
An active iVendNext tenant with administrator access to create a user and generate API keys.
An n8n instance (Cloud or self-hosted) with community nodes enabled.
The ability to create credentials in n8n.
Step 1 — Install the Node
The iVendNext Node is published as an n8n Community Node and installs from inside n8n in under a minute.
In n8n, open Settings → Community Nodes.
Click Install a community node.
In the package name field, enter: @ivendnext/n8n-nodes-ivendnext
Tick the acknowledgement box and click Install.
Wait for the success message. The iVendNext and iVendNext Trigger nodes now appear when you search the node panel.
To verify the install: click + to add a node and type "iVendNext". If both nodes appear, installation succeeds.
n8n Cloud users: Community nodes can be enabled from the same Settings → Community Nodes screen. If the option is not visible, ask your n8n administrator to enable community nodes for the instance.
Step 2 — Create a Dedicated Integration User in iVendNext
Best practice is to create a dedicated user in iVendNext specifically for n8n automations, rather than using a staff account.
In iVendNext Desk, go to User and create a new user — for example, n8n Automation with an internal email address.
Assign only the roles the automations require. A stock-sync automation does not need access to financial documents; an order-ingest automation does not need access to settings. Keep the scope minimal.
Save the user.
A dedicated integration user keeps automations separate from staff accounts, makes access straightforward to audit, and allows the connection to be revoked independently by revoking that user's API keys without affecting any other user.
Step 3 — Generate API Keys in iVendNext
Sign in to iVendNext as the integration user you created.
Open the User profile and scroll to the API Access section.
Click Generate Keys.
Copy the API Key and API Secret shown on screen.
Important: The API Secret is displayed only once. Store it securely — for example in a password manager. If it is lost, return to this screen and generate new keys.
Step 4 — Create the Credential in n8n
In n8n, go to Credentials → Create New.
Search for and select iVendNext API.
Complete the following fields:
| Field | What to enter |
|---|---|
| API Key | The API Key copied from iVendNext |
| API Secret | The API Secret copied from iVendNext |
| Environment | Select the listed environment option |
| Domain | Your tenant address, including https:// and with no trailing slash — e.g. https://acme.ivendnext.com |
| Ignore SSL Issues | Leave off. Enable only for temporary test environments with self-signed certificates — never in production. |
- Click Save.
n8n performs an immediate verification check against your tenant. A green tick confirms the credential is valid and the connection is live. This credential is now available for use in any iVendNext node across all your workflows.
If the test fails: The most common causes are a mistyped API Key or Secret, a Domain field missing the https:// prefix, a Domain with a trailing slash, or the integration user lacking sufficient permission. See the Troubleshooting article for a full diagnosis table.
Reusing the Credential
You only create the iVendNext API credential once. Every iVendNext Action Node and Trigger Node in every workflow uses the same credential — simply select it from the credential dropdown when configuring each node. If you need to connect to a second iVendNext tenant (for example, a staging environment), create a second credential for that tenant's domain and keys.
Revoking Access
To disconnect n8n from iVendNext at any time, sign in to iVendNext as the integration user and regenerate the API keys. The existing keys are immediately invalidated, and all n8n workflows using those keys will stop authenticating until the credential in n8n is updated with the new keys. This allows access to be revoked without deleting the n8n workflows themselves.