@levinnovation/n8n-nodes-agentyx

Custom n8n community nodes that power the Agentyx deterministic SDLC.

What's inside

| Node | Purpose | | --- | --- | | Agentyx Tenant Context | Stamps every execution with _agentyx_context.{tenant,domain,capability,timestamp} so downstream nodes (and the audit logger) carry the same identity. | | Agentyx Audit Logger | Emits a structured audit record (action, tenant, sub-workflows called, git hash) and optionally writes to a central audit DB. | | Agentyx AI Agent (Basic) | OpenRouter-backed agent: model picker, system prompt, user message, optional Redis memory. Designed to be the standard agent core for v2 workflows. | | Agentyx Composio MCP Tool | Filters Composio MCP tools by toolkit and exposes them to the AI agent. | | Agentyx Channel Input | Normalizes inbound payloads from Kapso WhatsApp, Telegram, Meta comments, LibreChat, Twenty webhooks into a single envelope. | | Agentyx Channel Output | Formats a unified reply for the right channel (WhatsApp, Telegram, Slack, Email/Resend). | | Agentyx CRM Query (Twenty) | Read-side helpers for Twenty CRM: search/list/getById for people, companies, opportunities. | | Agentyx CRM Update (Twenty) | Write-side helpers: create/update for people, companies, opportunities; link person↔company. |

Install

In n8n: Settings → Community Nodes → Install and enter @levinnovation/n8n-nodes-agentyx.

Programmatic install (for a self-hosted n8n):

npm i @levinnovation/n8n-nodes-agentyx

You'll also need the following env vars on the n8n process:

N8N_COMMUNITY_PACKAGES_ENABLED=true
N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true   # if you call these from an AI Agent
N8N_REINSTALL_MISSING_PACKAGES=true            # reinstalls on container restart

Develop

cd services/n8n-node-sdk
npm install
npm run build    # one-shot
npm run dev      # tsc --watch

The compiled dist/ is checked in (override of the repo's .gitignore) so Railway-linked builds of the Agentyx n8n base image (services/n8n-yaml-compiler/Dockerfile.n8n) can copy it directly without devDependencies in the runtime image.

Publish

Tag-driven release. See .github/workflows/publish-n8n-nodes.yml.

# 1. Make sure the work is on main and dist/ rebuilt
cd services/n8n-node-sdk
npm version patch          # or minor / major
# 2. Push the matching git tag (workflow listens on `n8n-nodes-agentyx-v*`)
git push --follow-tags

Alternatively, trigger the GitHub Actions workflow manually with a version_bump input. A dry_run toggle is available to validate the tarball without publishing.

Repo policy

These nodes are tenant-agnostic by design — tenant, domain, capability, and per-record IDs are passed in as parameters by the calling workflow. Do not hard-code Lev Innovation business logic here. Tenant-specific workflows live under tenants/{tenant}/assets/workflows/n8n/ in this repository.

See:

• ADR-0035 (knowledge/decisions/0035-n8n-sdk-and-deterministic-sdlc.md) — why this SDK exists.
• ADR-0036 (knowledge/decisions/0036-publish-n8n-nodes-agentyx-to-npm.md) — why we publish to npm.
• Change log (knowledge/change-log/2026-05-20-n8n-railway-recovery.md) — context for the May 2026 outage that motivated the npm path.