Setup
1
Install the community node
Settings → Community Nodes → Install, then enter:
2
Add the credential
Create an Opper API credential:
The credential test validates connectivity through Opper’s OpenAI-compatible
GET /models endpoint.3
Use it in a workflow
Add an AI Agent node (or Basic LLM Chain, or anything else that accepts a language-model connection) and attach Opper Chat Model as its model sub-node.
Choosing a model
The Opper Chat Model node lists the catalog fetched with your credential, filtered by your model access rules. Agent nodes need tool calling — pick a model the catalog marks with thetools capability.
Attributing usage per workflow
n8n instances usually run many workflows against one credential. Tag the traffic so you can tell them apart in Opper analytics — see Tags and usage attribution.Troubleshooting
The node doesn't appear after installing
The node doesn't appear after installing
n8n loads community nodes at startup. Restart the instance after installing.
Community nodes are disabled
Community nodes are disabled
Self-hosted n8n gates community nodes behind an environment flag, and some managed plans don’t allow them at all. Check your instance settings.
The credential test fails
The credential test fails
It calls
GET /models. A failure usually means the key is wrong, or the base URL has an extra path segment — it should be exactly https://api.opper.ai/v3/compat.Related
Tags and usage attribution
Split usage per workflow or tenant.
All integrations
Every app that runs on Opper.