@n8n/ai-workflow-builder 1.16.0 → 1.17.0

package/dist/prompts/chains/parameter-updater/guides/system-message.js

@@ -1,96 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.SYSTEM_MESSAGE_GUIDE = void 0;
-function hasSystemMessageParameters(nodeDefinition) {
-    if (!nodeDefinition.properties)
-        return false;
-    return nodeDefinition.properties.some((prop) => {
-        if (prop.name === 'messages' &&
-            (prop.type === 'fixedCollection' || prop.type === 'collection')) {
-            return true;
-        }
-        if (prop.name === 'options' && prop.type === 'collection' && Array.isArray(prop.options)) {
-            return prop.options.some((opt) => typeof opt === 'object' &&
-                opt !== null &&
-                'name' in opt &&
-                (opt.name === 'systemMessage' || opt.name === 'system'));
-        }
-        return false;
-    });
-}
-exports.SYSTEM_MESSAGE_GUIDE = {
-    patterns: ['*'],
-    condition: (ctx) => hasSystemMessageParameters(ctx.nodeDefinition),
-    content: `
-## CRITICAL: System Message vs User Prompt Separation
-
-AI nodes (AI Agent, LLM Chain, Anthropic, OpenAI, etc.) have TWO distinct prompt fields that MUST be used correctly:
-
-### Field Separation
-1. **System Message** - Model's persistent identity, role, and instructions
-2. **User Message/Text** - Dynamic user context and data references per execution
-
-**Node-specific field names:**
-- AI Agent: \`options.systemMessage\` and \`text\`
-- LLM Chain: \`messages.messageValues[]\` with system role and \`text\`
-- Anthropic: \`options.system\` and \`messages.values[]\`
-- OpenAI: \`messages.values[]\` with role "system" vs "user"
-
-### System Message
-Use for STATIC, ROLE-DEFINING content:
-- Agent identity: "You are a [role] agent..."
-- Task description: "Your task is to..."
-- Step-by-step instructions: "1. Do X, 2. Do Y, 3. Do Z"
-- Behavioral guidelines: "Always...", "Never..."
-- Tool coordination: "Call the Research Tool to..., then call..."
-
-### Text Parameter
-Use for DYNAMIC, EXECUTION-SPECIFIC content:
-- User input: "={{ $json.chatInput }}"
-- Workflow context: "=The research topic is: {{ $json.topic }}"
-- Data from previous nodes: "=Process this data: {{ $json.data }}"
-- Variable context: "=Analyze for user: {{ $json.userId }}"
-
-### Common Mistakes to Avoid
-
-**WRONG - Everything in text field:**
-{
-  "text": "=You are an orchestrator agent that coordinates specialized agents. Your task is to: 1) Call Research Agent Tool, 2) Call Fact-Check Agent Tool, 3) Generate report. Research topic: {{ $json.researchTopic }}"
-}
-
-**CORRECT - Properly separated:**
-{
-  "text": "=The research topic is: {{ $json.researchTopic }}",
-  "options": {
-    "systemMessage": "You are an orchestrator agent that coordinates specialized agents.\\n\\nYour task is to:\\n1. Call the Research Agent Tool to gather information\\n2. Call the Fact-Check Agent Tool to verify findings\\n3. Generate a comprehensive report\\n\\nReturn ONLY the final report."
-  }
-}
-
-### Update Pattern Examples
-
-Example 1 - AI Agent with orchestration:
-Instructions: [
-  "Set text to '=Research topic: {{ $json.researchTopic }}'",
-  "Set system message to 'You are an orchestrator coordinating research tasks.\\n\\nSteps:\\n1. Call Research Agent Tool\\n2. Call Fact-Check Agent Tool\\n3. Call Report Writer Agent Tool\\n4. Return final HTML report'"
-]
-
-Example 2 - Chat-based AI node:
-Instructions: [
-  "Set text to '=User question: {{ $json.chatInput }}'",
-  "Set system message to 'You are a helpful customer support assistant. Answer questions clearly and professionally. Escalate to human if needed.'"
-]
-
-Example 3 - Data processing with AI:
-Instructions: [
-  "Set text to '=Process this data: {{ $json.inputData }}'",
-  "Set system message to 'You are a data analysis assistant.\\n\\nTasks:\\n1. Validate data structure\\n2. Calculate statistics\\n3. Identify anomalies\\n4. Return JSON with findings'"
-]
-
-### Why This Matters
-- **Consistency**: System message stays the same across executions
-- **Maintainability**: Easy to update AI behavior without touching data flow
-- **Best Practice**: Follows standard AI prompt engineering patterns
-- **Clarity**: Separates "what the AI model is" from "what data to process"
-`,
-};
-//# sourceMappingURL=system-message.js.map

package/dist/prompts/chains/parameter-updater/guides/system-message.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"system-message.js","sourceRoot":"","sources":["../../../../../src/prompts/chains/parameter-updater/guides/system-message.ts"],"names":[],"mappings":";;;AAMA,SAAS,0BAA0B,CAAC,cAEnC;IACA,IAAI,CAAC,cAAc,CAAC,UAAU;QAAE,OAAO,KAAK,CAAC;IAE7C,OAAO,cAAc,CAAC,UAAU,CAAC,IAAI,CAAC,CAAC,IAAI,EAAE,EAAE;QAE9C,IACC,IAAI,CAAC,IAAI,KAAK,UAAU;YACxB,CAAC,IAAI,CAAC,IAAI,KAAK,iBAAiB,IAAI,IAAI,CAAC,IAAI,KAAK,YAAY,CAAC,EAC9D,CAAC;YACF,OAAO,IAAI,CAAC;QACb,CAAC;QAGD,IAAI,IAAI,CAAC,IAAI,KAAK,SAAS,IAAI,IAAI,CAAC,IAAI,KAAK,YAAY,IAAI,KAAK,CAAC,OAAO,CAAC,IAAI,CAAC,OAAO,CAAC,EAAE,CAAC;YAC1F,OAAO,IAAI,CAAC,OAAO,CAAC,IAAI,CACvB,CAAC,GAAG,EAAE,EAAE,CACP,OAAO,GAAG,KAAK,QAAQ;gBACvB,GAAG,KAAK,IAAI;gBACZ,MAAM,IAAI,GAAG;gBACb,CAAC,GAAG,CAAC,IAAI,KAAK,eAAe,IAAI,GAAG,CAAC,IAAI,KAAK,QAAQ,CAAC,CACxD,CAAC;QACH,CAAC;QAED,OAAO,KAAK,CAAC;IACd,CAAC,CAAC,CAAC;AACJ,CAAC;AAEY,QAAA,oBAAoB,GAAkB;IAClD,QAAQ,EAAE,CAAC,GAAG,CAAC;IACf,SAAS,EAAE,CAAC,GAAG,EAAE,EAAE,CAAC,0BAA0B,CAAC,GAAG,CAAC,cAAc,CAAC;IAClE,OAAO,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsET;CACA,CAAC"}

package/dist/prompts/chains/parameter-updater/guides/text-fields.d.ts

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

package/dist/prompts/chains/parameter-updater/guides/text-fields.js

@@ -1,31 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.TEXT_FIELDS_GUIDE = void 0;
-function hasTextFields(nodeDefinition) {
-    if (!nodeDefinition.properties)
-        return false;
-    return nodeDefinition.properties.some((prop) => prop.type === 'string' && prop.typeOptions?.multipleValues !== true);
-}
-exports.TEXT_FIELDS_GUIDE = {
-    patterns: ['*'],
-    condition: (ctx) => hasTextFields(ctx.nodeDefinition),
-    content: `
-## Text Field Expression Formatting
-
-### PREFERRED METHOD: Embedding expressions directly within text
-\`\`\`
-"text": "=ALERT: It is currently {{ $('Weather Node').item.json.weather }} in {{ $('Weather Node').item.json.city }}!"
-\`\`\`
-
-### Alternative method: Using string concatenation (use only when needed)
-\`\`\`
-"text": "={{ 'ALERT: It is currently ' + $('Weather Node').item.json.weather + ' in ' + $('Weather Node').item.json.city + '!' }}"
-\`\`\`
-
-### Key Points:
-- Use the embedded expression format when mixing static text with dynamic values
-- The entire string must start with = when using expressions
-- Expressions within text use single curly braces {{ }}
-- The outer expression wrapper uses double curly braces ={{ }}`,
-};
-//# sourceMappingURL=text-fields.js.map

package/dist/prompts/chains/parameter-updater/guides/text-fields.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"text-fields.js","sourceRoot":"","sources":["../../../../../src/prompts/chains/parameter-updater/guides/text-fields.ts"],"names":[],"mappings":";;;AAKA,SAAS,aAAa,CAAC,cAEtB;IACA,IAAI,CAAC,cAAc,CAAC,UAAU;QAAE,OAAO,KAAK,CAAC;IAE7C,OAAO,cAAc,CAAC,UAAU,CAAC,IAAI,CACpC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,IAAI,KAAK,QAAQ,IAAI,IAAI,CAAC,WAAW,EAAE,cAAc,KAAK,IAAI,CAC7E,CAAC;AACH,CAAC;AAEY,QAAA,iBAAiB,GAAkB;IAC/C,QAAQ,EAAE,CAAC,GAAG,CAAC;IACf,SAAS,EAAE,CAAC,GAAG,EAAE,EAAE,CAAC,aAAa,CAAC,GAAG,CAAC,cAAc,CAAC;IACrD,OAAO,EAAE;;;;;;;;;;;;;;;;;+DAiBqD;CAC9D,CAAC"}

package/dist/prompts/chains/parameter-updater/guides/tool-nodes.d.ts

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

package/dist/prompts/chains/parameter-updater/guides/tool-nodes.js

@@ -1,76 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.TOOL_NODES_GUIDE = void 0;
-exports.TOOL_NODES_GUIDE = {
-    patterns: ['*Tool'],
-    content: `
-## CRITICAL: $fromAI Expression Support for Tool Nodes
-
-Tool nodes (nodes ending with "Tool" like Gmail Tool, Google Calendar Tool, etc.) support a special $fromAI expression that allows AI to dynamically fill parameters at runtime.
-
-### When to Use $fromAI
-- ONLY available in tool nodes (node types ending with "Tool")
-- Use when the AI should determine the value based on context
-- Ideal for parameters that vary based on user input or conversation context
-
-### $fromAI Syntax
-\`={{ $fromAI('key', 'description', 'type', defaultValue) }}\`
-
-### Parameters
-- key: Unique identifier (1-64 chars, alphanumeric/underscore/hyphen)
-- description: Optional description for the AI (use empty string '' if not needed)
-- type: 'string' | 'number' | 'boolean' | 'json' (defaults to 'string')
-- defaultValue: Optional fallback value
-
-### Tool Node Examples
-
-#### Gmail Tool - Sending Email
-{
-  "sendTo": "={{ $fromAI('to') }}",
-  "subject": "={{ $fromAI('subject') }}",
-  "message": "={{ $fromAI('message_html') }}"
-}
-
-#### Google Calendar Tool - Filtering Events
-{
-  "timeMin": "={{ $fromAI('After', '', 'string') }}",
-  "timeMax": "={{ $fromAI('Before', '', 'string') }}"
-}
-
-### Mixed Usage Examples
-You can combine $fromAI with regular text:
-- "Subject: {{ $fromAI('subject') }} - Automated"
-- "Dear {{ $fromAI('recipientName', 'Customer name', 'string', 'Customer') }},"
-
-### Important Rules
-1. ONLY use $fromAI in tool nodes (check if node type ends with "Tool")
-2. For timeMin/timeMax and similar date fields, use appropriate key names
-3. The AI will fill these values based on context during execution
-4. Don't use $fromAI in regular nodes like Set, IF, HTTP Request, etc.
-
-## Tool Node Parameter Guidelines
-
-### Identifying Tool Nodes
-1. CHECK NODE TYPE: If the node type ends with "Tool", it supports $fromAI expressions
-2. COMMON TOOL NODES:
-   - Gmail Tool (gmailTool): to, subject, message → use $fromAI
-   - Google Calendar Tool (googleCalendarTool): timeMin, timeMax → use $fromAI
-   - Slack Tool (slackTool): channel, message → use $fromAI
-   - Microsoft Teams Tool: channel, message → use $fromAI
-   - Telegram Tool: chatId, text → use $fromAI
-   - Other communication/document tools: content fields → use $fromAI
-
-### When to Use $fromAI in Tool Nodes
-1. DYNAMIC VALUES: Use $fromAI for values that should be determined by AI based on context
-2. USER INPUT FIELDS: Recipients, subjects, messages, date ranges
-3. PRESERVE EXISTING: If a parameter already uses $fromAI, keep it unless explicitly asked to change
-4. DATE/TIME FIELDS: Use descriptive key names for clarity
-
-### Tool Node Parameter Patterns
-- Email recipients: "={{ $fromAI('to') }}"
-- Email subjects: "={{ $fromAI('subject') }}"
-- Message content: "={{ $fromAI('message_html') }}" or "={{ $fromAI('message') }}"
-- Date ranges: "={{ $fromAI('After', '', 'string') }}"
-- Channel IDs: "={{ $fromAI('channel') }}"`,
-};
-//# sourceMappingURL=tool-nodes.js.map

package/dist/prompts/chains/parameter-updater/guides/tool-nodes.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"tool-nodes.js","sourceRoot":"","sources":["../../../../../src/prompts/chains/parameter-updater/guides/tool-nodes.ts"],"names":[],"mappings":";;;AAEa,QAAA,gBAAgB,GAAkB;IAC9C,QAAQ,EAAE,CAAC,OAAO,CAAC;IACnB,OAAO,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;2CAoEiC;CAC1C,CAAC"}

package/dist/prompts/shared/node-guidance/structured-output-parser.d.ts

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

package/dist/prompts/shared/node-guidance/structured-output-parser.js

@@ -1,35 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.structuredOutputParser = void 0;
-exports.structuredOutputParser = {
-    nodeType: '@n8n/n8n-nodes-langchain.outputParserStructured',
-    usage: `Search for "Structured Output Parser" (@n8n/n8n-nodes-langchain.outputParserStructured) when:
-- AI output will be used programmatically (conditions, formatting, database storage, API calls)
-- AI needs to extract specific fields (e.g., score, category, priority, action items)
-- AI needs to classify/categorize data into defined categories
-- Downstream nodes need to access specific fields from AI response (e.g., $json.score, $json.category)
-- Output will be displayed in a formatted way (e.g., HTML email with specific sections)
-- Data needs validation against a schema before processing
-
-- Always use search_nodes to find the exact node names and versions - NEVER guess versions`,
-    connections: `When Discovery results include AI Agent or Structured Output Parser:
-1. Create the Structured Output Parser node
-2. Set AI Agent's hasOutputParser: true in initialParameters
-3. Connect: Structured Output Parser → AI Agent (ai_outputParser connection)`,
-    configuration: `WHEN TO SET hasOutputParser: true on AI Agent:
-- Discovery found Structured Output Parser node → MUST set hasOutputParser: true
-- AI output will be used in conditions (IF/Switch nodes checking $json.field)
-- AI output will be formatted/displayed (HTML emails, reports with specific sections)
-- AI output will be stored in database/data tables with specific fields
-- AI is classifying, scoring, or extracting specific data fields`,
-    recommendation: `For AI-generated structured data, prefer Structured Output Parser nodes over Code nodes.
-Why: Purpose-built parsers are more reliable and handle edge cases better than custom code.
-
-For binary file data, use Extract From File node to extract content from files before processing.
-
-Use Code nodes only for:
-- Simple string manipulations
-- Already structured data (JSON, CSV)
-- Custom business logic beyond parsing`,
-};
-//# sourceMappingURL=structured-output-parser.js.map

package/dist/prompts/shared/node-guidance/structured-output-parser.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"structured-output-parser.js","sourceRoot":"","sources":["../../../../src/prompts/shared/node-guidance/structured-output-parser.ts"],"names":[],"mappings":";;;AAEa,QAAA,sBAAsB,GAAiB;IACnD,QAAQ,EAAE,iDAAiD;IAE3D,KAAK,EAAE;;;;;;;;2FAQmF;IAE1F,WAAW,EAAE;;;6EAG+D;IAE5E,aAAa,EAAE;;;;;iEAKiD;IAEhE,cAAc,EAAE;;;;;;;;uCAQsB;CACtC,CAAC"}

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

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

package/dist/prompts/shared/node-guidance/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/shared/node-guidance/webhook.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"webhook.js","sourceRoot":"","sources":["../../../../src/prompts/shared/node-guidance/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"}

package/dist/prompts/shared/node-recommendations/audio-generation.d.ts

@@ -1,2 +0,0 @@
-import { type NodeRecommendationDocument } from '../../../types/node-recommendations';
-export declare const audioGenerationRecommendation: NodeRecommendationDocument;

package/dist/prompts/shared/node-recommendations/audio-generation.js

@@ -1,18 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.audioGenerationRecommendation = void 0;
-const node_recommendations_1 = require("../../../types/node-recommendations");
-exports.audioGenerationRecommendation = {
-    category: node_recommendations_1.RecommendationCategory.AUDIO_GENERATION,
-    version: '1.0.0',
-    recommendation: {
-        defaultNode: '@n8n/n8n-nodes-langchain.openAi',
-        operations: [
-            'Generate Audio: Create speech from text using OpenAI TTS',
-            'Transcribe a Recording: Convert audio to text using Whisper',
-            'Translate a Recording: Transcribe and translate audio to English using Whisper',
-        ],
-        reasoning: "OpenAI provides comprehensive audio capabilities: TTS for speech generation, Whisper for transcription and translation. Prefer OpenAI when user doesn't specify a provider.",
-    },
-};
-//# sourceMappingURL=audio-generation.js.map

package/dist/prompts/shared/node-recommendations/audio-generation.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"audio-generation.js","sourceRoot":"","sources":["../../../../src/prompts/shared/node-recommendations/audio-generation.ts"],"names":[],"mappings":";;;AAAA,uEAGsC;AAEzB,QAAA,6BAA6B,GAA+B;IACxE,QAAQ,EAAE,6CAAsB,CAAC,gBAAgB;IACjD,OAAO,EAAE,OAAO;IAChB,cAAc,EAAE;QACf,WAAW,EAAE,iCAAiC;QAC9C,UAAU,EAAE;YACX,0DAA0D;YAC1D,6DAA6D;YAC7D,gFAAgF;SAChF;QACD,SAAS,EACR,6KAA6K;KAC9K;CACD,CAAC"}

package/dist/prompts/shared/node-recommendations/image-generation.d.ts

@@ -1,2 +0,0 @@
-import { type NodeRecommendationDocument } from '../../../types/node-recommendations';
-export declare const imageGenerationRecommendation: NodeRecommendationDocument;

package/dist/prompts/shared/node-recommendations/image-generation.js

@@ -1,18 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.imageGenerationRecommendation = void 0;
-const node_recommendations_1 = require("../../../types/node-recommendations");
-exports.imageGenerationRecommendation = {
-    category: node_recommendations_1.RecommendationCategory.IMAGE_GENERATION,
-    version: '1.0.0',
-    recommendation: {
-        defaultNode: '@n8n/n8n-nodes-langchain.openAi',
-        operations: [
-            'Analyze Image: Analyze and describe image content using GPT-4 Vision',
-            'Generate an Image: Create images from text prompts using DALL-E',
-            'Edit Image: Modify existing images using DALL-E',
-        ],
-        reasoning: "OpenAI provides comprehensive image capabilities: DALL-E for generation/editing, GPT-4 Vision for analysis. Prefer OpenAI when user doesn't specify a provider.",
-    },
-};
-//# sourceMappingURL=image-generation.js.map

package/dist/prompts/shared/node-recommendations/image-generation.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"image-generation.js","sourceRoot":"","sources":["../../../../src/prompts/shared/node-recommendations/image-generation.ts"],"names":[],"mappings":";;;AAAA,uEAGsC;AAEzB,QAAA,6BAA6B,GAA+B;IACxE,QAAQ,EAAE,6CAAsB,CAAC,gBAAgB;IACjD,OAAO,EAAE,OAAO;IAChB,cAAc,EAAE;QACf,WAAW,EAAE,iCAAiC;QAC9C,UAAU,EAAE;YACX,sEAAsE;YACtE,iEAAiE;YACjE,iDAAiD;SACjD;QACD,SAAS,EACR,iKAAiK;KAClK;CACD,CAAC"}

package/dist/prompts/shared/node-recommendations/text-manipulation.d.ts

@@ -1,2 +0,0 @@
-import { type NodeRecommendationDocument } from '../../../types/node-recommendations';
-export declare const textManipulationRecommendation: NodeRecommendationDocument;

package/dist/prompts/shared/node-recommendations/text-manipulation.js

@@ -1,27 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.textManipulationRecommendation = void 0;
-const node_recommendations_1 = require("../../../types/node-recommendations");
-exports.textManipulationRecommendation = {
-    category: node_recommendations_1.RecommendationCategory.TEXT_MANIPULATION,
-    version: '1.0.0',
-    recommendation: {
-        defaultNode: '@n8n/n8n-nodes-langchain.agent',
-        operations: [
-            'Text summarization',
-            'Content analysis and extraction',
-            'Classification and categorization',
-            'Chat and conversational AI',
-            'Content generation and writing',
-        ],
-        reasoning: 'The AI Agent node is the default for text manipulation tasks. New users receive free OpenAI credits. Do NOT use provider-specific nodes directly.',
-        connectedNodes: [
-            {
-                nodeType: '@n8n/n8n-nodes-langchain.lmChatOpenAi',
-                connectionType: 'ai_languageModel',
-                description: 'Required chat model for the AI Agent',
-            },
-        ],
-    },
-};
-//# sourceMappingURL=text-manipulation.js.map

package/dist/prompts/shared/node-recommendations/text-manipulation.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"text-manipulation.js","sourceRoot":"","sources":["../../../../src/prompts/shared/node-recommendations/text-manipulation.ts"],"names":[],"mappings":";;;AAAA,uEAGsC;AAEzB,QAAA,8BAA8B,GAA+B;IACzE,QAAQ,EAAE,6CAAsB,CAAC,iBAAiB;IAClD,OAAO,EAAE,OAAO;IAChB,cAAc,EAAE;QACf,WAAW,EAAE,gCAAgC;QAC7C,UAAU,EAAE;YACX,oBAAoB;YACpB,iCAAiC;YACjC,mCAAmC;YACnC,4BAA4B;YAC5B,gCAAgC;SAChC;QACD,SAAS,EACR,mJAAmJ;QACpJ,cAAc,EAAE;YACf;gBACC,QAAQ,EAAE,uCAAuC;gBACjD,cAAc,EAAE,kBAAkB;gBAClC,WAAW,EAAE,sCAAsC;aACnD;SACD;KACD;CACD,CAAC"}

package/dist/prompts/shared/node-recommendations/utils/format-recommendation.d.ts

@@ -1,2 +0,0 @@
-import type { NodeRecommendation } from '../../../../types';
-export declare function formatRecommendation(rec: NodeRecommendation): string;

package/dist/prompts/shared/node-recommendations/utils/format-recommendation.js

@@ -1,24 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.formatRecommendation = formatRecommendation;
-const builder_1 = require("../../../../prompts/builder");
-function formatRecommendation(rec) {
-    const builder = (0, builder_1.prompt)()
-        .section('default_node', rec.defaultNode)
-        .section('operations', rec.operations.map((op) => `- ${op}`).join('\n'))
-        .section('reasoning', rec.reasoning);
-    if (rec.connectedNodes && rec.connectedNodes.length > 0) {
-        const connectedContent = rec.connectedNodes
-            .map((cn) => {
-            const desc = cn.description ? ` - ${cn.description}` : '';
-            return `- ${cn.nodeType} (connection: ${cn.connectionType})${desc}`;
-        })
-            .join('\n');
-        builder.section('connected_nodes', connectedContent);
-    }
-    if (rec.note) {
-        builder.section('note', rec.note);
-    }
-    return builder.build();
-}
-//# sourceMappingURL=format-recommendation.js.map

package/dist/prompts/shared/node-recommendations/utils/format-recommendation.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"format-recommendation.js","sourceRoot":"","sources":["../../../../../src/prompts/shared/node-recommendations/utils/format-recommendation.ts"],"names":[],"mappings":";;AAMA,oDAuBC;AA7BD,+CAA2C;AAM3C,SAAgB,oBAAoB,CAAC,GAAuB;IAC3D,MAAM,OAAO,GAAG,IAAA,gBAAM,GAAE;SACtB,OAAO,CAAC,cAAc,EAAE,GAAG,CAAC,WAAW,CAAC;SACxC,OAAO,CAAC,YAAY,EAAE,GAAG,CAAC,UAAU,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,KAAK,EAAE,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;SACvE,OAAO,CAAC,WAAW,EAAE,GAAG,CAAC,SAAS,CAAC,CAAC;IAGtC,IAAI,GAAG,CAAC,cAAc,IAAI,GAAG,CAAC,cAAc,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QACzD,MAAM,gBAAgB,GAAG,GAAG,CAAC,cAAc;aACzC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE;YACX,MAAM,IAAI,GAAG,EAAE,CAAC,WAAW,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,WAAW,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;YAC1D,OAAO,KAAK,EAAE,CAAC,QAAQ,iBAAiB,EAAE,CAAC,cAAc,IAAI,IAAI,EAAE,CAAC;QACrE,CAAC,CAAC;aACD,IAAI,CAAC,IAAI,CAAC,CAAC;QACb,OAAO,CAAC,OAAO,CAAC,iBAAiB,EAAE,gBAAgB,CAAC,CAAC;IACtD,CAAC;IAGD,IAAI,GAAG,CAAC,IAAI,EAAE,CAAC;QACd,OAAO,CAAC,OAAO,CAAC,MAAM,EAAE,GAAG,CAAC,IAAI,CAAC,CAAC;IACnC,CAAC;IAED,OAAO,OAAO,CAAC,KAAK,EAAE,CAAC;AACxB,CAAC"}

package/dist/prompts/shared/node-recommendations/video-generation.d.ts

@@ -1,2 +0,0 @@
-import { type NodeRecommendationDocument } from '../../../types/node-recommendations';
-export declare const videoGenerationRecommendation: NodeRecommendationDocument;

package/dist/prompts/shared/node-recommendations/video-generation.js

@@ -1,15 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.videoGenerationRecommendation = void 0;
-const node_recommendations_1 = require("../../../types/node-recommendations");
-exports.videoGenerationRecommendation = {
-    category: node_recommendations_1.RecommendationCategory.VIDEO_GENERATION,
-    version: '1.0.0',
-    recommendation: {
-        defaultNode: '@n8n/n8n-nodes-langchain.openAi',
-        operations: ['Generate a Video: Create videos from text prompts using Sora'],
-        reasoning: "OpenAI Sora is the default for video generation. Prefer OpenAI when user doesn't specify a provider.",
-        note: 'Video generation may require async processing with Wait nodes due to longer generation times.',
-    },
-};
-//# sourceMappingURL=video-generation.js.map

package/dist/prompts/shared/node-recommendations/video-generation.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"video-generation.js","sourceRoot":"","sources":["../../../../src/prompts/shared/node-recommendations/video-generation.ts"],"names":[],"mappings":";;;AAAA,uEAGsC;AAEzB,QAAA,6BAA6B,GAA+B;IACxE,QAAQ,EAAE,6CAAsB,CAAC,gBAAgB;IACjD,OAAO,EAAE,OAAO;IAChB,cAAc,EAAE;QACf,WAAW,EAAE,iCAAiC;QAC9C,UAAU,EAAE,CAAC,8DAA8D,CAAC;QAC5E,SAAS,EACR,sGAAsG;QACvG,IAAI,EAAE,+FAA+F;KACrG;CACD,CAAC"}

package/dist/shared/code-builder-and-mcp-prompt-constants.d.ts

@@ -1,3 +0,0 @@
-export declare const EXPRESSION_REFERENCE = "Available variables inside `expr('{{ ... }}')`:\n\n- `$json` \u2014 current item's JSON data from the immediate predecessor node\n- `$('NodeName').item.json` \u2014 access any node's output by name\n- `$input.first()` \u2014 first item from immediate predecessor\n- `$input.all()` \u2014 all items from immediate predecessor\n- `$input.item` \u2014 current item being processed\n- `$binary` \u2014 binary data of current item from immediate predecessor\n- `$now` \u2014 current date/time (Luxon DateTime). Example: `$now.toISO()`\n- `$today` \u2014 start of today (Luxon DateTime). Example: `$today.plus(1, 'days')`\n- `$itemIndex` \u2014 index of current item being processed\n- `$runIndex` \u2014 current run index\n- `$execution.id` \u2014 unique execution ID\n- `$execution.mode` \u2014 'test' or 'production'\n- `$workflow.id` \u2014 workflow ID\n- `$workflow.name` \u2014 workflow name\n\nString composition \u2014 variables MUST always be inside `{{ }}`, never outside as JS variables:\n\n- `expr('Hello {{ $json.name }}, welcome!')` \u2014 variable embedded in text\n- `expr('Report for {{ $now.toFormat(\"MMMM d, yyyy\") }} - {{ $json.title }}')` \u2014 multiple variables with method call\n- `expr('{{ $json.firstName }} {{ $json.lastName }}')` \u2014 combining multiple fields\n- `expr('Total: {{ $json.items.length }} items, updated {{ $now.toISO() }}')` \u2014 expressions with method calls\n- `expr('Status: {{ $json.count > 0 ? \"active\" : \"empty\" }}')` \u2014 inline ternary\n\nDynamic data from other nodes \u2014 `$()` MUST always be inside `{{ }}`, never used as plain JavaScript:\n\n- WRONG: `expr('{{ ' + JSON.stringify($('Source').all().map(i => i.json.name)) + ' }}')` \u2014 $() outside {{ }}\n- CORRECT: `expr('{{ $(\"Source\").all().map(i => ({ option: i.json.name })) }}')` \u2014 $() inside {{ }}\n- CORRECT: `expr('{{ { \"fields\": [{ \"values\": $(\"Fetch Projects\").all().map(i => ({ option: i.json.name })) }] } }}')` \u2014 complex JSON inside {{ }}";
-export declare const ADDITIONAL_FUNCTIONS = "Additional SDK functions:\n\n- `placeholder('hint')` \u2014 marks a parameter value for user input. Use directly as the parameter value \u2014 never wrap in `expr()`, objects, or arrays.\n  Example: `parameters: { url: placeholder('Your API URL (e.g. https://api.example.com/v1)') }`\n\n- `sticky('content', nodes?, config?)` \u2014 creates a sticky note on the canvas.\n  Example: `sticky('## Data Processing', [httpNode, setNode], { color: 2 })`\n\n- `.output(n)` \u2014 selects a specific output index for multi-output nodes. IF and Switch have dedicated methods (`onTrue/onFalse`, `onCase`), but `.output(n)` works as a generic alternative.\n  Example: `classifier.output(1).to(categoryB)`\n\n- `.onError(handler)` \u2014 connects a node's error output to a handler node. Requires `onError: 'continueErrorOutput'` in the node config.\n  Example: `httpNode.onError(errorHandler)` (with `config: { onError: 'continueErrorOutput' }`)\n\n- Additional subnode factories (all follow the same pattern as `languageModel()` and `tool()`):\n  `memory()`, `outputParser()`, `embeddings()`, `vectorStore()`, `retriever()`, `documentLoader()`, `textSplitter()`";
-export declare const WORKFLOW_RULES = "Follow these rules strictly when generating workflows:\n\n1. **Always use newCredential() for authentication**\n   - When a node needs credentials, always use `newCredential('Name')` in the credentials config\n   - NEVER use placeholder strings, fake API keys, or hardcoded auth values\n   - Example: `credentials: { slackApi: newCredential('Slack Bot') }`\n   - The credential type must match what the node expects";

package/dist/shared/code-builder-and-mcp-prompt-constants.js

@@ -1,57 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.WORKFLOW_RULES = exports.ADDITIONAL_FUNCTIONS = exports.EXPRESSION_REFERENCE = void 0;
-exports.EXPRESSION_REFERENCE = `Available variables inside \`expr('{{ ... }}')\`:
-
-- \`$json\` — current item's JSON data from the immediate predecessor node
-- \`$('NodeName').item.json\` — access any node's output by name
-- \`$input.first()\` — first item from immediate predecessor
-- \`$input.all()\` — all items from immediate predecessor
-- \`$input.item\` — current item being processed
-- \`$binary\` — binary data of current item from immediate predecessor
-- \`$now\` — current date/time (Luxon DateTime). Example: \`$now.toISO()\`
-- \`$today\` — start of today (Luxon DateTime). Example: \`$today.plus(1, 'days')\`
-- \`$itemIndex\` — index of current item being processed
-- \`$runIndex\` — current run index
-- \`$execution.id\` — unique execution ID
-- \`$execution.mode\` — 'test' or 'production'
-- \`$workflow.id\` — workflow ID
-- \`$workflow.name\` — workflow name
-
-String composition — variables MUST always be inside \`{{ }}\`, never outside as JS variables:
-
-- \`expr('Hello {{ $json.name }}, welcome!')\` — variable embedded in text
-- \`expr('Report for {{ $now.toFormat("MMMM d, yyyy") }} - {{ $json.title }}')\` — multiple variables with method call
-- \`expr('{{ $json.firstName }} {{ $json.lastName }}')\` — combining multiple fields
-- \`expr('Total: {{ $json.items.length }} items, updated {{ $now.toISO() }}')\` — expressions with method calls
-- \`expr('Status: {{ $json.count > 0 ? "active" : "empty" }}')\` — inline ternary
-
-Dynamic data from other nodes — \`$()\` MUST always be inside \`{{ }}\`, never used as plain JavaScript:
-
-- WRONG: \`expr('{{ ' + JSON.stringify($('Source').all().map(i => i.json.name)) + ' }}')\` — $() outside {{ }}
-- CORRECT: \`expr('{{ $("Source").all().map(i => ({ option: i.json.name })) }}')\` — $() inside {{ }}
-- CORRECT: \`expr('{{ { "fields": [{ "values": $("Fetch Projects").all().map(i => ({ option: i.json.name })) }] } }}')\` — complex JSON inside {{ }}`;
-exports.ADDITIONAL_FUNCTIONS = `Additional SDK functions:
-
-- \`placeholder('hint')\` — marks a parameter value for user input. Use directly as the parameter value — never wrap in \`expr()\`, objects, or arrays.
-  Example: \`parameters: { url: placeholder('Your API URL (e.g. https://api.example.com/v1)') }\`
-
-- \`sticky('content', nodes?, config?)\` — creates a sticky note on the canvas.
-  Example: \`sticky('## Data Processing', [httpNode, setNode], { color: 2 })\`
-
-- \`.output(n)\` — selects a specific output index for multi-output nodes. IF and Switch have dedicated methods (\`onTrue/onFalse\`, \`onCase\`), but \`.output(n)\` works as a generic alternative.
-  Example: \`classifier.output(1).to(categoryB)\`
-
-- \`.onError(handler)\` — connects a node's error output to a handler node. Requires \`onError: 'continueErrorOutput'\` in the node config.
-  Example: \`httpNode.onError(errorHandler)\` (with \`config: { onError: 'continueErrorOutput' }\`)
-
-- Additional subnode factories (all follow the same pattern as \`languageModel()\` and \`tool()\`):
-  \`memory()\`, \`outputParser()\`, \`embeddings()\`, \`vectorStore()\`, \`retriever()\`, \`documentLoader()\`, \`textSplitter()\``;
-exports.WORKFLOW_RULES = `Follow these rules strictly when generating workflows:
-
-1. **Always use newCredential() for authentication**
-   - When a node needs credentials, always use \`newCredential('Name')\` in the credentials config
-   - NEVER use placeholder strings, fake API keys, or hardcoded auth values
-   - Example: \`credentials: { slackApi: newCredential('Slack Bot') }\`
-   - The credential type must match what the node expects`;
-//# sourceMappingURL=code-builder-and-mcp-prompt-constants.js.map

package/dist/shared/code-builder-and-mcp-prompt-constants.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"code-builder-and-mcp-prompt-constants.js","sourceRoot":"","sources":["../../src/shared/code-builder-and-mcp-prompt-constants.ts"],"names":[],"mappings":";;;AAca,QAAA,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;qJA6BiH,CAAC;AAKzI,QAAA,oBAAoB,GAAG;;;;;;;;;;;;;;;mIAe+F,CAAC;AAKvH,QAAA,cAAc,GAAG;;;;;;0DAM4B,CAAC"}

package/dist/tools/best-practices/chatbot.d.ts

@@ -1,7 +0,0 @@
-import type { BestPracticesDocument } from '../../types/best-practices';
-export declare class ChatbotBestPractices implements BestPracticesDocument {
-    readonly technique: "chatbot";
-    readonly version = "1.0.0";
-    private readonly documentation;
-    getDocumentation(): string;
-}