@hostwebhook/node-types 1.16.0 → 1.17.0

package/dist/registry.d.ts

@@ -28,6 +28,19 @@ export interface NodeRegistryEntry {
     color: string;
     /** Whether this node supports test execution */
     testable: boolean;
+    /**
+     * Optional per-instance predicate marking a node as "tool-only".
+     * When this returns true, the canvas should hide every connectable
+     * handle so the user cannot draw pipeline edges to/from this node —
+     * it lives instead inside an upstream AI Node's tools[] list.
+     *
+     * Lets new toolkit-style nodes opt-in without per-component hardcoding
+     * in the dashboard. Currently only emailAction(aiEnabled=true) uses
+     * this; serviceTrigger or future Slack/Discord toolkits could too.
+     *
+     * Predicate must be pure (no side effects) — called on every render.
+     */
+    isToolOnly?: (entity: Record<string, unknown>) => boolean;
 }
 export declare const NODE_REGISTRY: Record<NodeType, NodeRegistryEntry>;
 /** Get registry entry by canonical type */

package/dist/registry.js

@@ -145,6 +145,10 @@ exports.NODE_REGISTRY = {
         group: 'Actions', detailPath: '/dashboard/email-actions', apiPath: '/email-actions',
         stateKey: 'emailActions', allStateKey: 'allEmailActions',
         color: '#f472b6', testable: true,
+        // AI Toolkit mode wires the node through the upstream AI Node's
+        // tools[] list, not via canvas edges — hide handles to prevent
+        // accidental misrouting that would silently fire with empty fields.
+        isToolOnly: (e) => e.aiEnabled === true,
     },
     httpAction: {
         type: 'httpAction', prefix: 'ha', label: 'HTTP Action',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hostwebhook/node-types",
-  "version": "1.16.0",
+  "version": "1.17.0",
   "description": "Shared node type definitions, connection rules, and dispatch config for HostWebhook",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",