npm - @n8n-as-code/agent-cli - Versions diffs - 0.8.0 → 0.10.0 - Mend

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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (16) hide show

package/dist/assets/n8n-docs-complete.json +296 -361
package/dist/assets/n8n-knowledge-index.json +1512 -1549
package/dist/assets/n8n-nodes-technical.json +118635 -142001
package/dist/cli.js +16 -6
package/dist/cli.js.map +1 -1
package/dist/services/ai-context-generator.d.ts.map +1 -1
package/dist/services/ai-context-generator.js +23 -8
package/dist/services/ai-context-generator.js.map +1 -1
package/dist/services/node-schema-provider.d.ts +2 -0
package/dist/services/node-schema-provider.d.ts.map +1 -1
package/dist/services/node-schema-provider.js +14 -1
package/dist/services/node-schema-provider.js.map +1 -1
package/dist/services/workflow-validator.d.ts.map +1 -1
package/dist/services/workflow-validator.js +4 -3
package/dist/services/workflow-validator.js.map +1 -1
package/package.json +3 -2

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

@@ -1,8 +1,8 @@
 {
-  "generatedAt": "2026-01-20T10:16:44.440Z",
+  "generatedAt": "2026-01-20T16:39:04.398Z",
   "version": "1.0.0",
   "sourceUrl": "https://docs.n8n.io/llms.txt",
-  "totalPages": 1243,
+  "totalPages": 1242,
   "statistics": {
     "byCategory": {
       "other": 432,
@@ -11,7 +11,7 @@
       "api": 5,
       "code": 38,
       "data": 20,
-      "flow-logic": 8,
+      "flow-logic": 7,
       "hosting": 76,
       "integrations": 305,
       "cluster-nodes": 96,
@@ -611,7 +611,7 @@
     },
     "flow-logic": {
       "description": "Documentation pages",
-      "totalPages": 8,
+      "totalPages": 7,
       "pages": [
         "page-0138",
         "page-0139",
@@ -619,7 +619,6 @@
         "page-0141",
         "page-0142",
         "page-0143",
-        "page-0144",
         "page-0145"
       ]
     },
@@ -10096,58 +10095,6 @@
     },
     {
       "id": "page-0111",
-      "title": "Data",
-      "url": "https://docs.n8n.io/data/index.md",
-      "urlPath": "data/index.md",
-      "category": "data",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Data\n\nData is the information that n8n nodes receive and process. For basic usage of n8n you don't need to understand data structures and manipulation. However, it becomes important if you want to:\n\n- Create your own node\n- Write custom [expressions](../glossary/#expression-n8n)\n- Use the Function or Function Item node\n\nThis section covers:\n\n- [Data structure](data-structure/)\n- [Data flow within nodes](data-flow-nodes/)\n- [Transforming data](transforming-data/)\n- [Process data using code](code/)\n- [Pinning](data-pinning/) and [editing](data-editing/) data during workflow development.\n- [Data mapping](data-mapping/) and [Item linking](data-mapping/data-item-linking/): how data items link to each other.\n\n## Related resources\n\n### Data transformation nodes\n\nn8n provides a collection of nodes to transform data:\n\n- [Aggregate](../integrations/builtin/core-nodes/n8n-nodes-base.aggregate/): take separate items, or portions of them, and group them together into individual items.\n- [Limit](../integrations/builtin/core-nodes/n8n-nodes-base.aggregate/): remove items beyond a defined maximum number.\n- [Remove Duplicates](../integrations/builtin/core-nodes/n8n-nodes-base.removeduplicates/): identify and delete items that are identical across all fields or a subset of fields.\n- [Sort](../integrations/builtin/core-nodes/n8n-nodes-base.sort/): organize lists of in a desired ordering, or generate a random selection.\n- [Split Out](../integrations/builtin/core-nodes/n8n-nodes-base.splitout/): separate a single data item containing a list into multiple items.\n- [Summarize](../integrations/builtin/core-nodes/n8n-nodes-base.summarize/): aggregate items together, in a manner similar to Excel pivot tables.\n",
-        "excerpt": "# Data  Data is the information that n8n nodes receive and process. For basic usage of n8n you don't need to understand data structures and manipulation. However, it becomes important if you want to:  - Create your own node - Write custom [expressions](../glossary/#expression-n8n) - Use the Function or Function Item node  This section covers:  - [Data structure](data-structure/) - [Data flow within nodes](data-flow-nodes/) - [Transforming data](transforming-data/) - [Process data using code](cod...",
-        "sections": [
-          {
-            "title": "Data",
-            "level": 1,
-            "content": "Data is the information that n8n nodes receive and process. For basic usage of n8n you don't need to understand data structures and manipulation. However, it becomes important if you want to:\n\n- Create your own node\n- Write custom [expressions](../glossary/#expression-n8n)\n- Use the Function or Function Item node\n\nThis section covers:\n\n- [Data structure](data-structure/)\n- [Data flow within nodes](data-flow-nodes/)\n- [Transforming data](transforming-data/)\n- [Process data using code](code/)\n- [Pinning](data-pinning/) and [editing](data-editing/) data during workflow development.\n- [Data mapping](data-mapping/) and [Item linking](data-mapping/data-item-linking/): how data items link to each other."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "data",
-          "related",
-          "resources",
-          "transformation",
-          "nodes"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "1 min",
-        "contentLength": 1715,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "data # data\n\ndata is the information that n8n nodes receive and process. for basic usage of n8n you don't need to understand data structures and manipulation. however, it becomes important if you want to:\n\n- create your own node\n- write custom [expressions](../glossary/#expression-n8n)\n- use the function or function item node\n\nthis section covers:\n\n- [data structure](data-structure/)\n- [data flow within nodes](data-flow-nodes/)\n- [transforming data](transforming-data/)\n- [process data using code](code/)\n- [pinning](data-pinning/) and [editing](data-editing/) data during workflow development.\n- [data mapping](data-mapping/) and [item linking](data-mapping/data-item-linking/): how data items link to each other.\n\n## related resources\n\n### data transformation nodes\n\nn8n provides a collection of nodes to transform data:\n\n- [aggregate](../integrations/builtin/core-nodes/n8n-nodes-base.aggregate/): take separate items, or portions of them, and group them together into individual items.\n- [limit](../integrations/builtin/core-nodes/n8n-nodes-base.aggregate/): remove items beyond a defined maximum number.\n- [remove duplicates](../integrations/builtin/core-nodes/n8n-nodes-base.removeduplicates/): identify and delete items that are identical across all fields or a subset of fields.\n- [sort](../integrations/builtin/core-nodes/n8n-nodes-base.sort/): organize lists of in a desired ordering, or generate a random selection.\n- [split out](../integrations/builtin/core-nodes/n8n-nodes-base.splitout/): separate a single data item containing a list into multiple items.\n- [summarize](../integrations/builtin/core-nodes/n8n-nodes-base.summarize/): aggregate items together, in a manner similar to excel pivot tables.\n data",
-        "importantTerms": [
-          "data",
-          "nodes",
-          "items",
-          "integrations",
-          "builtin",
-          "core",
-          "base",
-          "item",
-          "aggregate",
-          "mapping"
-        ]
-      }
-    },
-    {
-      "id": "page-0112",
       "title": "Binary data",
       "url": "https://docs.n8n.io/data/binary-data/index.md",
       "urlPath": "data/binary-data/index.md",
@@ -10216,6 +10163,58 @@
         ]
       }
     },
+    {
+      "id": "page-0112",
+      "title": "Data",
+      "url": "https://docs.n8n.io/data/index.md",
+      "urlPath": "data/index.md",
+      "category": "data",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Data\n\nData is the information that n8n nodes receive and process. For basic usage of n8n you don't need to understand data structures and manipulation. However, it becomes important if you want to:\n\n- Create your own node\n- Write custom [expressions](../glossary/#expression-n8n)\n- Use the Function or Function Item node\n\nThis section covers:\n\n- [Data structure](data-structure/)\n- [Data flow within nodes](data-flow-nodes/)\n- [Transforming data](transforming-data/)\n- [Process data using code](code/)\n- [Pinning](data-pinning/) and [editing](data-editing/) data during workflow development.\n- [Data mapping](data-mapping/) and [Item linking](data-mapping/data-item-linking/): how data items link to each other.\n\n## Related resources\n\n### Data transformation nodes\n\nn8n provides a collection of nodes to transform data:\n\n- [Aggregate](../integrations/builtin/core-nodes/n8n-nodes-base.aggregate/): take separate items, or portions of them, and group them together into individual items.\n- [Limit](../integrations/builtin/core-nodes/n8n-nodes-base.aggregate/): remove items beyond a defined maximum number.\n- [Remove Duplicates](../integrations/builtin/core-nodes/n8n-nodes-base.removeduplicates/): identify and delete items that are identical across all fields or a subset of fields.\n- [Sort](../integrations/builtin/core-nodes/n8n-nodes-base.sort/): organize lists of in a desired ordering, or generate a random selection.\n- [Split Out](../integrations/builtin/core-nodes/n8n-nodes-base.splitout/): separate a single data item containing a list into multiple items.\n- [Summarize](../integrations/builtin/core-nodes/n8n-nodes-base.summarize/): aggregate items together, in a manner similar to Excel pivot tables.\n",
+        "excerpt": "# Data  Data is the information that n8n nodes receive and process. For basic usage of n8n you don't need to understand data structures and manipulation. However, it becomes important if you want to:  - Create your own node - Write custom [expressions](../glossary/#expression-n8n) - Use the Function or Function Item node  This section covers:  - [Data structure](data-structure/) - [Data flow within nodes](data-flow-nodes/) - [Transforming data](transforming-data/) - [Process data using code](cod...",
+        "sections": [
+          {
+            "title": "Data",
+            "level": 1,
+            "content": "Data is the information that n8n nodes receive and process. For basic usage of n8n you don't need to understand data structures and manipulation. However, it becomes important if you want to:\n\n- Create your own node\n- Write custom [expressions](../glossary/#expression-n8n)\n- Use the Function or Function Item node\n\nThis section covers:\n\n- [Data structure](data-structure/)\n- [Data flow within nodes](data-flow-nodes/)\n- [Transforming data](transforming-data/)\n- [Process data using code](code/)\n- [Pinning](data-pinning/) and [editing](data-editing/) data during workflow development.\n- [Data mapping](data-mapping/) and [Item linking](data-mapping/data-item-linking/): how data items link to each other."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "data",
+          "related",
+          "resources",
+          "transformation",
+          "nodes"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "1 min",
+        "contentLength": 1715,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "data # data\n\ndata is the information that n8n nodes receive and process. for basic usage of n8n you don't need to understand data structures and manipulation. however, it becomes important if you want to:\n\n- create your own node\n- write custom [expressions](../glossary/#expression-n8n)\n- use the function or function item node\n\nthis section covers:\n\n- [data structure](data-structure/)\n- [data flow within nodes](data-flow-nodes/)\n- [transforming data](transforming-data/)\n- [process data using code](code/)\n- [pinning](data-pinning/) and [editing](data-editing/) data during workflow development.\n- [data mapping](data-mapping/) and [item linking](data-mapping/data-item-linking/): how data items link to each other.\n\n## related resources\n\n### data transformation nodes\n\nn8n provides a collection of nodes to transform data:\n\n- [aggregate](../integrations/builtin/core-nodes/n8n-nodes-base.aggregate/): take separate items, or portions of them, and group them together into individual items.\n- [limit](../integrations/builtin/core-nodes/n8n-nodes-base.aggregate/): remove items beyond a defined maximum number.\n- [remove duplicates](../integrations/builtin/core-nodes/n8n-nodes-base.removeduplicates/): identify and delete items that are identical across all fields or a subset of fields.\n- [sort](../integrations/builtin/core-nodes/n8n-nodes-base.sort/): organize lists of in a desired ordering, or generate a random selection.\n- [split out](../integrations/builtin/core-nodes/n8n-nodes-base.splitout/): separate a single data item containing a list into multiple items.\n- [summarize](../integrations/builtin/core-nodes/n8n-nodes-base.summarize/): aggregate items together, in a manner similar to excel pivot tables.\n data",
+        "importantTerms": [
+          "data",
+          "nodes",
+          "items",
+          "integrations",
+          "builtin",
+          "core",
+          "base",
+          "item",
+          "aggregate",
+          "mapping"
+        ]
+      }
+    },
     {
       "id": "page-0113",
       "title": "Process data using code",
@@ -12193,13 +12192,13 @@
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Splitting workflows with conditional nodes\n\nSplitting uses the [IF](../../integrations/builtin/core-nodes/n8n-nodes-base.if/) or [Switch](../../integrations/builtin/core-nodes/n8n-nodes-base.switch/) nodes. It turns a single-branch workflow into a multi-branch workflow. This is a key piece of representing complex logic in n8n.\n\nCompare these workflows:\n\nThis is the power of splitting and conditional nodes in n8n.\n\nRefer to the [IF](../../integrations/builtin/core-nodes/n8n-nodes-base.if/) or [Switch](../../integrations/builtin/core-nodes/n8n-nodes-base.switch/) documentation for usage details.\n",
-        "excerpt": "# Splitting workflows with conditional nodes  Splitting uses the [IF](../../integrations/builtin/core-nodes/n8n-nodes-base.if/) or [Switch](../../integrations/builtin/core-nodes/n8n-nodes-base.switch/) nodes. It turns a single-branch workflow into a multi-branch workflow. This is a key piece of representing complex logic in n8n.  Compare these workflows:  This is the power of splitting and conditional nodes in n8n.  Refer to the [IF](../../integrations/builtin/core-nodes/n8n-nodes-base.if/) or [...",
+        "markdown": "# Sub-workflows\n\nYou can call one workflow from another workflow. This allows you to build modular, microservice-like workflows. It can also help if your workflow grows large enough to encounter [memory issues](../../hosting/scaling/memory-errors/). Creating sub-workflows uses the [Execute Workflow](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) and [Execute Sub-workflow Trigger](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflowtrigger/) nodes.\n\nSub-wokflow executions don't count towards your plan's monthly execution or active workflow limits.\n\n## Set up and use a sub-workflow\n\nThis section walks through setting up both the parent workflow and sub-workflow.\n\n### Create the sub-workflow\n\n1. Create a new workflow.\n\n   Create sub-workflows from existing workflows\n\n   You can optionally create a sub-workflow directly from an existing parent workflow using the [Execute Sub-workflow](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) node. In the node, select the **Database** and **From list** options and select **Create a sub-workflow** in the list.\n\n   You can also extract selected nodes directly using [Sub-workflow conversion](../../workflows/subworkflow-conversion/) in the context menu.\n\n1. **Optional**: configure which workflows can call the sub-workflow:\n\n   1. Select the **Options** menu > **Settings**. n8n opens the **Workflow settings** modal.\n   1. Change the **This workflow can be called by** setting. Refer to [Workflow settings](../../workflows/settings/) for more information on configuring your workflows.\n\n1. Add the **Execute Sub-workflow** trigger node (if you are searching under trigger nodes, this is also titled **When Executed by Another Workflow**).\n\n1. Set the **Input data mode** to choose how you will define the sub-workflow's input data:\n\n   - **Define using fields below**: Choose this mode to define individual input names and data types that the calling workflow needs to provide. The [Execute Sub-workflow node](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) or [Call n8n Workflow Tool node](../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.toolworkflow/) in the calling workflow will automatically pull in the fields defined here.\n   - **Define using JSON example**: Choose this mode to provide an example JSON object that demonstrates the expected input items and their types.\n   - **Accept all data**: Choose this mode to accept all data unconditionally. The sub-workflow won't define any required input items. This sub-workflow must handle any input inconsistencies or missing values.\n\n1. Add other nodes as needed to build your sub-workflow functionality.\n\n1. Save the sub-workflow.\n\nSub-workflow mustn't contain errors\n\nIf there are errors in the sub-workflow, the parent workflow can't trigger it.\n\nLoad data into sub-workflow before building\n\nThis requires the ability to [load data from previous executions](../../workflows/executions/debug/), which is available on n8n Cloud and registered Community plans.\n\nIf you want to load data into your sub-workflow to use while building it:\n\n1. Create the sub-workflow and add the **Execute Sub-workflow Trigger**.\n1. Set the node's **Input data mode** to **Accept all data** or define the input items using fields or JSON if they're already known.\n1. In the sub-workflow [settings](../../workflows/settings/), set **Save successful production executions** to **Save**.\n1. Skip ahead to setting up the parent workflow, and run it.\n1. Follow the steps to [load data from previous executions](../../workflows/executions/debug/).\n1. Adjust the **Input data mode** to match the input sent by the parent workflow if necessary.\n\nYou can now pin example data in the trigger node, enabling you to work with real data while configuring the rest of the workflow.\n\n### Call the sub-workflow\n\n1. Open the workflow where you want to call the sub-workflow.\n\n1. Add the **Execute Sub-workflow** node.\n\n1. In the **Execute Sub-workflow** node, set the sub-workflow you want to call. You can choose to call the workflow by ID, load a workflow from a local file, add workflow JSON as a parameter in the node, or target a workflow by URL.\n\n   Find your workflow ID\n\n   Your sub-workflow's ID is the alphanumeric string at the end of its URL.\n\n1. Fill in the required input items defined by the sub-workflow.\n\n1. Save your workflow.\n\nWhen your workflow executes, it will send data to the sub-workflow, and run it.\n\nYou can follow the execution flow from the parent workflow to the sub-workflow by opening the Execute Sub-workflow node and selecting the **View sub-execution** link. Likewise, the sub-workflow's execution contains a link back to the parent workflow's execution to navigate in the other direction.\n\n## How data passes between workflows\n\nAs an example, imagine you have an Execute Sub-workflow node in **Workflow A**. The Execute Sub-workflow node calls another workflow called **Workflow B**:\n\n1. The Execute Sub-workflow node passes the data to the Execute Sub-workflow Trigger node (titled \"When executed by another node\" in the canvas) of **Workflow B**.\n1. The last node of **Workflow B** sends the data back to the Execute Sub-workflow node in **Workflow A**.\n\n## Sub-workflow conversion\n\nSee [sub-workflow conversion](../../workflows/subworkflow-conversion/) for how to divide your existing workflows into sub-workflows.\n",
+        "excerpt": "# Sub-workflows  You can call one workflow from another workflow. This allows you to build modular, microservice-like workflows. It can also help if your workflow grows large enough to encounter [memory issues](../../hosting/scaling/memory-errors/). Creating sub-workflows uses the [Execute Workflow](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) and [Execute Sub-workflow Trigger](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflowtrigger/) nodes.  Sub-wok...",
         "sections": [
           {
-            "title": "Splitting workflows with conditional nodes",
+            "title": "Sub-workflows",
             "level": 1,
-            "content": "Splitting uses the [IF](../../integrations/builtin/core-nodes/n8n-nodes-base.if/) or [Switch](../../integrations/builtin/core-nodes/n8n-nodes-base.switch/) nodes. It turns a single-branch workflow into a multi-branch workflow. This is a key piece of representing complex logic in n8n.\n\nCompare these workflows:\n\nThis is the power of splitting and conditional nodes in n8n.\n\nRefer to the [IF](../../integrations/builtin/core-nodes/n8n-nodes-base.if/) or [Switch](../../integrations/builtin/core-nodes/n8n-nodes-base.switch/) documentation for usage details."
+            "content": "You can call one workflow from another workflow. This allows you to build modular, microservice-like workflows. It can also help if your workflow grows large enough to encounter [memory issues](../../hosting/scaling/memory-errors/). Creating sub-workflows uses the [Execute Workflow](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) and [Execute Sub-workflow Trigger](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflowtrigger/) nodes.\n\nSub-wokflow executions don't count towards your plan's monthly execution or active workflow limits."
           }
         ]
       },
@@ -12216,72 +12215,17 @@
         "operations": [],
         "codeExamples": 0,
         "complexity": "beginner",
-        "readingTime": "1 min",
-        "contentLength": 603,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "splitting with conditionals # splitting workflows with conditional nodes\n\nsplitting uses the [if](../../integrations/builtin/core-nodes/n8n-nodes-base.if/) or [switch](../../integrations/builtin/core-nodes/n8n-nodes-base.switch/) nodes. it turns a single-branch workflow into a multi-branch workflow. this is a key piece of representing complex logic in n8n.\n\ncompare these workflows:\n\nthis is the power of splitting and conditional nodes in n8n.\n\nrefer to the [if](../../integrations/builtin/core-nodes/n8n-nodes-base.if/) or [switch](../../integrations/builtin/core-nodes/n8n-nodes-base.switch/) documentation for usage details.\n splitting workflows with conditional nodes",
-        "importantTerms": [
-          "nodes",
-          "splitting",
-          "integrations",
-          "builtin",
-          "core",
-          "base",
-          "switch",
-          "with",
-          "workflows",
-          "conditional"
-        ]
-      }
-    },
-    {
-      "id": "page-0144",
-      "title": "Sub-workflows",
-      "url": "https://docs.n8n.io/flow-logic/subworkflows/index.md",
-      "urlPath": "flow-logic/subworkflows/index.md",
-      "category": "flow-logic",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Sub-workflows\n\nYou can call one workflow from another workflow. This allows you to build modular, microservice-like workflows. It can also help if your workflow grows large enough to encounter [memory issues](../../hosting/scaling/memory-errors/). Creating sub-workflows uses the [Execute Workflow](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) and [Execute Sub-workflow Trigger](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflowtrigger/) nodes.\n\nSub-wokflow executions don't count towards your plan's monthly execution or active workflow limits.\n\n## Set up and use a sub-workflow\n\nThis section walks through setting up both the parent workflow and sub-workflow.\n\n### Create the sub-workflow\n\n1. Create a new workflow.\n\n   Create sub-workflows from existing workflows\n\n   You can optionally create a sub-workflow directly from an existing parent workflow using the [Execute Sub-workflow](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) node. In the node, select the **Database** and **From list** options and select **Create a sub-workflow** in the list.\n\n   You can also extract selected nodes directly using [Sub-workflow conversion](../../workflows/subworkflow-conversion/) in the context menu.\n\n1. **Optional**: configure which workflows can call the sub-workflow:\n\n   1. Select the **Options** menu > **Settings**. n8n opens the **Workflow settings** modal.\n   1. Change the **This workflow can be called by** setting. Refer to [Workflow settings](../../workflows/settings/) for more information on configuring your workflows.\n\n1. Add the **Execute Sub-workflow** trigger node (if you are searching under trigger nodes, this is also titled **When Executed by Another Workflow**).\n\n1. Set the **Input data mode** to choose how you will define the sub-workflow's input data:\n\n   - **Define using fields below**: Choose this mode to define individual input names and data types that the calling workflow needs to provide. The [Execute Sub-workflow node](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) or [Call n8n Workflow Tool node](../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.toolworkflow/) in the calling workflow will automatically pull in the fields defined here.\n   - **Define using JSON example**: Choose this mode to provide an example JSON object that demonstrates the expected input items and their types.\n   - **Accept all data**: Choose this mode to accept all data unconditionally. The sub-workflow won't define any required input items. This sub-workflow must handle any input inconsistencies or missing values.\n\n1. Add other nodes as needed to build your sub-workflow functionality.\n\n1. Save the sub-workflow.\n\nSub-workflow mustn't contain errors\n\nIf there are errors in the sub-workflow, the parent workflow can't trigger it.\n\nLoad data into sub-workflow before building\n\nThis requires the ability to [load data from previous executions](../../workflows/executions/debug/), which is available on n8n Cloud and registered Community plans.\n\nIf you want to load data into your sub-workflow to use while building it:\n\n1. Create the sub-workflow and add the **Execute Sub-workflow Trigger**.\n1. Set the node's **Input data mode** to **Accept all data** or define the input items using fields or JSON if they're already known.\n1. In the sub-workflow [settings](../../workflows/settings/), set **Save successful production executions** to **Save**.\n1. Skip ahead to setting up the parent workflow, and run it.\n1. Follow the steps to [load data from previous executions](../../workflows/executions/debug/).\n1. Adjust the **Input data mode** to match the input sent by the parent workflow if necessary.\n\nYou can now pin example data in the trigger node, enabling you to work with real data while configuring the rest of the workflow.\n\n### Call the sub-workflow\n\n1. Open the workflow where you want to call the sub-workflow.\n\n1. Add the **Execute Sub-workflow** node.\n\n1. In the **Execute Sub-workflow** node, set the sub-workflow you want to call. You can choose to call the workflow by ID, load a workflow from a local file, add workflow JSON as a parameter in the node, or target a workflow by URL.\n\n   Find your workflow ID\n\n   Your sub-workflow's ID is the alphanumeric string at the end of its URL.\n\n1. Fill in the required input items defined by the sub-workflow.\n\n1. Save your workflow.\n\nWhen your workflow executes, it will send data to the sub-workflow, and run it.\n\nYou can follow the execution flow from the parent workflow to the sub-workflow by opening the Execute Sub-workflow node and selecting the **View sub-execution** link. Likewise, the sub-workflow's execution contains a link back to the parent workflow's execution to navigate in the other direction.\n\n## How data passes between workflows\n\nAs an example, imagine you have an Execute Sub-workflow node in **Workflow A**. The Execute Sub-workflow node calls another workflow called **Workflow B**:\n\n1. The Execute Sub-workflow node passes the data to the Execute Sub-workflow Trigger node (titled \"When executed by another node\" in the canvas) of **Workflow B**.\n1. The last node of **Workflow B** sends the data back to the Execute Sub-workflow node in **Workflow A**.\n\n## Sub-workflow conversion\n\nSee [sub-workflow conversion](../../workflows/subworkflow-conversion/) for how to divide your existing workflows into sub-workflows.\n",
-        "excerpt": "# Sub-workflows  You can call one workflow from another workflow. This allows you to build modular, microservice-like workflows. It can also help if your workflow grows large enough to encounter [memory issues](../../hosting/scaling/memory-errors/). Creating sub-workflows uses the [Execute Workflow](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) and [Execute Sub-workflow Trigger](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflowtrigger/) nodes.  Sub-wok...",
-        "sections": [
-          {
-            "title": "Sub-workflows",
-            "level": 1,
-            "content": "You can call one workflow from another workflow. This allows you to build modular, microservice-like workflows. It can also help if your workflow grows large enough to encounter [memory issues](../../hosting/scaling/memory-errors/). Creating sub-workflows uses the [Execute Workflow](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) and [Execute Sub-workflow Trigger](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflowtrigger/) nodes.\n\nSub-wokflow executions don't count towards your plan's monthly execution or active workflow limits."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "workflows",
-          "workflow",
-          "create",
-          "call",
-          "data",
-          "passes",
-          "between",
-          "conversion"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
         "readingTime": "4 min",
         "contentLength": 5432,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "sub-workflows # sub-workflows\n\nyou can call one workflow from another workflow. this allows you to build modular, microservice-like workflows. it can also help if your workflow grows large enough to encounter [memory issues](../../hosting/scaling/memory-errors/). creating sub-workflows uses the [execute workflow](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) and [execute sub-workflow trigger](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflowtrigger/) nodes.\n\nsub-wokflow executions don't count towards your plan's monthly execution or active workflow limits.\n\n## set up and use a sub-workflow\n\nthis section walks through setting up both the parent workflow and sub-workflow.\n\n### create the sub-workflow\n\n1. create a new workflow.\n\n   create sub-workflows from existing workflows\n\n   you can optionally create a sub-workflow directly from an existing parent workflow using the [execute sub-workflow](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) node. in the node, select the **database** and **from list** options and select **create a sub-workflow** in the list.\n\n   you can also extract selected nodes directly using [sub-workflow conversion](../../workflows/subworkflow-conversion/) in the context menu.\n\n1. **optional**: configure which workflows can call the sub-workflow:\n\n   1. select the **options** menu > **settings**. n8n opens the **workflow settings** modal.\n   1. change the **this workflow can be called by** setting. refer to [workflow settings](../../workflows/settings/) for more information on configuring your workflows.\n\n1. add the **execute sub-workflow** trigger node (if you are searching under trigger nodes, this is also titled **when executed by another workflow**).\n\n1. set the **input data mode** to choose how you will define the sub-workflow's input data:\n\n   - **define using fields below**: choose this mode to define individual input names and data types that the calling workflow needs to provide. the [execute sub-workflow node](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) or [call n8n workflow tool node](../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.toolworkflow/) in the calling workflow will automatically pull in the fields defined here.\n   - **define using json example**: choose this mode to provide an example json object that demonstrates the expected input items and their types.\n   - **accept all data**: choose this mode to accept all data unconditionally. the sub-workflow won't define any required input items. this sub-workflow must handle any input inconsistencies or missing values.\n\n1. add other nodes as needed to build your sub-workflow functionality.\n\n1. save the sub-workflow.\n\nsub-workflow mustn't contain errors\n\nif there are errors in the sub-workflow, the parent workflow can't trigger it.\n\nload data into sub-workflow before building\n\nthis requires the ability to [load data from previous executions](../../workflows/executions/debug/), which is available on n8n cloud and registered community plans.\n\nif you want to load data into your sub-workflow to use while building it:\n\n1. create the sub-workflow and add the **execute sub-workflow trigger**.\n1. set the node's **input data mode** to **accept all data** or define the input items using fields or json if they're already known.\n1. in the sub-workflow [settings](../../workflows/settings/), set **save successful production executions** to **save**.\n1. skip ahead to setting up the parent workflow, and run it.\n1. follow the steps to [load data from previous executions](../../workflows/executions/debug/).\n1. adjust the **input data mode** to match the input sent by the parent workflow if necessary.\n\nyou can now pin example data in the trigger node, enabling you to work with real data while configuring the rest of the workflow.\n\n### call the sub-workflow\n\n1. open the workflow where you want to call the sub-workflow.\n\n1. add the **execute sub-workflow** node.\n\n1. in the **execute sub-workflow** node, set the sub-workflow you want to call. you can choose to call the workflow by id, load a workflow from a local file, add workflow json as a parameter in the node, or target a workflow by url.\n\n   find your workflow id\n\n   your sub-workflow's id is the alphanumeric string at the end of its url.\n\n1. fill in the required input items defined by the sub-workflow.\n\n1. save your workflow.\n\nwhen your workflow executes, it will send data to the sub-workflow, and run it.\n\nyou can follow the execution flow from the parent workflow to the sub-workflow by opening the execute sub-workflow node and selecting the **view sub-execution** link. likewise, the sub-workflow's execution contains a link back to the parent workflow's execution to navigate in the other direction.\n\n## how data passes between workflows\n\nas an example, imagine you have an execute sub-workflow node in **workflow a**. the execute sub-workflow node calls another workflow called **workflow b**:\n\n1. the execute sub-workflow node passes the data to the execute sub-workflow trigger node (titled \"when executed by another node\" in the canvas) of **workflow b**.\n1. the last node of **workflow b** sends the data back to the execute sub-workflow node in **workflow a**.\n\n## sub-workflow conversion\n\nsee [sub-workflow conversion](../../workflows/subworkflow-conversion/) for how to divide your existing workflows into sub-workflows.\n sub-workflows",
+        "fullText": "splitting with conditionals # sub-workflows\n\nyou can call one workflow from another workflow. this allows you to build modular, microservice-like workflows. it can also help if your workflow grows large enough to encounter [memory issues](../../hosting/scaling/memory-errors/). creating sub-workflows uses the [execute workflow](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) and [execute sub-workflow trigger](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflowtrigger/) nodes.\n\nsub-wokflow executions don't count towards your plan's monthly execution or active workflow limits.\n\n## set up and use a sub-workflow\n\nthis section walks through setting up both the parent workflow and sub-workflow.\n\n### create the sub-workflow\n\n1. create a new workflow.\n\n   create sub-workflows from existing workflows\n\n   you can optionally create a sub-workflow directly from an existing parent workflow using the [execute sub-workflow](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) node. in the node, select the **database** and **from list** options and select **create a sub-workflow** in the list.\n\n   you can also extract selected nodes directly using [sub-workflow conversion](../../workflows/subworkflow-conversion/) in the context menu.\n\n1. **optional**: configure which workflows can call the sub-workflow:\n\n   1. select the **options** menu > **settings**. n8n opens the **workflow settings** modal.\n   1. change the **this workflow can be called by** setting. refer to [workflow settings](../../workflows/settings/) for more information on configuring your workflows.\n\n1. add the **execute sub-workflow** trigger node (if you are searching under trigger nodes, this is also titled **when executed by another workflow**).\n\n1. set the **input data mode** to choose how you will define the sub-workflow's input data:\n\n   - **define using fields below**: choose this mode to define individual input names and data types that the calling workflow needs to provide. the [execute sub-workflow node](../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) or [call n8n workflow tool node](../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.toolworkflow/) in the calling workflow will automatically pull in the fields defined here.\n   - **define using json example**: choose this mode to provide an example json object that demonstrates the expected input items and their types.\n   - **accept all data**: choose this mode to accept all data unconditionally. the sub-workflow won't define any required input items. this sub-workflow must handle any input inconsistencies or missing values.\n\n1. add other nodes as needed to build your sub-workflow functionality.\n\n1. save the sub-workflow.\n\nsub-workflow mustn't contain errors\n\nif there are errors in the sub-workflow, the parent workflow can't trigger it.\n\nload data into sub-workflow before building\n\nthis requires the ability to [load data from previous executions](../../workflows/executions/debug/), which is available on n8n cloud and registered community plans.\n\nif you want to load data into your sub-workflow to use while building it:\n\n1. create the sub-workflow and add the **execute sub-workflow trigger**.\n1. set the node's **input data mode** to **accept all data** or define the input items using fields or json if they're already known.\n1. in the sub-workflow [settings](../../workflows/settings/), set **save successful production executions** to **save**.\n1. skip ahead to setting up the parent workflow, and run it.\n1. follow the steps to [load data from previous executions](../../workflows/executions/debug/).\n1. adjust the **input data mode** to match the input sent by the parent workflow if necessary.\n\nyou can now pin example data in the trigger node, enabling you to work with real data while configuring the rest of the workflow.\n\n### call the sub-workflow\n\n1. open the workflow where you want to call the sub-workflow.\n\n1. add the **execute sub-workflow** node.\n\n1. in the **execute sub-workflow** node, set the sub-workflow you want to call. you can choose to call the workflow by id, load a workflow from a local file, add workflow json as a parameter in the node, or target a workflow by url.\n\n   find your workflow id\n\n   your sub-workflow's id is the alphanumeric string at the end of its url.\n\n1. fill in the required input items defined by the sub-workflow.\n\n1. save your workflow.\n\nwhen your workflow executes, it will send data to the sub-workflow, and run it.\n\nyou can follow the execution flow from the parent workflow to the sub-workflow by opening the execute sub-workflow node and selecting the **view sub-execution** link. likewise, the sub-workflow's execution contains a link back to the parent workflow's execution to navigate in the other direction.\n\n## how data passes between workflows\n\nas an example, imagine you have an execute sub-workflow node in **workflow a**. the execute sub-workflow node calls another workflow called **workflow b**:\n\n1. the execute sub-workflow node passes the data to the execute sub-workflow trigger node (titled \"when executed by another node\" in the canvas) of **workflow b**.\n1. the last node of **workflow b** sends the data back to the execute sub-workflow node in **workflow a**.\n\n## sub-workflow conversion\n\nsee [sub-workflow conversion](../../workflows/subworkflow-conversion/) for how to divide your existing workflows into sub-workflows.\n sub-workflows",
         "importantTerms": [
           "workflow",
-          "workflows",
           "node",
           "data",
+          "workflows",
           "nodes",
           "execute",
           "input",
@@ -18099,78 +18043,6 @@
     },
     {
       "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",
@@ -18244,6 +18116,78 @@
         ]
       }
     },
+    {
+      "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",
@@ -58169,59 +58113,6 @@
     },
     {
       "id": "page-0758",
-      "title": "Cortex credentials",
-      "url": "https://docs.n8n.io/integrations/builtin/credentials/cortex/index.md",
-      "urlPath": "integrations/builtin/credentials/cortex/index.md",
-      "category": "other",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Cortex credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Cortex](../../app-nodes/n8n-nodes-base.cortex/)\n\n## Prerequisites\n\nInstall [Cortex](https://docs.strangebee.com/cortex/installation-and-configuration/) on your server.\n\n## Supported authentication methods\n\n- API key\n\n## Related resources\n\nRefer to [Cortex's API documentation](https://docs.strangebee.com/cortex/api/api-guide/) for more information about the service.\n\n## Using API key\n\nTo configure this credential, you'll need:\n\n- An **API Key**: Refer to the [Cortex API Authentication documentation](https://docs.strangebee.com/cortex/api/api-guide/#authentication) for detailed instructions on generating API keys.\n- The URL/Server Address for your **Cortex Instance** (defaults to `http://<your_server_address>:9001/`)\n",
-        "excerpt": "# Cortex credentials  You can use these credentials to authenticate the following nodes:  - [Cortex](../../app-nodes/n8n-nodes-base.cortex/)  ## Prerequisites  Install [Cortex](https://docs.strangebee.com/cortex/installation-and-configuration/) on your server.  ## Supported authentication methods  - API key  ## Related resources  Refer to [Cortex's API documentation](https://docs.strangebee.com/cortex/api/api-guide/) for more information about the service.  ## Using API key  To configure this cr...",
-        "sections": [
-          {
-            "title": "Cortex credentials",
-            "level": 1,
-            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Cortex](../../app-nodes/n8n-nodes-base.cortex/)"
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "cortex",
-          "credentials",
-          "prerequisites",
-          "supported",
-          "authentication",
-          "methods",
-          "related",
-          "resources",
-          "using"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "1 min",
-        "contentLength": 818,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "cortex credentials # cortex credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [cortex](../../app-nodes/n8n-nodes-base.cortex/)\n\n## prerequisites\n\ninstall [cortex](https://docs.strangebee.com/cortex/installation-and-configuration/) on your server.\n\n## supported authentication methods\n\n- api key\n\n## related resources\n\nrefer to [cortex's api documentation](https://docs.strangebee.com/cortex/api/api-guide/) for more information about the service.\n\n## using api key\n\nto configure this credential, you'll need:\n\n- an **api key**: refer to the [cortex api authentication documentation](https://docs.strangebee.com/cortex/api/api-guide/#authentication) for detailed instructions on generating api keys.\n- the url/server address for your **cortex instance** (defaults to `http://<your_server_address>:9001/`)\n cortex credentials",
-        "importantTerms": [
-          "cortex",
-          "credentials",
-          "nodes",
-          "https",
-          "docs",
-          "strangebee",
-          "authentication"
-        ]
-      }
-    },
-    {
-      "id": "page-0759",
       "title": "CrateDB credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/cratedb/index.md",
       "urlPath": "integrations/builtin/credentials/cratedb/index.md",
@@ -58278,7 +58169,7 @@
       }
     },
     {
-      "id": "page-0760",
+      "id": "page-0759",
       "title": "crowd.dev credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/crowddev/index.md",
       "urlPath": "integrations/builtin/credentials/crowddev/index.md",
@@ -58331,6 +58222,59 @@
         ]
       }
     },
+    {
+      "id": "page-0760",
+      "title": "Cortex credentials",
+      "url": "https://docs.n8n.io/integrations/builtin/credentials/cortex/index.md",
+      "urlPath": "integrations/builtin/credentials/cortex/index.md",
+      "category": "other",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Cortex credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Cortex](../../app-nodes/n8n-nodes-base.cortex/)\n\n## Prerequisites\n\nInstall [Cortex](https://docs.strangebee.com/cortex/installation-and-configuration/) on your server.\n\n## Supported authentication methods\n\n- API key\n\n## Related resources\n\nRefer to [Cortex's API documentation](https://docs.strangebee.com/cortex/api/api-guide/) for more information about the service.\n\n## Using API key\n\nTo configure this credential, you'll need:\n\n- An **API Key**: Refer to the [Cortex API Authentication documentation](https://docs.strangebee.com/cortex/api/api-guide/#authentication) for detailed instructions on generating API keys.\n- The URL/Server Address for your **Cortex Instance** (defaults to `http://<your_server_address>:9001/`)\n",
+        "excerpt": "# Cortex credentials  You can use these credentials to authenticate the following nodes:  - [Cortex](../../app-nodes/n8n-nodes-base.cortex/)  ## Prerequisites  Install [Cortex](https://docs.strangebee.com/cortex/installation-and-configuration/) on your server.  ## Supported authentication methods  - API key  ## Related resources  Refer to [Cortex's API documentation](https://docs.strangebee.com/cortex/api/api-guide/) for more information about the service.  ## Using API key  To configure this cr...",
+        "sections": [
+          {
+            "title": "Cortex credentials",
+            "level": 1,
+            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Cortex](../../app-nodes/n8n-nodes-base.cortex/)"
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "cortex",
+          "credentials",
+          "prerequisites",
+          "supported",
+          "authentication",
+          "methods",
+          "related",
+          "resources",
+          "using"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "1 min",
+        "contentLength": 818,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "cortex credentials # cortex credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [cortex](../../app-nodes/n8n-nodes-base.cortex/)\n\n## prerequisites\n\ninstall [cortex](https://docs.strangebee.com/cortex/installation-and-configuration/) on your server.\n\n## supported authentication methods\n\n- api key\n\n## related resources\n\nrefer to [cortex's api documentation](https://docs.strangebee.com/cortex/api/api-guide/) for more information about the service.\n\n## using api key\n\nto configure this credential, you'll need:\n\n- an **api key**: refer to the [cortex api authentication documentation](https://docs.strangebee.com/cortex/api/api-guide/#authentication) for detailed instructions on generating api keys.\n- the url/server address for your **cortex instance** (defaults to `http://<your_server_address>:9001/`)\n cortex credentials",
+        "importantTerms": [
+          "cortex",
+          "credentials",
+          "nodes",
+          "https",
+          "docs",
+          "strangebee",
+          "authentication"
+        ]
+      }
+    },
     {
       "id": "page-0761",
       "title": "CrowdStrike credentials",
@@ -68053,28 +67997,27 @@
     },
     {
       "id": "page-0914",
-      "title": "Quick Base credentials",
-      "url": "https://docs.n8n.io/integrations/builtin/credentials/quickbase/index.md",
-      "urlPath": "integrations/builtin/credentials/quickbase/index.md",
+      "title": "QuickBooks credentials",
+      "url": "https://docs.n8n.io/integrations/builtin/credentials/quickbooks/index.md",
+      "urlPath": "integrations/builtin/credentials/quickbooks/index.md",
       "category": "other",
       "subcategory": null,
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Quick Base credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Quick Base](../../app-nodes/n8n-nodes-base.quickbase/)\n\n## Prerequisites\n\nCreate a [Quick Base](https://www.quickbase.com/) account.\n\n## Supported authentication methods\n\n- API key\n\n## Related resources\n\nRefer to [Quick Base's API documentation](https://developer.quickbase.com/auth/) for more information about the service.\n\n## Using API key\n\nTo configure this credential, you'll need:\n\n- A **Hostname**: The string of characters located between `https://` and `/db` in your Quick Base URL.\n- A **User Token**: To generate a token, select your **Profile > My preferences > My User Information > Manage my user tokens**. Refer to [Creating and using user tokens](https://helpv2.quickbase.com/hc/en-us/articles/4570374095124-Creating-and-using-user-tokens) for detailed instructions.\n",
-        "excerpt": "# Quick Base credentials  You can use these credentials to authenticate the following nodes:  - [Quick Base](../../app-nodes/n8n-nodes-base.quickbase/)  ## Prerequisites  Create a [Quick Base](https://www.quickbase.com/) account.  ## Supported authentication methods  - API key  ## Related resources  Refer to [Quick Base's API documentation](https://developer.quickbase.com/auth/) for more information about the service.  ## Using API key  To configure this credential, you'll need:  - A **Hostname*...",
+        "markdown": "# QuickBooks credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [QuickBooks](../../app-nodes/n8n-nodes-base.quickbooks/)\n\n## Prerequisites\n\nCreate an [Intuit developer](https://developer.intuit.com/) account.\n\n## Supported authentication methods\n\n- OAuth2\n\n## Related resources\n\nRefer to [Intuit's API documentation](https://developer.intuit.com/app/developer/qbo/docs/develop) for more information about the service.\n\n## Using OAuth2\n\nTo configure this credential, you'll need:\n\n- A **Client ID**: Generated when you create an app.\n- A **Client Secret**: Generated when you create an app.\n- An **Environment**: Select whether this credential should access your **Production** or **Sandbox** environment.\n\nTo generate your **Client ID** and **Client Secret**, [create an app](https://developer.intuit.com/app/developer/qbo/docs/get-started/start-developing-your-app#create-an-app).\n\nUse these settings when creating your app:\n\n- Select appropriate scopes for your app. Refer to [Learn about scopes](https://developer.intuit.com/app/developer/qbo/docs/learn/scopes) for more information.\n- Enter the **OAuth Redirect URL** from n8n as a **Redirect URI** in the app's **Development > Keys & OAuth** section.\n- Copy the **Client ID** and **Client Secret** from the app's **Development > Keys & OAuth** section to enter in n8n. Refer to [Get the Client ID and Client Secret for your app](https://developer.intuit.com/app/developer/qbo/docs/get-started/get-client-id-and-client-secret) for more information.\n\nRefer to Intuit's [Set up OAuth 2.0 documentation](https://developer.intuit.com/app/developer/qbo/docs/develop/authentication-and-authorization/oauth-2.0) for more information on the entire process.\n\nEnvironment selection\n\nIf you're creating a new app from scratch, start with the **Sandbox** environment. Production apps need to fulfill all Intuit's requirements. Refer to Intuit's [Publish your app documentation](https://developer.intuit.com/app/developer/qbo/docs/go-live/publish-app) for more information.\n",
+        "excerpt": "# QuickBooks credentials  You can use these credentials to authenticate the following nodes:  - [QuickBooks](../../app-nodes/n8n-nodes-base.quickbooks/)  ## Prerequisites  Create an [Intuit developer](https://developer.intuit.com/) account.  ## Supported authentication methods  - OAuth2  ## Related resources  Refer to [Intuit's API documentation](https://developer.intuit.com/app/developer/qbo/docs/develop) for more information about the service.  ## Using OAuth2  To configure this credential, yo...",
         "sections": [
           {
-            "title": "Quick Base credentials",
+            "title": "QuickBooks credentials",
             "level": 1,
-            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Quick Base](../../app-nodes/n8n-nodes-base.quickbase/)"
+            "content": "You can use these credentials to authenticate the following nodes:\n\n- [QuickBooks](../../app-nodes/n8n-nodes-base.quickbooks/)"
           }
         ]
       },
       "metadata": {
         "keywords": [
-          "quick",
-          "base",
+          "quickbooks",
           "credentials",
           "prerequisites",
           "supported",
@@ -68082,54 +68025,67 @@
           "methods",
           "related",
           "resources",
-          "using"
+          "using",
+          "oauth2"
         ],
         "useCases": [],
         "operations": [],
         "codeExamples": 0,
         "complexity": "beginner",
-        "readingTime": "1 min",
-        "contentLength": 880,
+        "readingTime": "2 min",
+        "contentLength": 2047,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "quick base credentials # quick base credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [quick base](../../app-nodes/n8n-nodes-base.quickbase/)\n\n## prerequisites\n\ncreate a [quick base](https://www.quickbase.com/) account.\n\n## supported authentication methods\n\n- api key\n\n## related resources\n\nrefer to [quick base's api documentation](https://developer.quickbase.com/auth/) for more information about the service.\n\n## using api key\n\nto configure this credential, you'll need:\n\n- a **hostname**: the string of characters located between `https://` and `/db` in your quick base url.\n- a **user token**: to generate a token, select your **profile > my preferences > my user information > manage my user tokens**. refer to [creating and using user tokens](https://helpv2.quickbase.com/hc/en-us/articles/4570374095124-creating-and-using-user-tokens) for detailed instructions.\n quick base credentials",
+        "fullText": "quickbooks credentials # quickbooks credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [quickbooks](../../app-nodes/n8n-nodes-base.quickbooks/)\n\n## prerequisites\n\ncreate an [intuit developer](https://developer.intuit.com/) account.\n\n## supported authentication methods\n\n- oauth2\n\n## related resources\n\nrefer to [intuit's api documentation](https://developer.intuit.com/app/developer/qbo/docs/develop) for more information about the service.\n\n## using oauth2\n\nto configure this credential, you'll need:\n\n- a **client id**: generated when you create an app.\n- a **client secret**: generated when you create an app.\n- an **environment**: select whether this credential should access your **production** or **sandbox** environment.\n\nto generate your **client id** and **client secret**, [create an app](https://developer.intuit.com/app/developer/qbo/docs/get-started/start-developing-your-app#create-an-app).\n\nuse these settings when creating your app:\n\n- select appropriate scopes for your app. refer to [learn about scopes](https://developer.intuit.com/app/developer/qbo/docs/learn/scopes) for more information.\n- enter the **oauth redirect url** from n8n as a **redirect uri** in the app's **development > keys & oauth** section.\n- copy the **client id** and **client secret** from the app's **development > keys & oauth** section to enter in n8n. refer to [get the client id and client secret for your app](https://developer.intuit.com/app/developer/qbo/docs/get-started/get-client-id-and-client-secret) for more information.\n\nrefer to intuit's [set up oauth 2.0 documentation](https://developer.intuit.com/app/developer/qbo/docs/develop/authentication-and-authorization/oauth-2.0) for more information on the entire process.\n\nenvironment selection\n\nif you're creating a new app from scratch, start with the **sandbox** environment. production apps need to fulfill all intuit's requirements. refer to intuit's [publish your app documentation](https://developer.intuit.com/app/developer/qbo/docs/go-live/publish-app) for more information.\n quickbooks credentials",
         "importantTerms": [
-          "base",
-          "quick",
-          "user",
-          "credentials",
-          "quickbase",
+          "developer",
+          "intuit",
+          "client",
           "https",
+          "your",
+          "docs",
+          "quickbooks",
+          "create",
+          "refer",
+          "more",
+          "information",
+          "secret",
+          "oauth",
+          "credentials",
+          "environment",
           "nodes",
-          "using",
-          "tokens"
+          "documentation",
+          "when",
+          "scopes",
+          "from"
         ]
       }
     },
     {
       "id": "page-0915",
-      "title": "QuickBooks credentials",
-      "url": "https://docs.n8n.io/integrations/builtin/credentials/quickbooks/index.md",
-      "urlPath": "integrations/builtin/credentials/quickbooks/index.md",
+      "title": "Quick Base credentials",
+      "url": "https://docs.n8n.io/integrations/builtin/credentials/quickbase/index.md",
+      "urlPath": "integrations/builtin/credentials/quickbase/index.md",
       "category": "other",
       "subcategory": null,
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# QuickBooks credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [QuickBooks](../../app-nodes/n8n-nodes-base.quickbooks/)\n\n## Prerequisites\n\nCreate an [Intuit developer](https://developer.intuit.com/) account.\n\n## Supported authentication methods\n\n- OAuth2\n\n## Related resources\n\nRefer to [Intuit's API documentation](https://developer.intuit.com/app/developer/qbo/docs/develop) for more information about the service.\n\n## Using OAuth2\n\nTo configure this credential, you'll need:\n\n- A **Client ID**: Generated when you create an app.\n- A **Client Secret**: Generated when you create an app.\n- An **Environment**: Select whether this credential should access your **Production** or **Sandbox** environment.\n\nTo generate your **Client ID** and **Client Secret**, [create an app](https://developer.intuit.com/app/developer/qbo/docs/get-started/start-developing-your-app#create-an-app).\n\nUse these settings when creating your app:\n\n- Select appropriate scopes for your app. Refer to [Learn about scopes](https://developer.intuit.com/app/developer/qbo/docs/learn/scopes) for more information.\n- Enter the **OAuth Redirect URL** from n8n as a **Redirect URI** in the app's **Development > Keys & OAuth** section.\n- Copy the **Client ID** and **Client Secret** from the app's **Development > Keys & OAuth** section to enter in n8n. Refer to [Get the Client ID and Client Secret for your app](https://developer.intuit.com/app/developer/qbo/docs/get-started/get-client-id-and-client-secret) for more information.\n\nRefer to Intuit's [Set up OAuth 2.0 documentation](https://developer.intuit.com/app/developer/qbo/docs/develop/authentication-and-authorization/oauth-2.0) for more information on the entire process.\n\nEnvironment selection\n\nIf you're creating a new app from scratch, start with the **Sandbox** environment. Production apps need to fulfill all Intuit's requirements. Refer to Intuit's [Publish your app documentation](https://developer.intuit.com/app/developer/qbo/docs/go-live/publish-app) for more information.\n",
-        "excerpt": "# QuickBooks credentials  You can use these credentials to authenticate the following nodes:  - [QuickBooks](../../app-nodes/n8n-nodes-base.quickbooks/)  ## Prerequisites  Create an [Intuit developer](https://developer.intuit.com/) account.  ## Supported authentication methods  - OAuth2  ## Related resources  Refer to [Intuit's API documentation](https://developer.intuit.com/app/developer/qbo/docs/develop) for more information about the service.  ## Using OAuth2  To configure this credential, yo...",
+        "markdown": "# Quick Base credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Quick Base](../../app-nodes/n8n-nodes-base.quickbase/)\n\n## Prerequisites\n\nCreate a [Quick Base](https://www.quickbase.com/) account.\n\n## Supported authentication methods\n\n- API key\n\n## Related resources\n\nRefer to [Quick Base's API documentation](https://developer.quickbase.com/auth/) for more information about the service.\n\n## Using API key\n\nTo configure this credential, you'll need:\n\n- A **Hostname**: The string of characters located between `https://` and `/db` in your Quick Base URL.\n- A **User Token**: To generate a token, select your **Profile > My preferences > My User Information > Manage my user tokens**. Refer to [Creating and using user tokens](https://helpv2.quickbase.com/hc/en-us/articles/4570374095124-Creating-and-using-user-tokens) for detailed instructions.\n",
+        "excerpt": "# Quick Base credentials  You can use these credentials to authenticate the following nodes:  - [Quick Base](../../app-nodes/n8n-nodes-base.quickbase/)  ## Prerequisites  Create a [Quick Base](https://www.quickbase.com/) account.  ## Supported authentication methods  - API key  ## Related resources  Refer to [Quick Base's API documentation](https://developer.quickbase.com/auth/) for more information about the service.  ## Using API key  To configure this credential, you'll need:  - A **Hostname*...",
         "sections": [
           {
-            "title": "QuickBooks credentials",
+            "title": "Quick Base credentials",
             "level": 1,
-            "content": "You can use these credentials to authenticate the following nodes:\n\n- [QuickBooks](../../app-nodes/n8n-nodes-base.quickbooks/)"
+            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Quick Base](../../app-nodes/n8n-nodes-base.quickbase/)"
           }
         ]
       },
       "metadata": {
         "keywords": [
-          "quickbooks",
+          "quick",
+          "base",
           "credentials",
           "prerequisites",
           "supported",
@@ -68137,40 +68093,28 @@
           "methods",
           "related",
           "resources",
-          "using",
-          "oauth2"
+          "using"
         ],
         "useCases": [],
         "operations": [],
         "codeExamples": 0,
         "complexity": "beginner",
-        "readingTime": "2 min",
-        "contentLength": 2047,
+        "readingTime": "1 min",
+        "contentLength": 880,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "quickbooks credentials # quickbooks credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [quickbooks](../../app-nodes/n8n-nodes-base.quickbooks/)\n\n## prerequisites\n\ncreate an [intuit developer](https://developer.intuit.com/) account.\n\n## supported authentication methods\n\n- oauth2\n\n## related resources\n\nrefer to [intuit's api documentation](https://developer.intuit.com/app/developer/qbo/docs/develop) for more information about the service.\n\n## using oauth2\n\nto configure this credential, you'll need:\n\n- a **client id**: generated when you create an app.\n- a **client secret**: generated when you create an app.\n- an **environment**: select whether this credential should access your **production** or **sandbox** environment.\n\nto generate your **client id** and **client secret**, [create an app](https://developer.intuit.com/app/developer/qbo/docs/get-started/start-developing-your-app#create-an-app).\n\nuse these settings when creating your app:\n\n- select appropriate scopes for your app. refer to [learn about scopes](https://developer.intuit.com/app/developer/qbo/docs/learn/scopes) for more information.\n- enter the **oauth redirect url** from n8n as a **redirect uri** in the app's **development > keys & oauth** section.\n- copy the **client id** and **client secret** from the app's **development > keys & oauth** section to enter in n8n. refer to [get the client id and client secret for your app](https://developer.intuit.com/app/developer/qbo/docs/get-started/get-client-id-and-client-secret) for more information.\n\nrefer to intuit's [set up oauth 2.0 documentation](https://developer.intuit.com/app/developer/qbo/docs/develop/authentication-and-authorization/oauth-2.0) for more information on the entire process.\n\nenvironment selection\n\nif you're creating a new app from scratch, start with the **sandbox** environment. production apps need to fulfill all intuit's requirements. refer to intuit's [publish your app documentation](https://developer.intuit.com/app/developer/qbo/docs/go-live/publish-app) for more information.\n quickbooks credentials",
+        "fullText": "quick base credentials # quick base credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [quick base](../../app-nodes/n8n-nodes-base.quickbase/)\n\n## prerequisites\n\ncreate a [quick base](https://www.quickbase.com/) account.\n\n## supported authentication methods\n\n- api key\n\n## related resources\n\nrefer to [quick base's api documentation](https://developer.quickbase.com/auth/) for more information about the service.\n\n## using api key\n\nto configure this credential, you'll need:\n\n- a **hostname**: the string of characters located between `https://` and `/db` in your quick base url.\n- a **user token**: to generate a token, select your **profile > my preferences > my user information > manage my user tokens**. refer to [creating and using user tokens](https://helpv2.quickbase.com/hc/en-us/articles/4570374095124-creating-and-using-user-tokens) for detailed instructions.\n quick base credentials",
         "importantTerms": [
-          "developer",
-          "intuit",
-          "client",
-          "https",
-          "your",
-          "docs",
-          "quickbooks",
-          "create",
-          "refer",
-          "more",
-          "information",
-          "secret",
-          "oauth",
+          "base",
+          "quick",
+          "user",
           "credentials",
-          "environment",
+          "quickbase",
+          "https",
           "nodes",
-          "documentation",
-          "when",
-          "scopes",
-          "from"
+          "using",
+          "tokens"
         ]
       }
     },
@@ -89343,7 +89287,7 @@
         "page-0001",
         "page-0147",
         "page-0199",
-        "page-0225",
+        "page-0224",
         "page-0698"
       ],
       "start": [
@@ -89422,7 +89366,7 @@
         "page-0077",
         "page-0097",
         "page-0102",
-        "page-0112",
+        "page-0111",
         "page-0113",
         "page-0117",
         "page-0127",
@@ -90138,7 +90082,7 @@
         "page-0002",
         "page-0003",
         "page-0049",
-        "page-0112",
+        "page-0111",
         "page-0155",
         "page-0165",
         "page-0184",
@@ -90267,7 +90211,6 @@
         "page-0134",
         "page-0137",
         "page-0139",
-        "page-0144",
         "page-0146",
         "page-0149",
         "page-0151",
@@ -90354,7 +90297,7 @@
         "page-0002",
         "page-0200",
         "page-0218",
-        "page-0759",
+        "page-0758",
         "page-0780",
         "page-0782",
         "page-0796",
@@ -90502,7 +90445,7 @@
         "page-0002",
         "page-0048",
         "page-0061",
-        "page-0111",
+        "page-0112",
         "page-0632",
         "page-1187"
       ],
@@ -90562,7 +90505,6 @@
         "page-0137",
         "page-0139",
         "page-0142",
-        "page-0144",
         "page-0151",
         "page-0153",
         "page-0171",
@@ -90840,7 +90782,7 @@
         "page-0007",
         "page-0017",
         "page-0025",
-        "page-0112",
+        "page-0111",
         "page-0325",
         "page-0484",
         "page-0508",
@@ -90949,12 +90891,11 @@
         "page-0051",
         "page-0091",
         "page-0105",
-        "page-0112",
+        "page-0111",
         "page-0120",
         "page-0137",
         "page-0140",
         "page-0143",
-        "page-0144",
         "page-0149",
         "page-0151",
         "page-0191",
@@ -91718,7 +91659,7 @@
         "page-0003",
         "page-0078",
         "page-0103",
-        "page-0112",
+        "page-0111",
         "page-0171",
         "page-0206",
         "page-0209",
@@ -91909,7 +91850,7 @@
         "page-0092",
         "page-0094",
         "page-0106",
-        "page-0112",
+        "page-0111",
         "page-0137",
         "page-0147",
         "page-0155",
@@ -92558,7 +92499,7 @@
         "page-0139",
         "page-0141",
         "page-0192",
-        "page-0224",
+        "page-0225",
         "page-0325",
         "page-0484",
         "page-0508",
@@ -92898,7 +92839,7 @@
         "page-0077",
         "page-0102",
         "page-0105",
-        "page-0112",
+        "page-0111",
         "page-0113",
         "page-0117",
         "page-0120",
@@ -92996,7 +92937,7 @@
       "only": [
         "page-0005",
         "page-0164",
-        "page-0225",
+        "page-0224",
         "page-0508",
         "page-0515",
         "page-0620",
@@ -93552,7 +93493,7 @@
         "page-0095",
         "page-0096",
         "page-0097",
-        "page-0112",
+        "page-0111",
         "page-0156",
         "page-0158",
         "page-0159",
@@ -93715,7 +93656,7 @@
         "page-0147",
         "page-0149",
         "page-0150",
-        "page-0225",
+        "page-0224",
         "page-0226",
         "page-0840",
         "page-1127",
@@ -93789,7 +93730,7 @@
         "page-0017",
         "page-0044",
         "page-0045",
-        "page-0112",
+        "page-0111",
         "page-0148",
         "page-0154",
         "page-0156",
@@ -93817,7 +93758,7 @@
       ],
       "hosting": [
         "page-0009",
-        "page-0112",
+        "page-0111",
         "page-0148",
         "page-0196",
         "page-0197",
@@ -94660,7 +94601,6 @@
         "page-0093",
         "page-0134",
         "page-0139",
-        "page-0144",
         "page-0196",
         "page-0197",
         "page-0198",
@@ -94800,7 +94740,6 @@
         "page-0017",
         "page-0026",
         "page-0069",
-        "page-0144",
         "page-0637",
         "page-0644",
         "page-0645",
@@ -94837,7 +94776,7 @@
         "page-0046",
         "page-0047",
         "page-0131",
-        "page-0225",
+        "page-0224",
         "page-0516",
         "page-0610",
         "page-0625",
@@ -94852,7 +94791,7 @@
         "page-0042",
         "page-0047",
         "page-0131",
-        "page-0225",
+        "page-0224",
         "page-1202"
       ],
       "related": [
@@ -94862,7 +94801,7 @@
         "page-0076",
         "page-0080",
         "page-0083",
-        "page-0111",
+        "page-0112",
         "page-0138",
         "page-0210",
         "page-0214",
@@ -95388,7 +95327,7 @@
         "page-0076",
         "page-0080",
         "page-0083",
-        "page-0111",
+        "page-0112",
         "page-0196",
         "page-0197",
         "page-0201",
@@ -95915,7 +95854,7 @@
         "page-0016",
         "page-0024",
         "page-0103",
-        "page-0224",
+        "page-0225",
         "page-0226",
         "page-0977",
         "page-1203",
@@ -96543,7 +96482,7 @@
         "page-0899",
         "page-0901",
         "page-0907",
-        "page-0915",
+        "page-0914",
         "page-0920",
         "page-0925",
         "page-0936",
@@ -97245,7 +97184,7 @@
       ],
       "working": [
         "page-0018",
-        "page-0112",
+        "page-0111",
         "page-0425",
         "page-0513",
         "page-0523",
@@ -97490,7 +97429,7 @@
         "page-0201",
         "page-0202",
         "page-0203",
-        "page-0225",
+        "page-0224",
         "page-1138",
         "page-1141",
         "page-1189",
@@ -97861,7 +97800,6 @@
         "page-0027",
         "page-0044",
         "page-0134",
-        "page-0144",
         "page-0618",
         "page-0644",
         "page-0645",
@@ -98330,7 +98268,7 @@
       ],
       "scopes": [
         "page-0044",
-        "page-0224",
+        "page-0225",
         "page-0436",
         "page-0725",
         "page-0816",
@@ -98389,7 +98327,7 @@
         "page-0054",
         "page-0060",
         "page-0070",
-        "page-0225",
+        "page-0224",
         "page-0226",
         "page-0531",
         "page-0537",
@@ -101468,16 +101406,6 @@
       "conditional": [
         "page-0143"
       ],
-      "passes": [
-        "page-0144",
-        "page-0644",
-        "page-0645"
-      ],
-      "conversion": [
-        "page-0144",
-        "page-0672",
-        "page-1229"
-      ],
       "contributing": [
         "page-0146"
       ],
@@ -101926,7 +101854,7 @@
         "page-0158",
         "page-0415",
         "page-0579",
-        "page-0914",
+        "page-0915",
         "page-1024",
         "page-1141",
         "page-1154",
@@ -102923,7 +102851,7 @@
         "page-0688",
         "page-0716",
         "page-0723",
-        "page-0759",
+        "page-0758",
         "page-0787",
         "page-0860",
         "page-0869",
@@ -102962,16 +102890,11 @@
         "page-0223",
         "page-0558"
       ],
-      "actions": [
+      "integrations": [
         "page-0224",
         "page-0226",
-        "page-0228",
-        "page-0636",
-        "page-1235"
-      ],
-      "existing": [
-        "page-0224",
-        "page-1235"
+        "page-0227",
+        "page-0880"
       ],
       "operations": [
         "page-0224",
@@ -103294,22 +103217,27 @@
         "page-1166",
         "page-1186"
       ],
-      "predefined": [
+      "generic": [
         "page-0224",
         "page-0695",
-        "page-0815"
+        "page-1009",
+        "page-1219"
       ],
-      "integrations": [
+      "actions": [
         "page-0225",
         "page-0226",
-        "page-0227",
-        "page-0880"
+        "page-0228",
+        "page-0636",
+        "page-1235"
       ],
-      "generic": [
+      "existing": [
+        "page-0225",
+        "page-1235"
+      ],
+      "predefined": [
         "page-0225",
         "page-0695",
-        "page-1009",
-        "page-1219"
+        "page-0815"
       ],
       "operations:": [
         "page-0226",
@@ -103759,11 +103687,11 @@
       ],
       "cortex": [
         "page-0278",
-        "page-0758"
+        "page-0760"
       ],
       "cratedb": [
         "page-0279",
-        "page-0759"
+        "page-0758"
       ],
       "column's": [
         "page-0279",
@@ -103772,7 +103700,7 @@
       ],
       "crowd": [
         "page-0280",
-        "page-0760",
+        "page-0759",
         "page-1040",
         "page-1186"
       ],
@@ -104439,12 +104367,12 @@
       ],
       "quick": [
         "page-0415",
-        "page-0914",
+        "page-0915",
         "page-1200"
       ],
       "quickbooks": [
         "page-0416",
-        "page-0915"
+        "page-0914"
       ],
       "online": [
         "page-0416"
@@ -105975,6 +105903,10 @@
       "evaluating": [
         "page-0642"
       ],
+      "passes": [
+        "page-0644",
+        "page-0645"
+      ],
       "destination": [
         "page-0647",
         "page-0675"
@@ -106216,6 +106148,10 @@
       "(set)": [
         "page-0672"
       ],
+      "conversion": [
+        "page-0672",
+        "page-1229"
+      ],
       "(split": [
         "page-0674"
       ],
@@ -108556,7 +108492,6 @@
         "page-0141",
         "page-0142",
         "page-0143",
-        "page-0144",
         "page-0145"
       ],
       "hosting": [