API setup · Check client requirements
n8n + Luma Cloud
Add Luma Cloud text generation to a workflow with an OpenAI Chat Model node.
Use your Luma Cloud API key, Base URL and an available model ID with the client-specific settings below. SuperGPT desktop installation and sign-in are separate.
Before you start
- Create a named key in Dashboard → API. Use API Wallet credit, or an eligible Builder subscription key.
- Copy an exact model ID from the catalog returned for this key. Replace MODEL_ID_FROM_CATALOG wherever it appears below.
- Use a separate named key for this app. Paste it only into the app's credential field; keep it out of chat prompts, screenshots, shared configuration and workflow exports.
- An n8n version whose OpenAI credential exposes Base URL, with permission to create a workflow and credentials.
Set up n8n
- Build a small manual workflow
Create a workflow with Manual Trigger connected to Basic LLM Chain. Add OpenAI Chat Model to the chain's Model connector.
- Create a separate credential
In the model node, create an OpenAI credential named Luma Cloud. Enter your Luma key, set Base URL to https://api.lumaos.cloud/v1, leave Organization ID blank, and save.
- Select the model
Choose the Luma Cloud credential and the exact model ID from your catalog. If your version offers manual model entry, use it when discovery cannot select that ID. Keep Use Responses API off for this guide.
- Enter a fixed prompt
In Basic LLM Chain, set Prompt to Define below. Set Prompt (User Message) to “Reply with hello.” Leave Require Specific Output Format off for this first text reply.
- Run and inspect the result
Click Execute Workflow and inspect the Basic LLM Chain output. Keep this test manual; configure bounded retries and review usage before adding a schedule.
- Use HTTP Request if the model node is incompatible
Create Manual Trigger → HTTP Request. Set Method to POST, URL to https://api.lumaos.cloud/v1/chat/completions, Authentication to Generic Credential Type → Header Auth, then save a credential with Name Authorization and Value Bearer followed by your Luma key. Turn on Send Body, choose JSON → Using JSON and paste the body below. Keep the secret in the credential, not in the node body.
- Credential type
OpenAI- Base URL
https://api.lumaos.cloud/v1- API Key
Your Luma Cloud API key- Organization ID
Leave blank- Model
MODEL_ID_FROM_CATALOG- Use Responses API
Off for this guide- Chain: Prompt
Define below- Chain: Prompt (User Message)
Reply with hello.- Require Specific Output Format
Off for the first test
{
"model": "MODEL_ID_FROM_CATALOG",
"messages": [
{
"role": "user",
"content": "Reply with hello."
}
],
"stream": false
}Paste this into the HTTP Request node's JSON body after replacing the model placeholder. Authentication stays in the Header Auth credential. This is a request body, not an importable workflow.
{{ $json.choices[0].message.content }}Use this expression after a successful non-streaming HTTP Request with its default response-body output. If Include Response Headers and Status is enabled, the reply is under $json.body instead.
Check the connection
- One workflow item should produce a completed text answer in the chain output. A credential connection check alone does not test a prompt, model or tool.
- After the reply, open Dashboard → Usage. Check API Wallet for a wallet key, or subscription usage for a Builder subscription key.
- If the chain asks for chatInput, change Prompt to Define below or provide that field from the previous node. For the example above, Define below avoids needing an input field.
For errors or a request that stops, see troubleshooting. A visible model list alone does not confirm that a chat or editing task can complete.
What to expect
- Use this guide for the OpenAI Chat Model node. Other OpenAI operations, embeddings, uploaded files and hosted tools may require API features this connection does not provide.
- If your version cannot override Base URL or select the returned model, use an HTTP Request node with the request shown in the API quickstart instead.
- Workflow retries and background runs can spend additional credit. Avoid unlimited retries, especially after an uncertain network result.
- Keep custom sampling parameters unset for the first test. Built-in tools and structured output require compatible model features and separate verification.
- Model sub-nodes resolve expressions against the first input item. For batches needing different models or prompts, verify item handling explicitly before enabling production runs.
Troubleshooting n8n
401 or an invalid-key message
Confirm that the saved credential contains a Luma Cloud API key, without surrounding quotes, spaces or a Bearer prefix. Check that this key is still active in Dashboard → API. A dashboard password or another provider's key will not work.
The chain asks for chatInput
For the manual test, choose Define below in the chain's Prompt field and enter the fixed message. Connected Chat Trigger mode expects its own input field; it is a different workflow.
The model cannot be selected or the node calls the wrong endpoint
Select the separate Luma Cloud credential and confirm its Base URL. Keep Use Responses API off. If the node still cannot use your model ID, use the HTTP Request fallback with the explicit URL and body above.
A request succeeds but the next node gets no text
Inspect the actual output. The Basic LLM Chain and HTTP Request nodes return different shapes. For the non-streaming HTTP example, use choices[0].message.content; include body first only when the full response option is enabled.
The workflow repeatedly retries or spends more than expected
Stop the schedule and inspect execution history, retry settings and item count. An agent can make several model calls for one user request. Test with one input and a small retry limit before restoring automation.
429, a balance warning or an interrupted run
Read the error and check the usage associated with this key. A wallet key uses API Wallet funds; a Builder subscription key uses its eligible subscription quota. Pause retries, wait for the indicated reset or retry time, and reduce parallel requests. After a timeout, check the existing result before running a costly job again.
Client documentation
Settings checked on 2026-09-28. These instructions are based on the client’s documentation; installed versions may differ.
