n8n

The claritos community node for n8n: a trigger node for all events and a regular node for every endpoint — generated from the spec.

What the package is

npm package n8n-nodes-claritos (repo: integrations/n8n) with two nodes and one credential type. The regular node is declarative: resource = API domain, operation = endpoint, fields from the schema; lists are unwrapped to their data items. The trigger node subscribes to events via the webhook API. Both are generated from the OpenAPI spec and the event catalog and follow every API version.

Install and connect

In n8n under Settings → Community Nodes install the package n8n-nodes-claritos (self-hosted: npm install in the nodes directory). Credential “claritos API”: API key (capi_…) and environment; n8n tests the connection via GET /me. The key's scopes decide which operations and events work.

bash

# n8n → Settings → Community Nodes → Install
n8n-nodes-claritos

# oder selbst gehostet
cd ~/.n8n/nodes && npm install n8n-nodes-claritos

Trigger node

When the workflow is activated the node creates a subscription for the n8n webhook URL via POST /webhooks (chosen event types, empty = all), stores id and secret in the node data and verifies every delivery against the Standard Webhooks signature (webhook-id, webhook-timestamp, webhook-signature; 5-minute tolerance). Deactivating deletes the subscription. Payload = event envelope {id, type, createdAt, data}. To test without a real event: POST /webhooks/{id}/test from the API or “Test delivery” in the organisation tab.

Regular node

Choose a resource (contacts, invoices, signatures, letters, tasks …), then an operation — path parameters are required fields, query/body fields optional; nested fields (items, values) as JSON. Errors arrive as Problem Details (RFC 9457) and show title/detail in the execution log; 429 carries Retry-After. Use n8n's retry settings sparingly for write operations.

Alternative: MCP client node

n8n ships an MCP client node. Instead of the community node you can also connect the claritos MCP (POST /api/mcp/v1) with an Authorization header — useful for AI-agent workflows where the model picks the tools itself (“MCP” guide).

json

// n8n „MCP Client“-Node: Server-URL + Header
{ "url": "https://www.claritos.io/api/mcp/v1", "headers": { "Authorization": "Bearer capi_…" } }

For operators: publishing

npm account/token as secret NPM_TOKEN; tag n8n-v<version> starts the publish-n8n workflow (tests, build, npm publish with provenance). For the “verified” badge submit the package to n8n (community node guidelines: no runtime dependencies except n8n-workflow — satisfied).