Description

n8n-nodes-loomcycle

Community n8n nodes for the loomcycle agentic runtime — design and operate loomcycle agents directly from n8n’s visual builder.


This package realises Phase 2 / Vector 3 of the loomcycle ↔ n8n integration RFC: custom n8n nodes that let operators drive loomcycle from the n8n canvas, while loomcycle stays the agentic runtime substrate.

📦 Two editions — which one do I want?

This repo ships two parallel packages from two branches. Pick by where your n8n runs:

| | Slim (this package) | Full |
|—|—|—|
| npm | @loomcycle/n8n-nodes-loomcycle | @loomcycle/n8n-nodes-loomcycle-full |
| branch | main | full-edition |
| nodes | 20 | 24 |
| n8n Cloud verified | ✅ yes — passes n8n’s community-node scanner (zero deps, no langchain, no timers) | ❌ no — self-hosted only, install manually |
| AI-Agent Tool sub-nodes (Memory / Channel / Sub-Agent / MCP Server Tool) | — (wire the action nodes as Agent tools, or use the Chat Model) | ✅ included (langchain-based) |
| Triggers | poll-based (n8n schedules) | SSE-push + poll fallback (lower latency) |
| Run Wait for Completion op | — (use the Run Completed trigger / n8n Wait node) | ✅ included |
| Chat Model | @n8n/ai-node-sdk (langchain-free) | langchain BaseChatModel |

Use the Slim package (this one) if you’re on n8n Cloud, want the verified node, or don’t need the langchain Tool sub-nodes.

Switch to the Full edition if you’re self-hosted and want the extra nodes / SSE triggers / Wait op:

Self-hosted n8n → Settings → Community Nodes → Install:
@loomcycle/n8n-nodes-loomcycle-full

Both track the same loomcycle wire API and credential; they differ only in node surface + Cloud-eligibility. The rest of this README documents the slim package.

Requirements

These nodes are a thin n8n-shaped wrapper over loomcycle’s wire API — they call your loomcycle deployment, they don’t run an agent runtime inside n8n. So you need:

• A reachable loomcycle deployment + a bearer token (loomcycle’s LOOMCYCLEAUTHTOKEN). Every node call goes out to the Base URL on the LoomCycle API credential.

– Self-hosted n8n: loomcycle can sit on localhost / your LAN (e.g. http://127.0.0.1:8787).
– n8n Cloud: loomcycle must be reachable from the public internet — a public HTTPS URL or a tunnel (Cloudflare Tunnel, ngrok, …) — because n8n Cloud makes the outbound call from its own network, not yours.

• loomcycle ≥ v0.9.2 for the substrate-admin ops (AgentDef / SkillDef / MCP Server); ≥ v0.12.x for the Schedule node and per-tool credentials. Basic Run / Memory / Channel ops work on older builds.
• n8n ≥ 1.82 (the package targets n8n-workflow ≥ 1.82).

Quick install

In your n8n Settings → Community Nodes → Install:
@loomcycle/n8n-nodes-loomcycle

Once installed, configure the LoomCycle API credential with your loomcycle deployment’s bearer token + base URL.

The package lives under the @loomcycle npm org alongside @loomcycle/client — same trust boundary, same maintainer.

What’s in the box

Twenty nodes (16 action + 3 trigger + 1 AI-Agent cluster sub-node) plus one credential type. Zero runtime dependencies — n8n-Cloud-verification-ready.

Credential

• LoomCycle API — bearer token + base URL + optional Default User ID / User Tier / MCP URL. The credential test calls GET /v1/_me (whoami) to validate the bearer resolves to a principal (tenant + scopes) — requires loomcycle ≥ v0.17. Under v0.17’s multi-tenant authorization (RFC L), the bearer is a tenant-scoped OperatorTokenDef token; provision it with the scopes your workflow’s operations need.

Action nodes

As of 2.0.0 the former single multi-resource umbrella node is split into dedicated action nodes, each with its own canvas icon (n8n renders one icon per node type — separate nodes are the only way to give each entity a distinct glyph). They all share one credential and one wire client; they are drag-and-drop separate in the node picker.

• LoomCycle Run — Spawn / Spawn Batch / Get Status / Get Transcript / Compact / Cancel / List Agents. Spawn-time Sampling / Compaction / Run Timeout overrides live under Additional Fields. Spawn Batch fans out up to 32 runs (loomcycle ≥ v0.33); Compact summarises a parked run’s context (≥ v0.33). (To wait for completion, use the Run Completed trigger or n8n’s own Wait node.)
• LoomCycle Memory — Get Entry / List Entries / List Scope IDs / List Scopes / Set Entry / Delete Entry (full CRUD; per-tool credentials userCredentials map on Spawn require loomcycle ≥ v0.12.x)
• LoomCycle Channel — Publish / Subscribe / Peek / Ack / Await / Broadcast / List Channels / Create Channel / Update Channel / Delete Channel / Purge Channel. Await (fan-in) waits on a predicate across channels and Broadcast (fan-out) publishes to many atomically (loomcycle ≥ v0.25); yaml-declared channels remain immutable (but Purge is allowed on them).
• LoomCycle Agent Definition — Create / Fork / Get / List Versions / Promote / Retire / Verify (content_sha256 round-trip). Create/Fork expose a Provider dropdown (folded into the overlay); selecting Code-JS authors a deterministic JavaScript agent (RFC J).
• LoomCycle Skill Definition — same 7 ops as AgentDef, applied to skills
• LoomCycle MCP Server — Register / Fork / Promote / Retire / Get / List Versions / Rediscover / Verify — dynamic MCP server registration (requires loomcycle ≥ v0.9.2)
• LoomCycle Schedule — Create / Fork / Get / List Versions / Retire — substrate-native scheduled runs (RFC E; requires loomcycle ≥ v0.12.x). Fired runs land on the Run Completed trigger.
• LoomCycle Hook — Register / List / Delete — outbound pre/post-tool webhook callbacks; point the callback URL at an n8n Webhook trigger to call back into a workflow on matched tool calls.
• LoomCycle Webhook — Create / Fork / Get / List Versions / Retire — inbound webhook endpoints (RFC H; requires loomcycle ≥ v0.14.x): an external POST to a loomcycle-hosted endpoint spawns an agent run / publishes to a channel. (Distinct from Hook above, which is outbound.)
• LoomCycle A2A Agent — Create / Fork / Get / List Versions / Retire — register external A2A (Agent2Agent) agents loomcycle can call as tools (RFC G; requires loomcycle ≥ v0.14.x).
• LoomCycle A2A Server Card — Create / Fork / Get / List Versions / Retire — manage the agent card loomcycle publishes to expose its own agents to external A2A clients (RFC G; requires loomcycle ≥ v0.14.x).
• LoomCycle Interruption — List for User / List for Run / Resolve — human-in-the-loop over Interruption.ask: list pending agent questions and post a human’s answer back to unblock the parked run (requires loomcycle’s consumer-MCP interruption backend).
• LoomCycle LLM — Chat / Embeddings — direct calls to loomcycle’s LLM gateway (POST /v1/_llm/*) as a workflow step: provider routing + auth + retry handled substrate-side, no agent loop. For RAG / embedding pipelines. (Distinct from the Chat Model sub-node, which feeds an AI Agent.)
• LoomCycle Memory Backend — Create / Fork / Get / List Versions / Retire — versioned memory-backend definitions (in-process or external REST store + ranker) that agents’ Memory tool dispatches to (RFC I; requires loomcycle ≥ v0.15).
• LoomCycle Operator Token — Get / List / Retire — operator-token lifecycle (RFC L; requires loomcycle ≥ v0.17). Mint + rotate are intentionally NOT here — those return the token secret, which must not enter n8n execution data; do them via the loomcycle Web UI / CLI.
• LoomCycle Snapshot — Create / List / Get / Restore / Delete / Export URL — runtime snapshot backup + restore (loomcycle ≥ v0.8.17): snapshot before a deploy, restore on rollback. Restore accepts a stored snapshot ID or an inline envelope; Export URL returns a bearer-authed download link.

> Migration from 1.x: the umbrella LoomCycle node (type loomCycle) was removed. Workflows built on 1.x must swap each LoomCycle node for the matching dedicated node (e.g. a LoomCycle node with Resource = Memory → LoomCycle Memory); operations and parameters are otherwise unchanged.

Trigger nodes

All three triggers use n8n’s polling framework (poll()), scheduled by n8n’s Poll Times — no in-node timers (n8n Cloud forbids timer primitives in community nodes). Detection latency is the poll interval.

• LoomCycle: Run Completed — polls for agent runs that have reached a terminal state (completed / failed / cancelled), deduping via workflow static data. Filterable by status + parentAgentId.
• LoomCycle: Channel Message — polls a channel each tick: auto-ack (at-most-once, subscribeChannel poll-once) or peek + explicit ack (at-least-once, cursor persisted in workflow static data).
• LoomCycle: Interrupt Pending — polls for new pending interruptions (agent questions) for a user, deduping by interrupt_id. Wire the output to a human channel (Slack / email / form) and feed the answer back via LoomCycle Interruption → Resolve.

Cluster sub-node (plugs into n8n’s AI Agent)

• LoomCycle Chat Model — plugs into the AI Agent’s Chat Model slot. Routes the agent’s LLM calls through loomcycle’s gateway (POST /v1/_llm/chat) instead of a direct provider SDK. Single credential covers all providers; loomcycle’s resolver picks provider / model at request time; per-user quota tracking; single audit log. Supports tool calling. Built on @n8n/ai-node-sdk (BaseChatModel) — langchain-free, so the package stays Cloud-verifiable. No agent loop — this is the thin gateway shim, not the full runtime; use the LoomCycle Run action node for the full loop.

> Removed in v3.0.0: the langchain-based Memory / Channel / Sub-Agent / MCP Server Tool sub-nodes. n8n Cloud bans community nodes that depend on @langchain/core, and @n8n/ai-node-sdk has no tool-supply API yet. To give an AI Agent loomcycle capabilities, wire the action nodes (Run / Memory / Channel) as the Agent’s tools, or call loomcycle via the Chat Model. The Tool sub-nodes will return if/when the SDK adds a tool path.

Configure the credential

In n8n, navigate to Settings → Credentials → New and pick LoomCycle API.

| Field | Required | Notes |
|—|—|—|
| Base URL | yes | e.g. http://127.0.0.1:8787 |
| Bearer Token | yes | Matches loomcycle’s LOOMCYCLEAUTHTOKEN env var |
| Default User ID | no | Falls through to any node where userId is left empty |
| Default User Tier | no | Same fall-through |
| MCP URL (optional) | no | Only needed if you reference loomcycle’s MCP server from n8n’s MCP Client Tool sub-node (Vector 1) |

Click Test → a green checkmark means the bearer authenticated. Behind the scenes: GET /v1/_me with Authorization: Bearer — this resolves the token’s principal (tenant + scopes), so an invalid / expired / wrong-tenant token fails the test here rather than at runtime. (Requires loomcycle ≥ v0.17; on older deployments, change is needed — see the editions/compat notes.)

Examples

Four importable workflow JSONs in examples/ cover the canonical patterns:

| # | File | Pattern |
|—|—|—|
| 01 | 01-multi-agent-research.json | Researcher → summariser → channel digest |
| 02 | 02-slack-loomcycle-slack.json | Slack trigger → loomcycle agent → Slack reply |
| 03 | 03-daily-activity-report.json | Cron → listAgents → JS aggregation → email |
| 04 | 04-n8n-as-loomcycle-tool.json | Vector 2 — n8n workflow as MCP server consumed by loomcycle |

(The AI-Agent + cluster-tool examples were removed in v3.0.0 alongside the langchain Tool sub-nodes.)

Import via Workflows → Import from File, then attach your LoomCycle API credential. See examples/README.md for per-example prerequisites + caveats.

Provisioning MCP servers dynamically

The LoomCycle MCP Server action node registers HTTP / Streamable-HTTP MCP servers in the substrate at workflow-design time (run it once, ahead of any Run nodes), so spawned agents can reference them as mcp*:

1. Register: mcpServerDef({op: 'create', name, transport, url, headers, promote: true}). Re-registering identical content is a no-op (deduplicated: true) on loomcycle ≥ v0.20, so you can run Register unconditionally — no Get-first dance needed.
2. Manage: Fork / Promote / Retire / Rediscover / Verify the registration as versioned MCPServerDefs.
3. Spawn agents (via LoomCycle Run) with allowed_tools: ['mcp*'] to give them the MCP server’s tool surface.

Tool auto-discovery (loomcycle ≥ v0.20). Register/Fork run the MCP tools/list handshake at registration and return a discovered count in the node output — you can see the tool surface immediately instead of waiting for first call. It’s best-effort: an unreachable peer still registers and self-heals lazily. Untick Discover Tools at Registration to register connection metadata only.

Two create-time checks to know about (v0.20): the URL host is validated against the allowlist at registration (a loopback / RFC1918 callback host must be in the private host allowlist, not just the general one), and inner ${LOOMCYCLE_*} header tokens are expanded at registration — so those env vars must exist on the deployment before you Register, or the discovery handshake authenticates with an unresolved token.

> (Through v2.x this was an auto-provisioning AI-Agent cluster tool. That tool was langchain-based and removed in v3.0.0; the same substrate capability is now driven explicitly via the MCP Server action node.)

The env-var mirror

The Headers field accepts template strings (not plaintext credentials):

Authorization: Bearer ${LOOMCYCLESLACKTOKEN}

At request time, loomcycle substitutes ${LOOMCYCLE} tokens from its own environment. The operator must mirror the credential: it lives in n8n (for n8n’s own use, if any) AND in loomcycle’s env (LOOMCYCLESLACKTOKEN=…). Plaintext credentials never traverse the n8n → loomcycle wire. The MCP Server node’s UI renders a “Required env vars on loomcycle” notice listing the ${LOOMCYCLE} tokens it detects in your headers.

Code-JS agents

code-js (RFC J) is a loomcycle synthetic provider: the agent runs deterministic JavaScript instead of an LLM — replayable, no model cost. A code-js agent is just an Agent Definition with provider: code-js (and no model), spawned through the normal LoomCycle Run → Run Completed lifecycle. No dedicated node is needed.

Author it inline from n8n (loomcycle ≥ v0.20): on LoomCycle Agent Definition → Create (or Fork), pick Code-JS in the Provider dropdown and write the source in the JavaScript Code editor that appears. The node folds it into the overlay as code_body; loomcycle compiles + content-hashes it at registration. No host filesystem access needed — the code travels the wire like any other definition field.

One host prerequisite: enable the provider with LOOMCYCLECODEAGENTSENABLED=1 (default off — operator-trust, same posture as the Bash tool; or registration is refused). Inline source is capped at ~256 KB. For reproducible runs, optionally LOOMCYCLECODEAGENTSDETERMINISTIC=1.

> Filesystem fallback (still supported): leave the JavaScript Code editor empty and loomcycle falls back to agentcode//index.js (under LOOMCYCLECODEAGENTSROOT) on the host, where matches the Agent Definition name. Inline code_body wins when both are present.

Passing metadata to agents

loomcycle ≥ v0.21 adds a non-secret metadata channel to the agent. A code-js agent reads it as input.metadata; an LLM agent receives it as a trusted prompt block. It’s for context, not secrets (metadata is safe to log) — keep tokens in the credentials fields. Three entry points, all surfaced as a Metadata (JSON) field:

• LoomCycle Run → Spawn — Metadata (JSON) under Additional Fields. Per-call and trusted (first-party bearer); not inherited by a continuation.
• LoomCycle Schedule → Create / Fork — static Metadata (JSON), delivered on every scheduled fire. Override it per fork for the canonical “one template, a different repo per tenant” pattern.
• LoomCycle Webhook → Create / Fork — two channels:

– Static Metadata (JSON) — operator-authored, delivered trusted.
– Request-sourced — add payloadmapping entries with runmetadata. targets in the Advanced Overlay (e.g. {"runmetadata.repo": "$.repository.fullname"}). These are projected from the inbound POST body and delivered untrusted (fenced in a metadata> block for LLMs, input.payloadmetadata for code-js).

The Webhook node also gains Per-Delivery Credentials (template strings → user_credentials), reaching parity with the Schedule node’s per-fire credentials.

Human-in-the-loop

A loomcycle agent can call Interruption.ask to pause and ask a human a question (optionally with a fixed set of options). n8n is the natural place to answer it — and the LoomCycle: Interrupt Pending trigger + LoomCycle Interruption node close the loop end-to-end:

1. Interrupt Pending trigger fires when a new pending ask appears for a user (listUserInterrupts, deduped by interruptid). Each item carries runid, interrupt_id, question, and any options.
2. Route it to a human — a Slack message, an email, an n8n Form, an approval step.
3. LoomCycle Interruption → Resolve posts the human’s answer back (resolveInterrupt(runid, interruptid)). The parked agent unblocks and continues. When the ask declared options, the answer must be one of them (validated server-side).

> Requires loomcycle’s consumer-MCP interruption backend so an external resolver is accepted (set in the deployment’s yaml). Without it, asks are answered through loomcycle’s own Web UI / CLI instead.

Local development install

Want to install from the local checkout for development?

In this package:
git clone https://github.com/denn-gubsky/n8n-nodes-loomcycle.git
cd n8n-nodes-loomcycle
npm install
npm run build
npm link
In your n8n install (e.g. ~/.n8n/nodes):
cd ~/.n8n/nodes
npm link @loomcycle/n8n-nodes-loomcycle
Then restart n8n. The 14 nodes appear under the "LoomCycle" prefix in
the node picker.

Compatibility

Loomcycle version compatibility

| Feature | Min loomcycle | Notes |
|—|—|—|
| Run / Memory (read) / basic Channel | v0.8.x | Substrate stability since v0.8.4 |
| Channel CRUD (publish / subscribe / peek / ack) | v0.9.2 | PR #180 on the substrate |
| AgentDef + SkillDef substrate-admin ops | v0.8.22 | PR #163 |
| content_sha256 Verify op | v0.9.x | PR #175 |
| MCPServerDef substrate (dynamic MCP) | v0.9.2 | PR #177; required by the MCP Server action node |
| parentAgentId filter | v0.9.2 | used by the Run Completed trigger |
| LLM Gateway (POST /v1/_llm/chat) powering LoomCycle Chat Model | v0.10.x | enables n8n AI Agent’s Chat Model slot to route through loomcycle |
| Per-tool credentials (RFC F) + Schedule (RFC E) | v0.12.x | Schedule action node |
| Inbound Webhooks (RFC H) + A2A (RFC G) | v0.14.x | Webhook + A2A Agent / A2A Server Card action nodes |

If you’re on older loomcycle, the unaffected nodes still work; the gated ones surface a clean NodeApiError("Requires loomcycle vX.Y").

n8n version compatibility

• Minimum: n8n 1.82.0 (cluster-node API stability threshold)
• Tested against: n8n 2.22.1 (self-hosted Docker)
• Tools Agent path: requires n8n v1.82+ (cluster sub-nodes ship both supplyData() and execute() so they work across older modes too)
• Node.js: ≥ 20.15

@loomcycle/client (bundled, not a runtime dependency)

@loomcycle/client (^0.14.1) is bundled into the published nodes at build time (esbuild), so the package ships with zero runtime dependencies — the requirement for n8n Cloud verification. It’s a devDependency here, not a peer/runtime dep. The adapter tracks loomcycle’s minor version; consuming a new wire method bumps the bundled version. n8n-workflow is the only peer; @n8n/ai-node-sdk (used by the Chat Model) is provided by the n8n host at runtime.

Verified deployments

The integration has been smoke-tested end-to-end against the following configuration:

| Surface | What was validated |
|—|—|
| Action node — Run → Spawn | Picks an agent from the library dropdown (yaml-static + dynamic AgentDef entries, source-tagged), spawns via runStreaming, drains the final text + usage + stopReason into the workflow output |
| Action node — Channel → List | Lists declared channels (read-only credential smoke test) |
| Trigger — Run Completed (polling) | Workflow active → n8n calls poll() on the Poll Times schedule → new terminal-state runs emit, deduped via workflow static data |
| Cluster sub-node — Chat Model inside n8n AI Agent | LoomCycle Chat Model wired to the AI Agent’s Chat Model slot; the agent’s LLM calls route through loomcycle’s gateway (provider routing + per-user quota + single audit log) |
| Network path | TrueNAS-hosted n8n Docker → direct IP to loomcycle (Tailscale MagicDNS bypassed) → sub-second round-trips |

> v3.0.0 note: triggers moved from SSE-push to n8n’s polling framework (n8n Cloud bans in-node timers), so detection latency is the configured poll interval rather than near-instant.

Troubleshooting

Authentication failed after credential test

The bearer doesn’t resolve to a valid principal. Verify with curl against the same endpoint the credential test uses:

curl -H "Authorization: Bearer " http://127.0.0.1:8787/v1/_me

Expect a principal JSON ({"tenantid":"…","subject":"…","scopes":[…],…}). A 401 means the token is invalid/expired; a 404 means the deployment is older than v0.17 (no /v1/me). Under v0.17 multi-tenant auth, also check the token has the scopes for the operations your workflow calls — a missing scope surfaces as a 403 at runtime even though the credential test (which only needs an authenticated principal) passes.

Channel not declared on a Publish

The channel must exist in loomcycle’s channels: yaml block before the publish lands. Declare it operator-side and restart loomcycle. (Dynamic channel creation isn’t supported in the substrate today.)

MCPServerDef ops return “endpoint unknown”

You’re on a loomcycle older than v0.9.2 (PR #177). Upgrade the substrate.

Run Completed / Channel Message trigger isn’t firing

Both are polling triggers — they only fire when the workflow is Active (production), on the schedule set by the node’s Poll Times. In the editor, use Fetch Test Event to run one poll() manually. Detection latency is the poll interval (there’s no SSE push as of v3.0.0).

MCP Server node says “Required env vars on loomcycle: …”

That’s the env-var-mirror hint, not an error. Set the listed env vars on the loomcycle deployment (not on n8n). Restart loomcycle so they’re in scope. The MCP server will then authenticate when an agent invokes it.

LoomCycle Chat Model doesn’t appear in n8n’s AI Agent picker

n8n’s cluster-node API stabilised at 1.82.0. Older n8n versions won’t show the Chat Model sub-node. Upgrade n8n.

Filing issues / contributing

• Bug reports: GitHub issues — please include n8n version, loomcycle version, and a minimum reproduction (a workflow JSON you can attach).
• Loomcycle wire-API gaps: file against loomcycle — this package is a thin adapter over @loomcycle/client.
• Pull requests: see CLAUDE.md for development conventions + the 8 locked design constraints.

License

MIT. See LICENSE.