Connecting to iVendNext
Before a node can read or write data it needs to know which tenant to talk to and prove it is allowed to. This is done once with an iVendNext API credential, which you then reuse in every workflow.
4.1 — Generate your access keys in iVendNext
Sign in to your iVendNext tenant, e.g. https://acme.ivendnext.com.
Open your User profile and scroll to the API Access section.
Click Generate Keys.
Copy the API Key and the API Secret shown.
Copy the secret now The API Secret is displayed only once. Store it safely (e.g. in your password manager). If it is lost, simply generate keys again.
Best practice Create a dedicated integration user in iVendNext (for example n8n Automation) and grant it only the roles it needs. This keeps automations separate from real staff accounts and makes access easy to audit or revoke.
4.2 — Create the credential in n8n
In n8n choose Credentials → Create New → iVendNext API and complete the fields:
| Field | What to enter |
|---|---|
| API Key | The API Key you copied from iVendNext. |
| API Secret | The API Secret you 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. Only ever enable this for a temporary test environment with a self-signed certificate. |
4.3 — Test and save
Click Save. n8n immediately performs a secure sign-in check against your tenant. A green tick confirms the keys and address are correct and the connection is live. You can now use this credential in any iVendNext node.
If the test fails
The cause is almost always one of three things: a mistyped key or secret, a Domain missing the https:// prefix or carrying a trailing slash, or an integration user without permission. See Troubleshooting.