n8n-nodes-trigguard

n8n-nodes-trigguard

EXPERIMENTAL — community n8n node; not production-validated as enterprise integration.
Canonical execution client: @trigguard/execution-sdk.
PACKAGE_STATUS_MATRIX.md · ONBOARDING_AUTHORITY_MAP.md.

npm package name: n8n-nodes-trigguard. Community node for n8n that calls the TrigGuard gateway POST /execute before passing workflow items on (see src/nodes/TrigGuard/TrigGuard.node.ts).

Do not run npm create @n8n/node in a second copy — this package already lives at packages/trigguard-n8n-node/.

Build

cd /path/to/TrigGuard/packages/trigguard-n8n-node
npm install
npm run build

The node uses native fetch to call POST /execute (no trigguard-js dependency) so npm install n8n-nodes-trigguard from the registry is self‑contained.

Use with self‑hosted n8n

• Build this package.
• Point n8n custom / community nodes at the built dist/ output (or install from npm after publish).
• In the node, set Gateway Base URL (e.g. http://127.0.0.1:8080), API Key, and Policy surface; upstream JSON becomes context to /execute.

Local dev (n8n UI)

npm install
npm run dev

This runs npm run build then starts n8n@1.82.0 with N8N_CUSTOM_EXTENSIONS set to this package directory (requires npm 7+ for INIT_CWD). If the node does not appear, set manually: N8N_CUSTOM_EXTENSIONS=/absolute/path/to/trigguard-n8n-node npx n8n@1.82.0 start.

Publish to npm (maintainers)

• npm run build
• npm login then npm publish --access public
• End users: npm install n8n-nodes-trigguard and enable community nodes per n8n version.

Name vs folder

• Directory: trigguard-n8n-node (monorepo convention)
• npm name: n8n-nodes-trigguard (n8n community naming)

Related

• Python SDK: pip install trigguard
• Node helper: packages/trigguard-js (authorize / guard)
• LangChain: integrations/langchain/ in the monorepo