Description

n8n-nodes-disclarion

This is an n8n community node. It lets you use Disclarion in your n8n workflows.

Disclarion logs AI-generated interactions and gives you back disclosure metadata so you can meet EU AI Act Article 50 transparency obligations — labeling AI-generated content and disclosing that a user is talking to an AI system.

n8n is a fair-code licensed workflow automation platform.

Installation
Operations
Credentials
Compatibility
Usage
Resources
Version history

Installation

Follow the installation guide in the n8n community nodes documentation, and search for n8n-nodes-disclarion.

Operations

• Track Interaction — logs one AI response with Disclarion. Returns the stored log entry plus isfirstmessage, which tells you whether this is the first message in the session (useful for deciding whether to show an AI-disclosure notice to the end user).

Credentials

You need a Disclarion account and an API key:

1. Sign up at app.disclarion.com.
2. Go to Project Settings → API Keys and create a key (dcllive... or dcltest...).
3. In n8n, create a Disclarion API credential and paste the key in. Leave Base URL as https://api.disclarion.com unless you’re on a self-hosted or staging backend.
4. Use the credential’s Test button to verify the key — it calls GET /v1/me, which only reads account info and never writes a log entry.

Compatibility

Tested against n8n 1.x with n8nNodesApiVersion: 1. No known version incompatibilities.

Usage

Add the Disclarion node anywhere in your workflow after you’ve called an LLM (OpenAI, Anthropic, Gemini, or any other provider). Fill in:

• Session ID — a stable identifier for the end-user conversation (e.g. a chat session ID), used to group log entries and detect the first message in a session.
• Provider and Model Name — which model produced the response.
• Optionally, under Additional Fields: the provider’s own response ID, any extra JSON metadata you want stored alongside the log, Jurisdiction / Interaction Type (see below), and Content Type (see below).

The node can also be used directly as a tool by n8n’s AI Agent node, so an agent can log its own reply as it generates it.

Jurisdiction and Interaction Type

Under Additional Fields, two optional fields feed Disclarion’s backend Obligation Engine, which decides what disclosure/logging obligations apply:

• Jurisdiction — free text (e.g. EU). Leave it out to use the backend default, EU.
• Interaction Type — Chat or Generated Content. Leave it out to use the backend default, Chat.

Leaving both out reproduces the exact request every workflow built before this existed already sends — nothing changes unless you explicitly add one of these fields.

Generated Content is the one worth calling out for n8n specifically: it’s for workflows that draft and publish AI-generated content, product descriptions, articles, social posts, rather than holding a live conversation with a user. Where Chat may return a disclosuremodal obligation (something to show a user mid-conversation), Generated Content returns contentlabel instead: a signal that the content leaving this workflow should be labeled as AI-generated wherever it’s published, with no chat UI involved at all. A typical automated-content workflow:

Generate content (OpenAI node)
  → Disclarion node
      Interaction Type: Generated Content
  → Publish content (e.g. a CMS or social API node)

The Disclarion node’s output includes interactiontype and appliedactions from the stored log entry, so a later node in the workflow can branch on appliedactions (e.g. only add an “AI-generated” caption when it actually contains contentlabel) instead of assuming it always applies.

Content Type

Also under Additional Fields: Content Type is free text describing the kind of content being logged, e.g. image, video, audio, text — no fixed list. It’s only meaningful when Interaction Type is Generated Content, matching the Python SDK’s dc.trackcontent(contenttype=...). It’s purely descriptive today (it doesn’t change which obligations apply, only what’s recorded for later reporting). Leave it blank to send no content type at all, same as before this field existed.

Resources

• n8n community nodes documentation
• Disclarion documentation
• Disclarion Python SDK (for logging directly from application code instead of a workflow)

Version history

• 0.3.1 — Updated node icon to the official Disclarion logo.
• 0.3.0 — Added an optional Content Type field (under Additional Fields), matching the contenttype parameter the Python SDK exposes as of disclarion 0.3.2 (dc.trackcontent()). Backward compatible: leaving it out sends the exact same request as before.
• 0.2.0 — Added optional Jurisdiction and Interaction Type fields (under Additional Fields), matching the jurisdiction/interaction_type parameters the Python SDK exposes as of disclarion 0.3.0. Backward compatible: leaving both out sends the exact same request as before.
• 0.1.0 — Initial release: Track Interaction operation, API key credential with key verification.