Skip to main content
Last updated on

Configuration

Unlike the Python and TypeScript SDKs, the n8n node has no environment variables or a middleware-options object. Configuration happens in two places: the OpenBox API credential, and the node's own parameters.

OpenBox API Credential

Create this once under Settings → Credentials → Add Credential.

FieldRequiredDescription
API KeyYesAgent API key issued by OpenBox. Live keys start with obx_live_; test keys with obx_test_.
Agent DIDNoAgent decentralised identifier (did:aip:<uuid>).
Agent Private KeyNoBase64-encoded raw 32-byte Ed25519 seed.

Agent DID and Agent Private Key

DID signing is enabled by default for newly registered agents. If signing is enabled, set both Agent DID and Agent Private Key on the credential — every request is then signed locally with an Ed25519 signature. If Require signing is disabled for the agent, leave both fields blank.

OpenBox: Agent Node Parameters

These are set per node, in the n8n editor.

Source for Prompt (User Message)

ValueBehavior
Connected Chat Trigger Node (auto, default)Reads chatInput from a connected Chat Trigger. If absent, the node falls back to the first non-empty string field among chatInput, text, message, input, query, prompt, then any string field on the item.
Define Below (define)Use the Prompt field, which accepts static text or an expression.

Options

OptionDefaultDescription
System MessageYou are a helpful assistantSent to the agent before the conversation starts.
Max Iterations10Maximum model/tool loop iterations before the node stops and returns a truncation message.
Return Intermediate StepsfalseInclude intermediate agent steps in the output.
Automatically Passthrough Binary ImagestruePass binary images through to the agent as image-type messages.

Current Defaults (Not Yet Configurable)

The node always constructs its internal governance middleware with a fixed set of options — these are not exposed as node parameters yet, unlike the equivalent settings in the Python and TypeScript SDKs.

SettingFixed valuePython/TypeScript SDK equivalent
agentNameDerived from the node's display name (n8n.Agent.<Node Name>)agent_name
taskQueue"n8n"task_queue
onApiErrorfail_openon_api_error
governanceTimeout30 secondsgovernance_timeout
toolTypeMap{} (no tool classification)tool_type_map
skipToolTypesnoneskip_tool_types
Event emission flags (send*Event)all enabledsend_chain_start_event, etc.
HITL pollingenabled, 5s interval, 5 minute timeout
HTTP instrumentationenabled
File I/O instrumentationdisabled
Database instrumentationenabled (n8n's own internal Postgres connection is excluded)sqlalchemy_engine

If you need one of these tuned per agent, rename the node to control the agentName value shown in traces, or open an issue against n8n-nodes-openbox-hook.

Next Steps

  1. Error Handling — Handle governance decisions with Continue On Fail
  2. Integration Walkthrough — Wire and verify an existing n8n agent
  3. Event Model — Understand the event payloads used by policies and guardrails
  4. Troubleshooting — Diagnose configuration and telemetry issues