@n8n/workflow-sdk 0.13.1 → 0.14.1

package/dist/prompts/node-guidance/node-tips/types.d.ts

@@ -1,7 +0,0 @@
-export interface NodeGuidance {
-    nodeType: string;
-    usage: string;
-    connections: string;
-    configuration: string;
-    recommendation?: string;
-}

package/dist/prompts/node-guidance/node-tips/types.js

@@ -1,3 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-//# sourceMappingURL=types.js.map

package/dist/prompts/node-guidance/node-tips/types.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"types.js","sourceRoot":"","sources":["../../../../src/prompts/node-guidance/node-tips/types.ts"],"names":[],"mappings":""}

package/dist/prompts/node-guidance/node-tips/webhook.d.ts

@@ -1,2 +0,0 @@
-import type { NodeGuidance } from './types';
-export declare const webhook: NodeGuidance;

package/dist/prompts/node-guidance/node-tips/webhook.js

@@ -1,38 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.webhook = void 0;
-exports.webhook = {
-    nodeType: 'n8n-nodes-base.webhook',
-    usage: `Search for "Webhook" (n8n-nodes-base.webhook) when:
-- Workflow needs to receive HTTP requests from external services
-- API callbacks, webhooks, or HTTP endpoints are needed
-- Integration requires real-time event handling from external systems`,
-    connections: `WEBHOOK RESPONSE MODE RULES - CRITICAL:
-
-Response modes and their requirements:
-- "onReceived" (Immediately): Responds instantly when webhook is called. No RespondToWebhook node needed.
-- "lastNode" (When Last Node Finishes): Responds with data from last node. No RespondToWebhook node needed.
-- "responseNode" (Using Respond to Webhook Node): REQUIRES a RespondToWebhook node connected downstream.
-
-RULE 1: If responseMode='responseNode', you MUST add a RespondToWebhook node
-RULE 2: If RespondToWebhook node exists, responseMode MUST be 'responseNode'
-
-Pattern for custom response control:
-Webhook (responseMode: responseNode) → [Processing] → RespondToWebhook`,
-    configuration: `WEBHOOK RESPONSE MODE CONFIGURATION:
-
-Choose responseMode based on use case:
-- "onReceived": Quick acknowledgment, processing happens async
-- "lastNode": Return processed data, simple request-response flows
-- "responseNode": Full control over response timing, headers, status codes
-
-CRITICAL: When user needs to control response content/timing/headers, set responseMode='responseNode' AND add RespondToWebhook node.
-
-When NOT to use responseNode:
-- Simple acknowledgments (use 'onReceived')
-- Return last node output directly (use 'lastNode')`,
-    recommendation: `For webhook workflows requiring custom response handling (status codes, headers, delayed response), use responseMode='responseNode' with a RespondToWebhook node.
-
-For simple webhook acknowledgments or direct data return, use 'onReceived' or 'lastNode' modes respectively.`,
-};
-//# sourceMappingURL=webhook.js.map

package/dist/prompts/node-guidance/node-tips/webhook.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"webhook.js","sourceRoot":"","sources":["../../../../src/prompts/node-guidance/node-tips/webhook.ts"],"names":[],"mappings":";;;AAEa,QAAA,OAAO,GAAiB;IACpC,QAAQ,EAAE,wBAAwB;IAElC,KAAK,EAAE;;;sEAG8D;IAErE,WAAW,EAAE;;;;;;;;;;;uEAWyD;IAEtE,aAAa,EAAE;;;;;;;;;;;oDAWoC;IAEnD,cAAc,EAAE;;6GAE4F;CAC5G,CAAC"}