================================================================================ WORKFLOW: Batch Process Prompts with Anthropic Claude API ================================================================================ 📋 BASIC INFORMATION ------------------------------ ID: 3409 Name: Batch Process Prompts with Anthropic Claude API Total Views: 959 Created At: 2025-04-02T19:20:04.824Z Purchase URL: None 👤 AUTHOR INFORMATION ------------------------------ Name: Greg Evseev Username: greg Verified: ✅ Yes Bio: 15+ years in AI/ML development & integration. Now specializing in establishing ISO 42001-compliant AI management systems. Background includes AI/ML research, system development, AI governance, and ISO 42001 Lead Auditor training (in progress). Helping organizations: ✓ Evaluate AI maturity & governance ✓ Implement ISO 42001 systems ✓ Bridge technical & regulatory requirements ✓ Design practical AI governance frameworks Expertise: AI Risk Assessment, Compliance Strategy, Technical Due Diligence. Links: https://www.linkedin.com/in/aimsgreg 📝 DESCRIPTION ------------------------------ This workflow template provides a robust solution for efficiently sending multiple prompts to Anthropic's Claude models in a single batch request and retrieving the results. It leverages the Anthropic Batch API endpoint (/v1/messages/batches) for optimized processing and outputs each result as a separate item. Core Functionality & Example Usage Included This template includes: The Core Batch Processing Workflow: Designed to be called by another n8n workflow. An Example Usage Workflow: A separate branch demonstrating how to prepare data and trigger the core workflow, including examples using simple strings and n8n's Langchain Chat Memory nodes. Who is this for? This template is designed for: Developers, data scientists, and researchers** who need to process large volumes of text prompts using Claude models via n8n. Content creators** looking to generate multiple pieces of content (e.g., summaries, Q&As, creative text) based on different inputs simultaneously. n8n users** who want to automate interactions with the Anthropic API beyond single requests, improve efficiency, and integrate batch processing into larger automation sequences. Anyone needing to perform bulk text generation or analysis tasks with Claude programmatically. What problem does this workflow solve? Sending prompts to language models one by one can be slow and inefficient, especially when dealing with hundreds or thousands of requests. This workflow addresses that by: Batching:** Grouping multiple prompts into a single API call to Anthropic's dedicated batch endpoint (/v1/messages/batches). Efficiency:** Significantly reducing the time required compared to sequential processing. Scalability:** Handling large numbers of prompts (up to API limits) systematically. Automation:** Providing a ready-to-use, callable n8n structure for batch interactions with Claude. Structured Output:** Parsing the results and outputting each individual prompt's result as a separate n8n item. Use Cases: Bulk content generation (e.g., product descriptions, summaries). Large-scale question answering based on different contexts. Sentiment analysis or data extraction across multiple text snippets. Running the same prompt against many different inputs for research or testing. What the Core Workflow does (Triggered by the 'When Executed by Another Workflow' node) Receive Input: The workflow starts when called by another workflow (e.g., using the 'Execute Workflow' node). It expects input data containing: anthropic-version (string, e.g., "2023-06-01") requests (JSON array, where each object represents a single prompt request conforming to the Anthropic Batch API schema). Submit Batch Job: Sends the formatted requests data via POST to the Anthropic API /v1/messages/batches endpoint to create a new batch job. Requires Anthropic credentials. Wait & Poll: Enters a loop: Checks if the processing_status of the batch job is ended. If not ended, it waits for a set interval (10 seconds by default in the 'Batch Status Poll Interval' node). It then checks the batch job status again via GET to /v1/messages/batches/{batch_id}. Requires Anthropic credentials. This loop continues until the status is ended. Retrieve Results: Once the batch job is complete, it fetches the results file by making a GET request to the results_url provided in the batch status response. Requires Anthropic credentials. Parse Results: The results are typically returned in JSON Lines (.jsonl) format. The 'Parse response' Code node splits the response text by newlines and parses each line into a separate JSON object, storing them in an array field (e.g., parsed). Split Output: The 'Split Out Parsed Results' node takes the array of parsed results and outputs each result object as an individual item from the workflow. Prerequisites An active n8n instance (Cloud or self-hosted). An Anthropic API account with access granted to Claude models and the Batch API. Your Anthropic API Key. Basic understanding of n8n concepts (nodes, workflows, credentials, expressions, 'Execute Workflow' node). Familiarity with JSON data structures for providing input prompts and understanding the output. Understanding of the Anthropic Batch API request/response structure. (For Example Usage Branch) Familiarity with n8n's Langchain nodes (@n8n/n8n-nodes-langchain) if you plan to adapt that part. Setup Import Template: Add this template to your n8n instance. Configure Credentials: Navigate to the 'Credentials' section in your n8n instance. Click 'Add Credential'. Search for 'Anthropic' and select the Anthropic API credential type. Enter your Anthropic API Key and save the credential (e.g., name it "Anthropic account"). Assign Credentials: Open the workflow and locate the three HTTP Request nodes in the core workflow: Submit batch Check batch status Get results In each of these nodes, select the Anthropic credential you just configured from the 'Credential for Anthropic API' dropdown. Review Input Format: Understand the required input structure for the When Executed by Another Workflow trigger node. The primary inputs are anthropic-version (string) and requests (array). Refer to the Sticky Notes in the template and the Anthropic Batch API documentation for the exact schema required within the requests array. Activate Workflow: Save and activate the core workflow so it can be called by other workflows. ➡️ Quick Start & Input/Output Examples: Look for the Sticky Notes within the workflow canvas! They provide crucial information, including examples of the required input JSON structure and the expected output format. How to customize this workflow Input Source:* The core workflow is designed to be called. You will build *another workflow that prepares the anthropic-version and requests array and then uses the 'Execute Workflow' node to trigger this template. The included example branch shows how to prepare this data. Model Selection & Parameters:* Model (claude-3-opus-20240229, etc.), max_tokens, temperature, and other parameters are defined *within each object inside the requests array you pass to the workflow trigger. You configure these in the workflow calling this template. Polling Interval:** Modify the 'Wait' node ('Batch Status Poll Interval') duration if you need faster or slower status checks (default is 10 seconds). Be mindful of potential rate limits. Parsing Logic:** If Anthropic changes the result format or you have specific needs, modify the Javascript code within the 'Parse response' Code node. Error Handling:** Enhance the workflow with more specific error handling for API failures (e.g., using 'Error Trigger' or checking HTTP status codes) or batch processing issues (batch.status === 'failed'). Output Processing:* In the workflow that *calls this template, add nodes after the 'Execute Workflow' node to process the individual result items returned (e.g., save to a database, spreadsheet, send notifications). Example Usage Branch (Manual Trigger) This template also contains a separate branch starting with the Run example Manual Trigger node. Purpose:** This branch demonstrates how to construct the necessary anthropic-version and requests array payload. Methods Shown:** It includes steps for: Creating a request object from a simple query string. Creating a request object using data from n8n's Langchain Chat Memory nodes (@n8n/n8n-nodes-langchain). Execution:** It merges these examples, constructs the final payload, and then uses the Execute Workflow node to call the main batch processing logic described above. It finishes by filtering the results for demonstration. Note:** This branch is for demonstration and testing. You would typically build your own data preparation logic in a separate workflow. The use of Langchain nodes is optional for the core batch functionality. Notes API Limits:** According to the Anthropic API documentation, batches can contain up to 100,000 requests and be up to 256 MB in total size. Ensure your n8n instance has sufficient resources for large batches. API Costs:** Using the Anthropic API, including the Batch API, incurs costs based on token usage. Monitor your usage via the Anthropic dashboard. Completion Time:** Batch processing time depends on the number and complexity of prompts and current API load. The polling mechanism accounts for this variability. Versioning:** Always include the anthropic-version header in your requests, as shown in the workflow and examples. Refer to Anthropic API versioning documentation. 🔧 NODES USED ------------------------------ • HTTP Request - Categories: Core Nodes, Development • Code - Categories: Core Nodes, Development • Simple Memory - Categories: AI, Langchain • Chat Memory Manager - Categories: AI, Langchain Total Nodes: 4 📊 RAW DATA (JSON) ------------------------------ { "id": 3409, "name": "Batch Process Prompts with Anthropic Claude API", "totalViews": 959, "purchaseUrl": null, "user": { "id": 93555, "name": "Greg Evseev", "username": "greg", "bio": "15+ years in AI/ML development & integration. Now specializing in establishing ISO 42001-compliant AI management systems. Background includes AI/ML research, system development, AI governance, and ISO 42001 Lead Auditor training (in progress).\n\nHelping organizations:\n✓ Evaluate AI maturity & governance\n✓ Implement ISO 42001 systems\n✓ Bridge technical & regulatory requirements\n✓ Design practical AI governance frameworks\n\nExpertise: AI Risk Assessment, Compliance Strategy, Technical Due Diligence.", "verified": true, "links": "[\"https://www.linkedin.com/in/aimsgreg\"]", "avatar": "https://gravatar.com/avatar/a2532827cb048e2c6433b7d6c3bf075066d9fac93092eca13593902b502e75b1?r=pg&d=retro&size=200" }, "description": "This workflow template provides a robust solution for efficiently sending multiple prompts to Anthropic's Claude models in a single batch request and retrieving the results. It leverages the Anthropic Batch API endpoint (/v1/messages/batches) for optimized processing and outputs each result as a separate item.\n\nCore Functionality & Example Usage Included\n\nThis template includes:\nThe Core Batch Processing Workflow: Designed to be called by another n8n workflow.\nAn Example Usage Workflow: A separate branch demonstrating how to prepare data and trigger the core workflow, including examples using simple strings and n8n's Langchain Chat Memory nodes.\n\nWho is this for?\n\nThis template is designed for:\n\nDevelopers, data scientists, and researchers** who need to process large volumes of text prompts using Claude models via n8n.\nContent creators** looking to generate multiple pieces of content (e.g., summaries, Q&As, creative text) based on different inputs simultaneously.\nn8n users** who want to automate interactions with the Anthropic API beyond single requests, improve efficiency, and integrate batch processing into larger automation sequences.\nAnyone needing to perform bulk text generation or analysis tasks with Claude programmatically.\n\nWhat problem does this workflow solve?\n\nSending prompts to language models one by one can be slow and inefficient, especially when dealing with hundreds or thousands of requests. This workflow addresses that by:\n\nBatching:** Grouping multiple prompts into a single API call to Anthropic's dedicated batch endpoint (/v1/messages/batches).\nEfficiency:** Significantly reducing the time required compared to sequential processing.\nScalability:** Handling large numbers of prompts (up to API limits) systematically.\nAutomation:** Providing a ready-to-use, callable n8n structure for batch interactions with Claude.\nStructured Output:** Parsing the results and outputting each individual prompt's result as a separate n8n item.\n\nUse Cases:\n\nBulk content generation (e.g., product descriptions, summaries).\nLarge-scale question answering based on different contexts.\nSentiment analysis or data extraction across multiple text snippets.\nRunning the same prompt against many different inputs for research or testing.\n\nWhat the Core Workflow does\n\n(Triggered by the 'When Executed by Another Workflow' node)\n\nReceive Input: The workflow starts when called by another workflow (e.g., using the 'Execute Workflow' node). It expects input data containing:\n anthropic-version (string, e.g., \"2023-06-01\")\n requests (JSON array, where each object represents a single prompt request conforming to the Anthropic Batch API schema).\nSubmit Batch Job: Sends the formatted requests data via POST to the Anthropic API /v1/messages/batches endpoint to create a new batch job. Requires Anthropic credentials.\nWait & Poll: Enters a loop:\n Checks if the processing_status of the batch job is ended.\n If not ended, it waits for a set interval (10 seconds by default in the 'Batch Status Poll Interval' node).\n It then checks the batch job status again via GET to /v1/messages/batches/{batch_id}. Requires Anthropic credentials.\n This loop continues until the status is ended.\nRetrieve Results: Once the batch job is complete, it fetches the results file by making a GET request to the results_url provided in the batch status response. Requires Anthropic credentials.\nParse Results: The results are typically returned in JSON Lines (.jsonl) format. The 'Parse response' Code node splits the response text by newlines and parses each line into a separate JSON object, storing them in an array field (e.g., parsed).\nSplit Output: The 'Split Out Parsed Results' node takes the array of parsed results and outputs each result object as an individual item from the workflow.\n\nPrerequisites\n\nAn active n8n instance (Cloud or self-hosted).\nAn Anthropic API account with access granted to Claude models and the Batch API.\nYour Anthropic API Key.\nBasic understanding of n8n concepts (nodes, workflows, credentials, expressions, 'Execute Workflow' node).\nFamiliarity with JSON data structures for providing input prompts and understanding the output.\nUnderstanding of the Anthropic Batch API request/response structure.\n(For Example Usage Branch) Familiarity with n8n's Langchain nodes (@n8n/n8n-nodes-langchain) if you plan to adapt that part.\n\nSetup\n\nImport Template: Add this template to your n8n instance.\nConfigure Credentials:\n Navigate to the 'Credentials' section in your n8n instance.\n Click 'Add Credential'.\n Search for 'Anthropic' and select the Anthropic API credential type.\n Enter your Anthropic API Key and save the credential (e.g., name it \"Anthropic account\").\nAssign Credentials: Open the workflow and locate the three HTTP Request nodes in the core workflow:\n Submit batch\n Check batch status\n Get results\n In each of these nodes, select the Anthropic credential you just configured from the 'Credential for Anthropic API' dropdown.\nReview Input Format: Understand the required input structure for the When Executed by Another Workflow trigger node. The primary inputs are anthropic-version (string) and requests (array). Refer to the Sticky Notes in the template and the Anthropic Batch API documentation for the exact schema required within the requests array.\nActivate Workflow: Save and activate the core workflow so it can be called by other workflows.\n\n➡️ Quick Start & Input/Output Examples: Look for the Sticky Notes within the workflow canvas! They provide crucial information, including examples of the required input JSON structure and the expected output format.\n\nHow to customize this workflow\n\nInput Source:* The core workflow is designed to be called. You will build *another workflow that prepares the anthropic-version and requests array and then uses the 'Execute Workflow' node to trigger this template. The included example branch shows how to prepare this data.\nModel Selection & Parameters:* Model (claude-3-opus-20240229, etc.), max_tokens, temperature, and other parameters are defined *within each object inside the requests array you pass to the workflow trigger. You configure these in the workflow calling this template.\nPolling Interval:** Modify the 'Wait' node ('Batch Status Poll Interval') duration if you need faster or slower status checks (default is 10 seconds). Be mindful of potential rate limits.\nParsing Logic:** If Anthropic changes the result format or you have specific needs, modify the Javascript code within the 'Parse response' Code node.\nError Handling:** Enhance the workflow with more specific error handling for API failures (e.g., using 'Error Trigger' or checking HTTP status codes) or batch processing issues (batch.status === 'failed').\nOutput Processing:* In the workflow that *calls this template, add nodes after the 'Execute Workflow' node to process the individual result items returned (e.g., save to a database, spreadsheet, send notifications).\n\nExample Usage Branch (Manual Trigger)\n\nThis template also contains a separate branch starting with the Run example Manual Trigger node.\n\nPurpose:** This branch demonstrates how to construct the necessary anthropic-version and requests array payload.\nMethods Shown:** It includes steps for:\n Creating a request object from a simple query string.\n Creating a request object using data from n8n's Langchain Chat Memory nodes (@n8n/n8n-nodes-langchain).\nExecution:** It merges these examples, constructs the final payload, and then uses the Execute Workflow node to call the main batch processing logic described above. It finishes by filtering the results for demonstration.\nNote:** This branch is for demonstration and testing. You would typically build your own data preparation logic in a separate workflow. The use of Langchain nodes is optional for the core batch functionality.\n\nNotes\n\nAPI Limits:** According to the Anthropic API documentation, batches can contain up to 100,000 requests and be up to 256 MB in total size. Ensure your n8n instance has sufficient resources for large batches.\nAPI Costs:** Using the Anthropic API, including the Batch API, incurs costs based on token usage. Monitor your usage via the Anthropic dashboard.\nCompletion Time:** Batch processing time depends on the number and complexity of prompts and current API load. The polling mechanism accounts for this variability.\nVersioning:** Always include the anthropic-version header in your requests, as shown in the workflow and examples. Refer to Anthropic API versioning documentation.\n", "createdAt": "2025-04-02T19:20:04.824Z", "nodes": [ { "id": 19, "icon": "file:httprequest.svg", "name": "n8n-nodes-base.httpRequest", "codex": { "data": { "alias": [ "API", "Request", "URL", "Build", "cURL" ], "resources": { "generic": [ { "url": "https://n8n.io/blog/2021-the-year-to-automate-the-new-you-with-n8n/", "icon": "☀️", "label": "2021: The Year to Automate the New You with n8n" }, { "url": "https://n8n.io/blog/why-business-process-automation-with-n8n-can-change-your-daily-life/", "icon": "🧬", "label": "Why business process automation with n8n can change your daily life" }, { "url": "https://n8n.io/blog/automatically-pulling-and-visualizing-data-with-n8n/", "icon": "📈", "label": "Automatically pulling and visualizing data with n8n" }, { "url": "https://n8n.io/blog/learn-how-to-automatically-cross-post-your-content-with-n8n/", "icon": "✍️", "label": "Learn how to automatically cross-post your content with n8n" }, { "url": "https://n8n.io/blog/automatically-adding-expense-receipts-to-google-sheets-with-telegram-mindee-twilio-and-n8n/", "icon": "🧾", "label": "Automatically Adding Expense Receipts to Google Sheets with Telegram, Mindee, Twilio, and n8n" }, { "url": "https://n8n.io/blog/running-n8n-on-ships-an-interview-with-maranics/", "icon": "🛳", "label": "Running n8n on ships: An interview with Maranics" }, { "url": "https://n8n.io/blog/what-are-apis-how-to-use-them-with-no-code/", "icon": " 🪢", "label": "What are APIs and how to use them with no code" }, { "url": "https://n8n.io/blog/5-tasks-you-can-automate-with-notion-api/", "icon": "⚡️", "label": "5 tasks you can automate with the new Notion API " }, { "url": "https://n8n.io/blog/world-poetry-day-workflow/", "icon": "📜", "label": "Celebrating World Poetry Day with a daily poem in Telegram" }, { "url": "https://n8n.io/blog/automate-google-apps-for-productivity/", "icon": "💡", "label": "15 Google apps you can combine and automate to increase productivity" }, { "url": "https://n8n.io/blog/automate-designs-with-bannerbear-and-n8n/", "icon": "🎨", "label": "Automate Designs with Bannerbear and n8n" }, { "url": "https://n8n.io/blog/how-uproc-scraped-a-multi-page-website-with-a-low-code-workflow/", "icon": " 🕸️", "label": "How uProc scraped a multi-page website with a low-code workflow" }, { "url": "https://n8n.io/blog/building-an-expense-tracking-app-in-10-minutes/", "icon": "📱", "label": "Building an expense tracking app in 10 minutes" }, { "url": "https://n8n.io/blog/5-workflow-automations-for-mattermost-that-we-love-at-n8n/", "icon": "🤖", "label": "5 workflow automations for Mattermost that we love at n8n" }, { "url": "https://n8n.io/blog/how-to-use-the-http-request-node-the-swiss-army-knife-for-workflow-automation/", "icon": "🧰", "label": "How to use the HTTP Request Node - The Swiss Army Knife for Workflow Automation" }, { "url": "https://n8n.io/blog/learn-how-to-use-webhooks-with-mattermost-slash-commands/", "icon": "🦄", "label": "Learn how to use webhooks with Mattermost slash commands" }, { "url": "https://n8n.io/blog/how-a-membership-development-manager-automates-his-work-and-investments/", "icon": "📈", "label": "How a Membership Development Manager automates his work and investments" }, { "url": "https://n8n.io/blog/a-low-code-bitcoin-ticker-built-with-questdb-and-n8n-io/", "icon": "📈", "label": "A low-code bitcoin ticker built with QuestDB and n8n.io" }, { "url": "https://n8n.io/blog/how-to-set-up-a-ci-cd-pipeline-with-no-code/", "icon": "🎡", "label": "How to set up a no-code CI/CD pipeline with GitHub and TravisCI" }, { "url": "https://n8n.io/blog/automations-for-activists/", "icon": "✨", "label": "How Common Knowledge use workflow automation for activism" }, { "url": "https://n8n.io/blog/creating-scheduled-text-affirmations-with-n8n/", "icon": "🤟", "label": "Creating scheduled text affirmations with n8n" }, { "url": "https://n8n.io/blog/how-goomer-automated-their-operations-with-over-200-n8n-workflows/", "icon": "🛵", "label": "How Goomer automated their operations with over 200 n8n workflows" }, { "url": "https://n8n.io/blog/aws-workflow-automation/", "label": "7 no-code workflow automations for Amazon Web Services" } ], "primaryDocumentation": [ { "url": "https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/" } ] }, "categories": [ "Development", "Core Nodes" ], "nodeVersion": "1.0", "codexVersion": "1.0", "subcategories": { "Core Nodes": [ "Helpers" ] } } }, "group": "[\"output\"]", "defaults": { "name": "HTTP Request", "color": "#0004F5" }, "iconData": { "type": "file", "fileBuffer": "data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iNDAiIGhlaWdodD0iNDAiIHZpZXdCb3g9IjAgMCA0MCA0MCIgZmlsbD0ibm9uZSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIj4KPHBhdGggZmlsbC1ydWxlPSJldmVub2RkIiBjbGlwLXJ1bGU9ImV2ZW5vZGQiIGQ9Ik00MCAyMEM0MCA4Ljk1MzE0IDMxLjA0NjkgMCAyMCAwQzguOTUzMTQgMCAwIDguOTUzMTQgMCAyMEMwIDMxLjA0NjkgOC45NTMxNCA0MCAyMCA0MEMzMS4wNDY5IDQwIDQwIDMxLjA0NjkgNDAgMjBaTTIwIDM2Ljk0NThDMTguODg1MiAzNi45NDU4IDE3LjEzNzggMzUuOTY3IDE1LjQ5OTggMzIuNjk4NUMxNC43OTY0IDMxLjI5MTggMTQuMTk2MSAyOS41NDMxIDEzLjc1MjYgMjcuNjg0N0gyNi4xODk4QzI1LjgwNDUgMjkuNTQwMyAyNS4yMDQ0IDMxLjI5MDEgMjQuNTAwMiAzMi42OTg1QzIyLjg2MjIgMzUuOTY3IDIxLjExNDggMzYuOTQ1OCAyMCAzNi45NDU4Wk0xMi45MDY0IDIwQzEyLjkwNjQgMjEuNjA5NyAxMy4wMDg3IDIzLjE2NCAxMy4yMDAzIDI0LjYzMDVIMjYuNzk5N0MyNi45OTEzIDIzLjE2NCAyNy4wOTM2IDIxLjYwOTcgMjcuMDkzNiAyMEMyNy4wOTM2IDE4LjM5MDMgMjYuOTkxMyAxNi44MzYgMjYuNzk5NyAxNS4zNjk1SDEzLjIwMDNDMTMuMDA4NyAxNi44MzYgMTIuOTA2NCAxOC4zOTAzIDEyLjkwNjQgMjBaTTIwIDMuMDU0MTlDMjEuMTE0OSAzLjA1NDE5IDIyLjg2MjIgNC4wMzA3OCAyNC41MDAxIDcuMzAwMzlDMjUuMjA2NiA4LjcxNDA4IDI1LjgwNzIgMTAuNDA2NyAyNi4xOTIgMTIuMzE1M0gxMy43NTAxQzE0LjE5MzMgMTAuNDA0NyAxNC43OTQyIDguNzEyNTQgMTUuNDk5OCA3LjMwMDY0QzE3LjEzNzcgNC4wMzA4MyAxOC44ODUxIDMuMDU0MTkgMjAgMy4wNTQxOVpNMzAuMTQ3OCAyMEMzMC4xNDc4IDE4LjQwOTkgMzAuMDU0MyAxNi44NjE3IDI5LjgyMjcgMTUuMzY5NUgzNi4zMDQyQzM2LjcyNTIgMTYuODQyIDM2Ljk0NTggMTguMzk2NCAzNi45NDU4IDIwQzM2Ljk0NTggMjEuNjAzNiAzNi43MjUyIDIzLjE1OCAzNi4zMDQyIDI0LjYzMDVIMjkuODIyN0MzMC4wNTQzIDIzLjEzODMgMzAuMTQ3OCAyMS41OTAxIDMwLjE0NzggMjBaTTI2LjI3NjcgNC4yNTUxMkMyNy42MzY1IDYuMzYwMTkgMjguNzExIDkuMTMyIDI5LjM3NzQgMTIuMzE1M0gzNS4xMDQ2QzMzLjI1MTEgOC42NjggMzAuMTA3IDUuNzgzNDYgMjYuMjc2NyA0LjI1NTEyWk0xMC42MjI2IDEyLjMxNTNINC44OTI5M0M2Ljc1MTQ3IDguNjY3ODQgOS44OTM1MSA1Ljc4MzQxIDEzLjcyMzIgNC4yNTUxM0MxMi4zNjM1IDYuMzYwMjEgMTEuMjg5IDkuMTMyMDEgMTAuNjIyNiAxMi4zMTUzWk0zLjA1NDE5IDIwQzMuMDU0MTkgMjEuNjAzIDMuMjc3NDMgMjMuMTU3NSAzLjY5NDg0IDI0LjYzMDVIMTAuMTIxN0M5Ljk0NjE5IDIzLjE0MiA5Ljg1MjIyIDIxLjU5NDMgOS44NTIyMiAyMEM5Ljg1MjIyIDE4LjQwNTcgOS45NDYxOSAxNi44NTggMTAuMTIxNyAxNS4zNjk1SDMuNjk0ODRDMy4yNzc0MyAxNi44NDI1IDMuMDU0MTkgMTguMzk3IDMuMDU0MTkgMjBaTTI2LjI3NjYgMzUuNzQyN0MyNy42MzY1IDMzLjYzOTMgMjguNzExIDMwLjg2OCAyOS4zNzc0IDI3LjY4NDdIMzUuMTA0NkMzMy4yNTEgMzEuMzMyMiAzMC4xMDY4IDM0LjIxNzkgMjYuMjc2NiAzNS43NDI3Wk0xMy43MjM0IDM1Ljc0MjdDOS44OTM2OSAzNC4yMTc5IDYuNzUxNTUgMzEuMzMyNCA0Ljg5MjkzIDI3LjY4NDdIMTAuNjIyNkMxMS4yODkgMzAuODY4IDEyLjM2MzUgMzMuNjM5MyAxMy43MjM0IDM1Ljc0MjdaIiBmaWxsPSIjM0E0MkU5Ii8+Cjwvc3ZnPgo=" }, "displayName": "HTTP Request", "typeVersion": 4, "nodeCategories": [ { "id": 5, "name": "Development" }, { "id": 9, "name": "Core Nodes" } ] }, { "id": 834, "icon": "file:code.svg", "name": "n8n-nodes-base.code", "codex": { "data": { "alias": [ "cpde", "Javascript", "JS", "Python", "Script", "Custom Code", "Function" ], "details": "The Code node allows you to execute JavaScript in your workflow.", "resources": { "primaryDocumentation": [ { "url": "https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.code/" } ] }, "categories": [ "Development", "Core Nodes" ], "nodeVersion": "1.0", "codexVersion": "1.0", "subcategories": { "Core Nodes": [ "Helpers", "Data Transformation" ] } } }, "group": "[\"transform\"]", "defaults": { "name": "Code" }, "iconData": { "type": "file", "fileBuffer": "data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iNTEyIiBoZWlnaHQ9IjUxMiIgdmlld0JveD0iMCAwIDUxMiA1MTIiIGZpbGw9Im5vbmUiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyI+CjxnIGNsaXAtcGF0aD0idXJsKCNjbGlwMF8xMTcxXzQ0MSkiPgo8cGF0aCBkPSJNMTcwLjI4MyA0OEgxOTYuNUMyMDMuMTI3IDQ4IDIwOC41IDQyLjYyNzQgMjA4LjUgMzZWMTJDMjA4LjUgNS4zNzI1OCAyMDMuMTI3IDAgMTk2LjUgMEgxNzAuMjgzQzEyNi4xIDAgOTAuMjgzIDM1LjgxNzIgOTAuMjgzIDgwVjE3NkM5MC4yODMgMjA2LjkyOCA2NS4yMTA5IDIzMiAzNC4yODMgMjMySDIzQzE2LjM3MjYgMjMyIDExIDIzNy4zNzIgMTEgMjQ0VjI2OEMxMSAyNzQuNjI3IDE2LjM3MjQgMjgwIDIyLjk5OTYgMjgwTDM0LjI4MyAyODBDNjUuMjEwOSAyODAgOTAuMjgzIDMwNS4wNzIgOTAuMjgzIDMzNlY0NDBDOTAuMjgzIDQ3OS43NjQgMTIyLjUxOCA1MTIgMTYyLjI4MyA1MTJIMTk2LjVDMjAzLjEyNyA1MTIgMjA4LjUgNTA2LjYyNyAyMDguNSA1MDBWNDc2QzIwOC41IDQ2OS4zNzMgMjAzLjEyNyA0NjQgMTk2LjUgNDY0SDE2Mi4yODNDMTQ5LjAyOCA0NjQgMTM4LjI4MyA0NTMuMjU1IDEzOC4yODMgNDQwVjMzNkMxMzguMjgzIDMwOS4wMjIgMTI4LjAxMSAyODQuNDQzIDExMS4xNjQgMjY1Ljk2MUMxMDYuMTA5IDI2MC40MTYgMTA2LjEwOSAyNTEuNTg0IDExMS4xNjQgMjQ2LjAzOUMxMjguMDExIDIyNy41NTcgMTM4LjI4MyAyMDIuOTc4IDEzOC4yODMgMTc2VjgwQzEzOC4yODMgNjIuMzI2OSAxNTIuNjEgNDggMTcwLjI4MyA0OFoiIGZpbGw9IiNGRjk5MjIiLz4KPHBhdGggZD0iTTMwNSAzNkMzMDUgNDIuNjI3NCAzMTAuMzczIDQ4IDMxNyA0OEgzNDIuOTc5QzM2MC42NTIgNDggMzc0Ljk3OCA2Mi4zMjY5IDM3NC45NzggODBWMTc2QzM3NC45NzggMjAyLjk3OCAzODUuMjUxIDIyNy41NTcgNDAyLjA5OCAyNDYuMDM5QzQwNy4xNTMgMjUxLjU4NCA0MDcuMTUzIDI2MC40MTYgNDAyLjA5OCAyNjUuOTYxQzM4NS4yNTEgMjg0LjQ0MyAzNzQuOTc4IDMwOS4wMjIgMzc0Ljk3OCAzMzZWNDMyQzM3NC45NzggNDQ5LjY3MyAzNjAuNjUyIDQ2NCAzNDIuOTc5IDQ2NEgzMTdDMzEwLjM3MyA0NjQgMzA1IDQ2OS4zNzMgMzA1IDQ3NlY1MDBDMzA1IDUwNi42MjcgMzEwLjM3MyA1MTIgMzE3IDUxMkgzNDIuOTc5QzM4Ny4xNjEgNTEyIDQyMi45NzggNDc2LjE4MyA0MjIuOTc4IDQzMlYzMzZDNDIyLjk3OCAzMDUuMDcyIDQ0OC4wNTEgMjgwIDQ3OC45NzkgMjgwSDQ5MEM0OTYuNjI3IDI4MCA1MDIgMjc0LjYyOCA1MDIgMjY4VjI0NEM1MDIgMjM3LjM3MyA0OTYuNjI4IDIzMiA0OTAgMjMyTDQ3OC45NzkgMjMyQzQ0OC4wNTEgMjMyIDQyMi45NzggMjA2LjkyOCA0MjIuOTc4IDE3NlY4MEM0MjIuOTc4IDM1LjgxNzIgMzg3LjE2MSAwIDM0Mi45NzkgMEgzMTdDMzEwLjM3MyAwIDMwNSA1LjM3MjU4IDMwNSAxMlYzNloiIGZpbGw9IiNGRjk5MjIiLz4KPC9nPgo8ZGVmcz4KPGNsaXBQYXRoIGlkPSJjbGlwMF8xMTcxXzQ0MSI+CjxyZWN0IHdpZHRoPSI1MTIiIGhlaWdodD0iNTEyIiBmaWxsPSJ3aGl0ZSIvPgo8L2NsaXBQYXRoPgo8L2RlZnM+Cjwvc3ZnPgo=" }, "displayName": "Code", "typeVersion": 2, "nodeCategories": [ { "id": 5, "name": "Development" }, { "id": 9, "name": "Core Nodes" } ] }, { "id": 1163, "icon": "fa:database", "name": "@n8n/n8n-nodes-langchain.memoryBufferWindow", "codex": { "data": { "resources": { "primaryDocumentation": [ { "url": "https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorybufferwindow/" } ] }, "categories": [ "AI", "Langchain" ], "subcategories": { "AI": [ "Memory" ], "Memory": [ "For beginners" ] } } }, "group": "[\"transform\"]", "defaults": { "name": "Simple Memory" }, "iconData": { "icon": "database", "type": "icon" }, "displayName": "Simple Memory", "typeVersion": 1, "nodeCategories": [ { "id": 25, "name": "AI" }, { "id": 26, "name": "Langchain" } ] }, { "id": 1246, "icon": "fa:database", "name": "@n8n/n8n-nodes-langchain.memoryManager", "codex": { "data": { "resources": { "primaryDocumentation": [ { "url": "https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorymanager/" } ] }, "categories": [ "AI", "Langchain" ], "subcategories": { "AI": [ "Miscellaneous", "Root Nodes" ] } } }, "group": "[\"transform\"]", "defaults": { "name": "Chat Memory Manager" }, "iconData": { "icon": "database", "type": "icon" }, "displayName": "Chat Memory Manager", "typeVersion": 1, "nodeCategories": [ { "id": 25, "name": "AI" }, { "id": 26, "name": "Langchain" } ] } ] }