@hostwebhook/node-types 1.50.1 → 1.52.0

package/dist/telegram-operations.d.ts

@@ -11,7 +11,7 @@
  * extending this list, bumping the package, and re-installing in
  * consumers — same pattern as Gmail / Calendar / Drive.
  */
-export declare const TELEGRAM_OPERATIONS: readonly ["sendMessage", "replyToMessage", "sendPhoto", "sendDocument", "sendVoice", "editMessageText", "deleteMessage", "answerCallbackQuery", "forwardMessage", "sendPoll"];
+export declare const TELEGRAM_OPERATIONS: readonly ["sendMessage", "replyToMessage", "sendPhoto", "sendDocument", "sendVoice", "sendAndWaitForResponse", "editMessageText", "deleteMessage", "answerCallbackQuery", "forwardMessage", "sendPoll"];
 export type TelegramOperation = (typeof TELEGRAM_OPERATIONS)[number];
 /** Type guard — useful when validating untrusted input (DTOs, tool calls). */
 export declare function isTelegramOperation(value: unknown): value is TelegramOperation;

package/dist/telegram-operations.js

@@ -21,6 +21,17 @@ exports.TELEGRAM_OPERATIONS = [
     'sendPhoto',
     'sendDocument',
     'sendVoice',
+    // Pause-the-pipeline op — sends a Telegram message with Approve /
+    // (optional) Disapprove inline buttons and waits for the recipient to
+    // tap one. When `allowFreeText` is on, a text reply in the same chat
+    // also resolves the wait. Backed by the same shared PendingApproval +
+    // send-and-wait infra emailAction uses, with a Telegram-specific
+    // resume path through service-triggers.processTelegramPush (intercepts
+    // callback_query.data === "swat:{token}:a|r" before normal dispatch).
+    // Output of the node carries `payload._waitResponse = { approved,
+    // decidedAt, ipAddress, comment?, responseText?, timedOut? }` for
+    // downstream Conditional nodes.
+    'sendAndWaitForResponse',
     'editMessageText',
     'deleteMessage',
     'answerCallbackQuery',

package/dist/ui.js

@@ -28,7 +28,15 @@ exports.NODE_UI = {
     aggregator: { fromNodes: true, toNodes: true, special: { loopBackAllowed: true } },
     cache: { fromNodes: true, toNodes: true },
     code: { fromNodes: true, toNodes: true, special: { loopBackAllowed: true } },
-    ai: { fromNodes: true, toNodes: true },
+    // AI Node: in classifier mode (entity.outputMode === 'classifier') the
+    // node fans out to N output handles — one per category in
+    // `entity.categories[]` plus an optional synthesized "Other" handle
+    // (controlled by `entity.includeOtherBranch`). Wiring lives in
+    // `categories[].outputNodes` + `otherOutputNodes`, mirroring
+    // ConditionalNode's `branches[]` + `elseOutputNodes`. In any other
+    // outputMode the node falls back to the single right-out handle
+    // NodeShell renders when no dynamic outputs materialize.
+    ai: { fromNodes: true, toNodes: true, outputHandles: ['right'], special: { loopBackAllowed: true, connectModal: 'output-group', outputGroups: { field: 'categories', nameField: 'name', summaryField: 'description', label: 'category', elseField: 'otherOutputNodes' } } },
     markdown: { fromNodes: true, toNodes: true, special: { loopBackAllowed: true } },
     fileTransform: { fromNodes: true, toNodes: true },
     limit: { fromNodes: true, toNodes: true, special: { loopBackAllowed: true } },

package/package.json

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