@varios-ai/n8n-nodes-varios-ai; the source code lives at github.com/varios-ai/n8n (MIT).
Requirements
- A current n8n installation. The node requires a minimum version and cannot be installed in older n8n versions; the version required is stated in the package description on npm.
- Permission to install community nodes in n8n. n8n Cloud restricts the installation of your own community nodes, so use a self-hosted instance there.
- An API key from VARIOS AI with the desired chat models or assistants assigned to it.
- The VARIOS AI instance must be reachable over HTTPS from the n8n server.
Every API key requires its own license. Include the license for the n8n integration in your planning.
Installation
1
Install the community node
In n8n, open Settings → Community nodes → Install and enter the package name:Accept the terms for community nodes and complete the installation. Afterwards the VARIOS AI node is available in the node search under AI → Language Models.
2
Create an API key in VARIOS AI
Under Administration → API keys, create a key for n8n, for example named “n8n”. Assign the chat models that should be usable in n8n to the key and set a cost limit. Copy the key immediately, it is shown only once.
3
Set up the credentials in n8n
In n8n, create credentials of type VARIOS AI API with these two values:
Replace
<PROJECT_DOMAIN> with the domain of your installation, i.e. the value of PROJECT_DOMAIN from the .env; the path /api/v1 stays unchanged. Example for the domain ki.example.com: https://ki.example.com/api/v1.Using Test, n8n checks the credentials against /models. The key is sent as a bearer token in the Authorization header on every request.4
Use the node in a workflow
Add the VARIOS AI node and select the credentials. Under Model, either choose From List – n8n then loads the models assigned to the key – or enter an ID manually via Name. Optionally, System Prompt holds a system message that is prepended to every conversation.Then connect the Model output to an AI Agent or another node that expects a language model. The node itself has no data input.
As an ID, the API accepts the chat model ID of a preconfigured model or an assistant ID. Only assistants and models assigned to the API key in use are available, see API keys.
