Skip to main content
The sample workflow uses n8n’s built-in Manual Trigger, Edit Fields, and HTTP Request nodes. It sends one non-streaming request to AceDataCloud Chat Completions and exposes the answer, response ID, model, and token counts. You do not need a community node.

​
Native nodes and model entry

Use independent service nodes after a trigger and search by service name before building HTTP requests. Cloud verification and self-hosted npm installation are separate. For chat, install Ace Data Cloud Chat Model and connect it to an Agent/Basic LLM Chain Model input, with no Base URL field. It is not a default-installed provider or verified Cloud listing. Published 0.1.2 provides native Model Name or ID catalog choices and exact-ID expressions; reading the list does not generate a paid answer. The HTTP example below is an optional low-level recipe, not a replacement for these native nodes or official distribution.

​
Import and run

  1. Follow Get an API key below, then check the current model price and available balance.
  2. In n8n, create a workflow. Choose Import from URL and paste the workflow JSON URL. You can also download the JSON and choose Import from File.
  3. Open AceDataCloud chat. Authentication → Generic Credential Type and Generic Auth Type → Bearer Auth are already set. Click Connect to Bearer Auth, then create or select an HTTP Bearer Auth credential. Enter the token without a Bearer prefix. Select the credential and save the workflow before running it. Credentials are not included in the JSON.
  4. In Set prompt and model, edit the prompt and, if needed, replace gpt-4o-mini with another model supported by Chat Completions. The sample limits output to 80 tokens. Adjust max_tokens in the HTTP Request body if your task needs a longer answer.
  5. Click Execute workflow once. Open Read answer and usage to inspect answer, response_id, model, and token counts. The workflow starts inactive and runs only when you click it.
Keep the token in the n8n credential, not in an Edit Fields node or the workflow JSON. Review n8n’s execution-data retention settings before processing sensitive prompts.

​
Get an API key

  1. Open Applications and sign in or register. If General application is missing, choose Initialize General Application.
  2. Copy the application’s API Key, or choose Keys / Manage Keys → Create to create a separately named key for n8n. A general application’s key can use services available to your account; a dedicated application’s key is limited to its service.
  3. Check Expiration Time, Set Usage Limitation, and Allowed APIs. Allow Chat Completions and the model you intend to use. Check your balance before running the workflow; any trial allowance is whatever your account currently displays.
  4. Copy the raw token into n8n’s HTTP Bearer Auth credential. Do not include Bearer , quotation marks, or spaces. A platform-... account-management token cannot replace a generation API key.

​
Connect your automation

Replace Start a manual test with your own trigger and map its text to prompt in Set prompt and model. The HTTP Request node posts to https://api.acedata.cloud/openai/chat/completions with stream: false. Downstream nodes can use answer and response_id from Read answer and usage. Each execution can consume credits. The final node’s token counts do not establish the amount charged: check the AceDataCloud usage record for the actual charge. Start with one manual run before adding a schedule or webhook. Monitor successful and failed n8n executions, duration, response IDs, token counts, and the matching AceDataCloud usage records.

​
Handle errors and retries

The HTTP Request node fails the execution on an unsuccessful HTTP response. Open that node to inspect the status and error body: Automatic retries are disabled for this POST because replaying a completed request could incur a second charge. If you need retries, add them only after deciding how to reconcile ambiguous outcomes in your workflow. This JSON is available for import directly. It will appear in n8n’s built-in Templates search only after n8n publishes a separate template listing.