InkRoom
Menu

InkRoom · Visual & Batch Design Studio

Connect n8n to the InkRoom Image API

Use n8n’s HTTP Request node with InkRoom’s OpenAI-compatible image API. Check available image models and pricing before generating your first image.

Setup

  1. Get a public API key in InkRoom API Management. In n8n select Generic Credential Type → Header Auth and store the Authorization header with its Bearer value as a credential.
  2. Connect a Manual Trigger to HTTP Request and start with GET /v1/models. Check the live image catalog for an available image model ID and pricing.
  3. After checking the expected cost, use POST /v1/images/generations for one sample. Keep the response, execution record and errors. Leave Retry On Fail off for paid submissions and investigate the original call after a timeout.

Connection settings

Connection settings
FieldValue
API origin · inkroom.aihttps://api.inkroom.ai
API origin · inkroom.tophttps://api.inkroom.top
AuthenticationHeader Auth · Authorization: Bearer YOUR_INKROOM_API_KEY
Read-only checkGET /v1/models
Create one imagePOST /v1/images/generations · Content-Type: application/json

Single-image request body

{
  "model": "YOUR_AVAILABLE_IMAGE_MODEL_ID",
  "prompt": "A blue ceramic cup on a neutral studio background",
  "n": 1
}

FAQ

Do I need an InkRoom node?

This guide uses the built-in HTTP Request node on instances that can reach the relevant InkRoom API domain.

Which credential does HTTP Request use?

Use a public API key as the Bearer credential on /v1. Use MCP tokens for Remote MCP connectors.

How do I control generation costs in a workflow?

The public API submits directly. Check the live catalog, limit models, settings, quantities and triggers, and review actual charges before increasing volume.

Should n8n retry a timed-out paid request?

The original request may still be running. Keep the execution log and any returned identifier, and check its status and charges before handling unfinished work.

Documentation

Related pages