@n8n-as-code/agent-cli 0.7.0 → 0.8.0

package/dist/assets/n8n-docs-complete.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-01-20T10:00:03.777Z",
+  "generatedAt": "2026-01-20T10:16:44.440Z",
   "version": "1.0.0",
   "sourceUrl": "https://docs.n8n.io/llms.txt",
   "totalPages": 1243,
@@ -18099,6 +18099,78 @@
     },
     {
       "id": "page-0224",
+      "title": "Custom API actions for existing nodes",
+      "url": "https://docs.n8n.io/integrations/custom-operations/index.md",
+      "urlPath": "integrations/custom-operations/index.md",
+      "category": "other",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Custom API operations\n\nOne of the most complex parts of setting up [API](../../glossary/#api) calls is managing authentication. n8n provides [credentials](../../glossary/#credential-n8n) support for operations and services beyond those supported by built-in nodes.\n\n- Custom operations for existing nodes: n8n supplies hundreds of nodes to create workflows that link multiple products. However, some nodes don't include all the possible operations supported by a product's API. You can work around this by making a custom API call using the [HTTP Request](../builtin/core-nodes/n8n-nodes-base.httprequest/) node.\n- Credential-only nodes: n8n includes credential-only nodes. These are integrations where n8n supports setting up credentials for use in the HTTP Request node, but doesn't provide a standalone node. You can find a credential-only node in the nodes panel, as you would for any other integration.\n\n## Predefined credential types\n\nA predefined credential type is a credential that already exists in n8n. You can use predefined credential types instead of generic credentials in the HTTP Request node.\n\nFor example: you create an Asana credential, for use with the Asana node. Later, you want to perform an operation that isn't supported by the Asana node, using Asana's API. You can use your existing Asana credential in the HTTP Request node to perform the operation, without additional authentication setup.\n\n### Using predefined credential types\n\nTo use a predefined credential type:\n\n1. Open your HTTP Request node, or add a new one to your workflow.\n1. In **Authentication**, select **Predefined Credential Type**.\n1. In **Credential Type**, select the API you want to use.\n1. In **Credential for `<API name>`**, you can:\n   1. Select an existing credential for that platform, if available.\n   1. Select **Create New** to create a new credential.\n\n### Credential scopes\n\nSome existing credential types have specific scopes: endpoints that they work with. n8n warns you about this when you select the credential type.\n\nFor example, follow the steps in [Using predefined credential types](#using-predefined-credential-types), and select **Google Calendar OAuth2 API** as your **Credential Type**. n8n displays a box listing the two endpoints you can use this credential type with:\n",
+        "excerpt": "# Custom API operations  One of the most complex parts of setting up [API](../../glossary/#api) calls is managing authentication. n8n provides [credentials](../../glossary/#credential-n8n) support for operations and services beyond those supported by built-in nodes.  - Custom operations for existing nodes: n8n supplies hundreds of nodes to create workflows that link multiple products. However, some nodes don't include all the possible operations supported by a product's API. You can work around...",
+        "sections": [
+          {
+            "title": "Custom API operations",
+            "level": 1,
+            "content": "One of the most complex parts of setting up [API](../../glossary/#api) calls is managing authentication. n8n provides [credentials](../../glossary/#credential-n8n) support for operations and services beyond those supported by built-in nodes.\n\n- Custom operations for existing nodes: n8n supplies hundreds of nodes to create workflows that link multiple products. However, some nodes don't include all the possible operations supported by a product's API. You can work around this by making a custom API call using the [HTTP Request](../builtin/core-nodes/n8n-nodes-base.httprequest/) node.\n- Credential-only nodes: n8n includes credential-only nodes. These are integrations where n8n supports setting up credentials for use in the HTTP Request node, but doesn't provide a standalone node. You can find a credential-only node in the nodes panel, as you would for any other integration."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "custom",
+          "actions",
+          "existing",
+          "nodes",
+          "operations",
+          "predefined",
+          "credential",
+          "types",
+          "using",
+          "scopes"
+        ],
+        "useCases": [],
+        "operations": [
+          "if available."
+        ],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "2 min",
+        "contentLength": 2296,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "custom api actions for existing nodes # custom api operations\n\none of the most complex parts of setting up [api](../../glossary/#api) calls is managing authentication. n8n provides [credentials](../../glossary/#credential-n8n) support for operations and services beyond those supported by built-in nodes.\n\n- custom operations for existing nodes: n8n supplies hundreds of nodes to create workflows that link multiple products. however, some nodes don't include all the possible operations supported by a product's api. you can work around this by making a custom api call using the [http request](../builtin/core-nodes/n8n-nodes-base.httprequest/) node.\n- credential-only nodes: n8n includes credential-only nodes. these are integrations where n8n supports setting up credentials for use in the http request node, but doesn't provide a standalone node. you can find a credential-only node in the nodes panel, as you would for any other integration.\n\n## predefined credential types\n\na predefined credential type is a credential that already exists in n8n. you can use predefined credential types instead of generic credentials in the http request node.\n\nfor example: you create an asana credential, for use with the asana node. later, you want to perform an operation that isn't supported by the asana node, using asana's api. you can use your existing asana credential in the http request node to perform the operation, without additional authentication setup.\n\n### using predefined credential types\n\nto use a predefined credential type:\n\n1. open your http request node, or add a new one to your workflow.\n1. in **authentication**, select **predefined credential type**.\n1. in **credential type**, select the api you want to use.\n1. in **credential for `<api name>`**, you can:\n   1. select an existing credential for that platform, if available.\n   1. select **create new** to create a new credential.\n\n### credential scopes\n\nsome existing credential types have specific scopes: endpoints that they work with. n8n warns you about this when you select the credential type.\n\nfor example, follow the steps in [using predefined credential types](#using-predefined-credential-types), and select **google calendar oauth2 api** as your **credential type**. n8n displays a box listing the two endpoints you can use this credential type with:\n custom api operations",
+        "importantTerms": [
+          "credential",
+          "nodes",
+          "node",
+          "predefined",
+          "type",
+          "types",
+          "select",
+          "custom",
+          "existing",
+          "operations",
+          "that",
+          "using",
+          "http",
+          "request",
+          "asana",
+          "create",
+          "your",
+          "authentication",
+          "credentials",
+          "supported",
+          "this",
+          "only",
+          "with"
+        ]
+      }
+    },
+    {
+      "id": "page-0225",
       "title": "n8n Integrations Documentation and Guides",
       "url": "https://docs.n8n.io/integrations/index.md",
       "urlPath": "integrations/index.md",
@@ -18172,78 +18244,6 @@
         ]
       }
     },
-    {
-      "id": "page-0225",
-      "title": "Custom API actions for existing nodes",
-      "url": "https://docs.n8n.io/integrations/custom-operations/index.md",
-      "urlPath": "integrations/custom-operations/index.md",
-      "category": "other",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Custom API operations\n\nOne of the most complex parts of setting up [API](../../glossary/#api) calls is managing authentication. n8n provides [credentials](../../glossary/#credential-n8n) support for operations and services beyond those supported by built-in nodes.\n\n- Custom operations for existing nodes: n8n supplies hundreds of nodes to create workflows that link multiple products. However, some nodes don't include all the possible operations supported by a product's API. You can work around this by making a custom API call using the [HTTP Request](../builtin/core-nodes/n8n-nodes-base.httprequest/) node.\n- Credential-only nodes: n8n includes credential-only nodes. These are integrations where n8n supports setting up credentials for use in the HTTP Request node, but doesn't provide a standalone node. You can find a credential-only node in the nodes panel, as you would for any other integration.\n\n## Predefined credential types\n\nA predefined credential type is a credential that already exists in n8n. You can use predefined credential types instead of generic credentials in the HTTP Request node.\n\nFor example: you create an Asana credential, for use with the Asana node. Later, you want to perform an operation that isn't supported by the Asana node, using Asana's API. You can use your existing Asana credential in the HTTP Request node to perform the operation, without additional authentication setup.\n\n### Using predefined credential types\n\nTo use a predefined credential type:\n\n1. Open your HTTP Request node, or add a new one to your workflow.\n1. In **Authentication**, select **Predefined Credential Type**.\n1. In **Credential Type**, select the API you want to use.\n1. In **Credential for `<API name>`**, you can:\n   1. Select an existing credential for that platform, if available.\n   1. Select **Create New** to create a new credential.\n\n### Credential scopes\n\nSome existing credential types have specific scopes: endpoints that they work with. n8n warns you about this when you select the credential type.\n\nFor example, follow the steps in [Using predefined credential types](#using-predefined-credential-types), and select **Google Calendar OAuth2 API** as your **Credential Type**. n8n displays a box listing the two endpoints you can use this credential type with:\n",
-        "excerpt": "# Custom API operations  One of the most complex parts of setting up [API](../../glossary/#api) calls is managing authentication. n8n provides [credentials](../../glossary/#credential-n8n) support for operations and services beyond those supported by built-in nodes.  - Custom operations for existing nodes: n8n supplies hundreds of nodes to create workflows that link multiple products. However, some nodes don't include all the possible operations supported by a product's API. You can work around...",
-        "sections": [
-          {
-            "title": "Custom API operations",
-            "level": 1,
-            "content": "One of the most complex parts of setting up [API](../../glossary/#api) calls is managing authentication. n8n provides [credentials](../../glossary/#credential-n8n) support for operations and services beyond those supported by built-in nodes.\n\n- Custom operations for existing nodes: n8n supplies hundreds of nodes to create workflows that link multiple products. However, some nodes don't include all the possible operations supported by a product's API. You can work around this by making a custom API call using the [HTTP Request](../builtin/core-nodes/n8n-nodes-base.httprequest/) node.\n- Credential-only nodes: n8n includes credential-only nodes. These are integrations where n8n supports setting up credentials for use in the HTTP Request node, but doesn't provide a standalone node. You can find a credential-only node in the nodes panel, as you would for any other integration."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "custom",
-          "actions",
-          "existing",
-          "nodes",
-          "operations",
-          "predefined",
-          "credential",
-          "types",
-          "using",
-          "scopes"
-        ],
-        "useCases": [],
-        "operations": [
-          "if available."
-        ],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "2 min",
-        "contentLength": 2296,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "custom api actions for existing nodes # custom api operations\n\none of the most complex parts of setting up [api](../../glossary/#api) calls is managing authentication. n8n provides [credentials](../../glossary/#credential-n8n) support for operations and services beyond those supported by built-in nodes.\n\n- custom operations for existing nodes: n8n supplies hundreds of nodes to create workflows that link multiple products. however, some nodes don't include all the possible operations supported by a product's api. you can work around this by making a custom api call using the [http request](../builtin/core-nodes/n8n-nodes-base.httprequest/) node.\n- credential-only nodes: n8n includes credential-only nodes. these are integrations where n8n supports setting up credentials for use in the http request node, but doesn't provide a standalone node. you can find a credential-only node in the nodes panel, as you would for any other integration.\n\n## predefined credential types\n\na predefined credential type is a credential that already exists in n8n. you can use predefined credential types instead of generic credentials in the http request node.\n\nfor example: you create an asana credential, for use with the asana node. later, you want to perform an operation that isn't supported by the asana node, using asana's api. you can use your existing asana credential in the http request node to perform the operation, without additional authentication setup.\n\n### using predefined credential types\n\nto use a predefined credential type:\n\n1. open your http request node, or add a new one to your workflow.\n1. in **authentication**, select **predefined credential type**.\n1. in **credential type**, select the api you want to use.\n1. in **credential for `<api name>`**, you can:\n   1. select an existing credential for that platform, if available.\n   1. select **create new** to create a new credential.\n\n### credential scopes\n\nsome existing credential types have specific scopes: endpoints that they work with. n8n warns you about this when you select the credential type.\n\nfor example, follow the steps in [using predefined credential types](#using-predefined-credential-types), and select **google calendar oauth2 api** as your **credential type**. n8n displays a box listing the two endpoints you can use this credential type with:\n custom api operations",
-        "importantTerms": [
-          "credential",
-          "nodes",
-          "node",
-          "predefined",
-          "type",
-          "types",
-          "select",
-          "custom",
-          "existing",
-          "operations",
-          "that",
-          "using",
-          "http",
-          "request",
-          "asana",
-          "create",
-          "your",
-          "authentication",
-          "credentials",
-          "supported",
-          "this",
-          "only",
-          "with"
-        ]
-      }
-    },
     {
       "id": "page-0226",
       "title": "Node types",
@@ -89343,7 +89343,7 @@
         "page-0001",
         "page-0147",
         "page-0199",
-        "page-0224",
+        "page-0225",
         "page-0698"
       ],
       "start": [
@@ -92558,7 +92558,7 @@
         "page-0139",
         "page-0141",
         "page-0192",
-        "page-0225",
+        "page-0224",
         "page-0325",
         "page-0484",
         "page-0508",
@@ -92996,7 +92996,7 @@
       "only": [
         "page-0005",
         "page-0164",
-        "page-0224",
+        "page-0225",
         "page-0508",
         "page-0515",
         "page-0620",
@@ -93715,7 +93715,7 @@
         "page-0147",
         "page-0149",
         "page-0150",
-        "page-0224",
+        "page-0225",
         "page-0226",
         "page-0840",
         "page-1127",
@@ -94837,7 +94837,7 @@
         "page-0046",
         "page-0047",
         "page-0131",
-        "page-0224",
+        "page-0225",
         "page-0516",
         "page-0610",
         "page-0625",
@@ -94852,7 +94852,7 @@
         "page-0042",
         "page-0047",
         "page-0131",
-        "page-0224",
+        "page-0225",
         "page-1202"
       ],
       "related": [
@@ -95915,7 +95915,7 @@
         "page-0016",
         "page-0024",
         "page-0103",
-        "page-0225",
+        "page-0224",
         "page-0226",
         "page-0977",
         "page-1203",
@@ -97490,7 +97490,7 @@
         "page-0201",
         "page-0202",
         "page-0203",
-        "page-0224",
+        "page-0225",
         "page-1138",
         "page-1141",
         "page-1189",
@@ -98330,7 +98330,7 @@
       ],
       "scopes": [
         "page-0044",
-        "page-0225",
+        "page-0224",
         "page-0436",
         "page-0725",
         "page-0816",
@@ -98389,7 +98389,7 @@
         "page-0054",
         "page-0060",
         "page-0070",
-        "page-0224",
+        "page-0225",
         "page-0226",
         "page-0531",
         "page-0537",
@@ -102962,11 +102962,16 @@
         "page-0223",
         "page-0558"
       ],
-      "integrations": [
+      "actions": [
         "page-0224",
         "page-0226",
-        "page-0227",
-        "page-0880"
+        "page-0228",
+        "page-0636",
+        "page-1235"
+      ],
+      "existing": [
+        "page-0224",
+        "page-1235"
       ],
       "operations": [
         "page-0224",
@@ -103289,27 +103294,22 @@
         "page-1166",
         "page-1186"
       ],
-      "generic": [
+      "predefined": [
         "page-0224",
         "page-0695",
-        "page-1009",
-        "page-1219"
+        "page-0815"
       ],
-      "actions": [
+      "integrations": [
         "page-0225",
         "page-0226",
-        "page-0228",
-        "page-0636",
-        "page-1235"
-      ],
-      "existing": [
-        "page-0225",
-        "page-1235"
+        "page-0227",
+        "page-0880"
       ],
-      "predefined": [
+      "generic": [
         "page-0225",
         "page-0695",
-        "page-0815"
+        "page-1009",
+        "page-1219"
       ],
       "operations:": [
         "page-0226",