n8n + Meridian
Wire Meridian into your n8n automation workflows using the HTTP Request node with a custom OpenAI-compatible base URL. No custom nodes required — just point, authenticate, and go.
Prerequisites
n8n instance
Self-hosted or n8n Cloud, any recent version.
Meridian API key
Generate one from your dashboard.
HTTP Request node
Built into n8n — no extra installs.
Set your API key as an environment variable
In your n8n instance, add a credential or set an env variable so the key stays out of your workflow JSON.
MERIDIAN_API_KEY=sk-mer-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Configure the HTTP Request node
Add an HTTP Request node to your workflow. Set the method to POST and use the Meridian base URL below. The API is fully OpenAI-compatible.
https://api.getnimbus.net/v1
Paste the node parameters
In the HTTP Request node, switch to the Parameters tab and paste this JSON. Adjust the model field to meridian-pro, meridian-fast, or meridian-vision as needed.
{
"method": "POST",
"url": "={{$node["Meridian"].parameter.baseUrl}}/chat/completions",
"body": {
"model": "meridian-pro",
"messages": [{{ $json.messages }}],
"temperature": 0.7
}
}Add authentication headers
In the Headers section of the HTTP Request node, add:
| Name | Value |
|---|---|
| Authorization | Bearer {{ $env.MERIDIAN_API_KEY }} |
| Content-Type | application/json |
Example: Slack → Meridian → Slack
- 1.Slack Trigger — fires on new channel message.
- 2.HTTP Request (Meridian) — sends the message text to /chat/completions.
- 3.Slack Respond — posts the AI reply back to the thread.
Need an API key or want to explore rate limits and model capabilities?