@n8n-as-code/skills 1.7.0-next.5 → 1.7.0-next.7

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

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-04-03T14:29:40.602Z",
+  "generatedAt": "2026-04-03T15:01:32.369Z",
   "version": "1.0.0",
   "sourceUrl": "https://docs.n8n.io/llms.txt",
   "totalPages": 1262,
@@ -3921,102 +3921,6 @@
     },
     {
       "id": "page-0024",
-      "title": "Light evaluations",
-      "url": "https://docs.n8n.io/advanced-ai/evaluations/light-evaluations/index.md",
-      "urlPath": "advanced-ai/evaluations/light-evaluations/index.md",
-      "category": "advanced-ai",
-      "subcategory": "evaluations",
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Light evaluations\n\nAvailable on registered community and paid plans\n\nLight evaluations are available to registered community users and on all paid plans.\n\n## What are light evaluations?\n\nWhen building your workflow, you often want to test it with a handful of examples to get a sense of how it performs and make improvements. At this stage of workflow development, looking over workflow outputs for each example is often enough. The benefits of setting up more [formal scoring or metrics](../metric-based-evaluations/) don't yet justify the effort.\n\nLight evaluation allows you to run the examples in a test dataset through your workflow one-by-one, writing the outputs back to your dataset. You can then examine those outputs next to each other, and visually compare them to the expected outputs (if you have them).\n\n## How it works\n\nCredentials for Google Sheets\n\nEvaluations use data tables or Google Sheets to store the test dataset. To use Google Sheets as a dataset source, configure a [Google Sheets credential](../../../integrations/builtin/credentials/google/).\n\nLight evaluations take place in the 'Editor' tab of your workflow, although you’ll find instructions on how to set it up in the 'Evaluations' tab.\n\nSteps:\n\n1. Create a dataset\n1. Wire the dataset up to the workflow\n1. Write workflow outputs back to dataset\n1. Run evaluation\n\nThe following explanation will use a sample workflow that assigns a category and priority to incoming support tickets.\n\n### 1. Create a dataset\n\nCreate a data table or Google Sheet with a handful of examples for your workflow. Your dataset should contain columns for:\n\n- The workflow input\n- (Optional) The expected or correct workflow output\n- The actual output\n\nLeave the actual output column or columns blank, since you'll be filling them during the evaluation.\n\nA [sample dataset](https://docs.google.com/spreadsheets/d/1uuPS5cHtSNZ6HNLOi75A2m8nVWZrdBZ_Ivf58osDAS8/edit?gid=294497137#gid=294497137) for the support ticket classification workflow.\n\n### 2. Wire the dataset up to your workflow\n\n#### Insert an evaluation trigger to pull in your dataset\n\nEach time the [evaluation trigger](../../../integrations/builtin/core-nodes/n8n-nodes-base.evaluationtrigger/) runs, it will output a single item representing one row of your dataset.\n\nClicking the 'Evaluate all' button to the left of the evaluation trigger will run your workflow multiple times in sequence, once for each row in your dataset. This is a special behavior of the evaluation trigger.\n\nWhile wiring the trigger up, you often only want to run it once. You can do this by either:\n\n- Setting the trigger's 'Max rows to process' to 1\n- Clicking on the 'Execute node' button on the trigger (rather than the 'Evaluate all' button)\n\n#### Wire the trigger up to your workflow\n\nYou can now connect the evaluation trigger to the rest of your workflow and reference the data that it outputs. At a minimum, you need to use the dataset’s input column(s) later in the workflow.\n\nIf you have multiple triggers in your workflow you will need to [merge their branches together](../tips-and-common-issues/#combining-multiple-triggers).\n\nThe support ticket classification workflow with the evaluation trigger added in and wired up.\n\n### 3. Write workflow outputs back to dataset\n\nTo populate the output column(s) of your dataset when the evaluation runs:\n\n- Insert the 'Set outputs' action of the [evaluation node](../../../integrations/builtin/core-nodes/n8n-nodes-base.evaluation/)\n- Wire it up to your workflow at a point after it has produced the outputs you're evaluating\n- In the node's parameters, map the workflow outputs into the correct dataset column\n\nThe support ticket classification workflow with the 'set outputs' node added in and wired up.\n\n### 4. Run evaluation\n\nClick on the **Execute workflow** button to the left of the evaluation trigger. The workflow will execute multiple times, once for each row of the dataset:\n\nReview the outputs of each execution in the data table or Google Sheet, and examine the execution details using the workflow's 'executions' tab if you need to.\n\nOnce your dataset grows past a handful of examples, consider [metric-based evaluation](../metric-based-evaluations/) to get a numerical view of performance. See also [tips and common issues](../tips-and-common-issues/).\n",
-        "excerpt": "# Light evaluations  Available on registered community and paid plans  Light evaluations are available to registered community users and on all paid plans.  ## What are light evaluations?  When building your workflow, you often want to test it with a handful of examples to get a sense of how it performs and make improvements. At this stage of workflow development, looking over workflow outputs for each example is often enough. The benefits of setting up more [formal scoring or metrics](../metric...",
-        "sections": [
-          {
-            "title": "Light evaluations",
-            "level": 1,
-            "content": "Available on registered community and paid plans\n\nLight evaluations are available to registered community users and on all paid plans."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "light",
-          "evaluations",
-          "what",
-          "evaluations?",
-          "works",
-          "create",
-          "dataset",
-          "wire",
-          "your",
-          "workflow",
-          "insert",
-          "evaluation",
-          "trigger",
-          "pull",
-          "write",
-          "outputs",
-          "back"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "4 min",
-        "contentLength": 4319,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "light evaluations # light evaluations\n\navailable on registered community and paid plans\n\nlight evaluations are available to registered community users and on all paid plans.\n\n## what are light evaluations?\n\nwhen building your workflow, you often want to test it with a handful of examples to get a sense of how it performs and make improvements. at this stage of workflow development, looking over workflow outputs for each example is often enough. the benefits of setting up more [formal scoring or metrics](../metric-based-evaluations/) don't yet justify the effort.\n\nlight evaluation allows you to run the examples in a test dataset through your workflow one-by-one, writing the outputs back to your dataset. you can then examine those outputs next to each other, and visually compare them to the expected outputs (if you have them).\n\n## how it works\n\ncredentials for google sheets\n\nevaluations use data tables or google sheets to store the test dataset. to use google sheets as a dataset source, configure a [google sheets credential](../../../integrations/builtin/credentials/google/).\n\nlight evaluations take place in the 'editor' tab of your workflow, although you’ll find instructions on how to set it up in the 'evaluations' tab.\n\nsteps:\n\n1. create a dataset\n1. wire the dataset up to the workflow\n1. write workflow outputs back to dataset\n1. run evaluation\n\nthe following explanation will use a sample workflow that assigns a category and priority to incoming support tickets.\n\n### 1. create a dataset\n\ncreate a data table or google sheet with a handful of examples for your workflow. your dataset should contain columns for:\n\n- the workflow input\n- (optional) the expected or correct workflow output\n- the actual output\n\nleave the actual output column or columns blank, since you'll be filling them during the evaluation.\n\na [sample dataset](https://docs.google.com/spreadsheets/d/1uups5chtsnz6hnloi75a2m8nvwzrdbz_ivf58osdas8/edit?gid=294497137#gid=294497137) for the support ticket classification workflow.\n\n### 2. wire the dataset up to your workflow\n\n#### insert an evaluation trigger to pull in your dataset\n\neach time the [evaluation trigger](../../../integrations/builtin/core-nodes/n8n-nodes-base.evaluationtrigger/) runs, it will output a single item representing one row of your dataset.\n\nclicking the 'evaluate all' button to the left of the evaluation trigger will run your workflow multiple times in sequence, once for each row in your dataset. this is a special behavior of the evaluation trigger.\n\nwhile wiring the trigger up, you often only want to run it once. you can do this by either:\n\n- setting the trigger's 'max rows to process' to 1\n- clicking on the 'execute node' button on the trigger (rather than the 'evaluate all' button)\n\n#### wire the trigger up to your workflow\n\nyou can now connect the evaluation trigger to the rest of your workflow and reference the data that it outputs. at a minimum, you need to use the dataset’s input column(s) later in the workflow.\n\nif you have multiple triggers in your workflow you will need to [merge their branches together](../tips-and-common-issues/#combining-multiple-triggers).\n\nthe support ticket classification workflow with the evaluation trigger added in and wired up.\n\n### 3. write workflow outputs back to dataset\n\nto populate the output column(s) of your dataset when the evaluation runs:\n\n- insert the 'set outputs' action of the [evaluation node](../../../integrations/builtin/core-nodes/n8n-nodes-base.evaluation/)\n- wire it up to your workflow at a point after it has produced the outputs you're evaluating\n- in the node's parameters, map the workflow outputs into the correct dataset column\n\nthe support ticket classification workflow with the 'set outputs' node added in and wired up.\n\n### 4. run evaluation\n\nclick on the **execute workflow** button to the left of the evaluation trigger. the workflow will execute multiple times, once for each row of the dataset:\n\nreview the outputs of each execution in the data table or google sheet, and examine the execution details using the workflow's 'executions' tab if you need to.\n\nonce your dataset grows past a handful of examples, consider [metric-based evaluation](../metric-based-evaluations/) to get a numerical view of performance. see also [tips and common issues](../tips-and-common-issues/).\n light evaluations",
-        "importantTerms": [
-          "workflow",
-          "dataset",
-          "your",
-          "evaluation",
-          "outputs",
-          "trigger",
-          "evaluations",
-          "google",
-          "light",
-          "each",
-          "will",
-          "output",
-          "with",
-          "examples",
-          "sheets",
-          "data",
-          "wire",
-          "support",
-          "column",
-          "nodes",
-          "button",
-          "multiple",
-          "once",
-          "node",
-          "often",
-          "test",
-          "handful",
-          "this",
-          "metric",
-          "based",
-          "back",
-          "them",
-          "integrations",
-          "builtin",
-          "create",
-          "ticket",
-          "classification",
-          "execute",
-          "need",
-          "tips",
-          "common",
-          "issues"
-        ]
-      }
-    },
-    {
-      "id": "page-0025",
       "title": "Metric-based evaluations",
       "url": "https://docs.n8n.io/advanced-ai/evaluations/metric-based-evaluations/index.md",
       "urlPath": "advanced-ai/evaluations/metric-based-evaluations/index.md",
@@ -4110,7 +4014,7 @@
       }
     },
     {
-      "id": "page-0026",
+      "id": "page-0025",
       "title": "Overview",
       "url": "https://docs.n8n.io/advanced-ai/evaluations/overview/index.md",
       "urlPath": "advanced-ai/evaluations/overview/index.md",
@@ -4190,7 +4094,7 @@
       }
     },
     {
-      "id": "page-0027",
+      "id": "page-0026",
       "title": "Tips and common issues",
       "url": "https://docs.n8n.io/advanced-ai/evaluations/tips-and-common-issues/index.md",
       "urlPath": "advanced-ai/evaluations/tips-and-common-issues/index.md",
@@ -4296,7 +4200,7 @@
       }
     },
     {
-      "id": "page-0028",
+      "id": "page-0027",
       "title": "Agents vs chains example",
       "url": "https://docs.n8n.io/advanced-ai/examples/agent-chain-comparison/index.md",
       "urlPath": "advanced-ai/examples/agent-chain-comparison/index.md",
@@ -4358,7 +4262,7 @@
       }
     },
     {
-      "id": "page-0029",
+      "id": "page-0028",
       "title": "Call an API to fetch data",
       "url": "https://docs.n8n.io/advanced-ai/examples/api-workflow-tool/index.md",
       "urlPath": "advanced-ai/examples/api-workflow-tool/index.md",
@@ -4422,7 +4326,7 @@
       }
     },
     {
-      "id": "page-0030",
+      "id": "page-0029",
       "title": "Use Google Sheets as a data source",
       "url": "https://docs.n8n.io/advanced-ai/examples/data-google-sheets/index.md",
       "urlPath": "advanced-ai/examples/data-google-sheets/index.md",
@@ -4489,6 +4393,102 @@
         ]
       }
     },
+    {
+      "id": "page-0030",
+      "title": "Light evaluations",
+      "url": "https://docs.n8n.io/advanced-ai/evaluations/light-evaluations/index.md",
+      "urlPath": "advanced-ai/evaluations/light-evaluations/index.md",
+      "category": "advanced-ai",
+      "subcategory": "evaluations",
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Light evaluations\n\nAvailable on registered community and paid plans\n\nLight evaluations are available to registered community users and on all paid plans.\n\n## What are light evaluations?\n\nWhen building your workflow, you often want to test it with a handful of examples to get a sense of how it performs and make improvements. At this stage of workflow development, looking over workflow outputs for each example is often enough. The benefits of setting up more [formal scoring or metrics](../metric-based-evaluations/) don't yet justify the effort.\n\nLight evaluation allows you to run the examples in a test dataset through your workflow one-by-one, writing the outputs back to your dataset. You can then examine those outputs next to each other, and visually compare them to the expected outputs (if you have them).\n\n## How it works\n\nCredentials for Google Sheets\n\nEvaluations use data tables or Google Sheets to store the test dataset. To use Google Sheets as a dataset source, configure a [Google Sheets credential](../../../integrations/builtin/credentials/google/).\n\nLight evaluations take place in the 'Editor' tab of your workflow, although you’ll find instructions on how to set it up in the 'Evaluations' tab.\n\nSteps:\n\n1. Create a dataset\n1. Wire the dataset up to the workflow\n1. Write workflow outputs back to dataset\n1. Run evaluation\n\nThe following explanation will use a sample workflow that assigns a category and priority to incoming support tickets.\n\n### 1. Create a dataset\n\nCreate a data table or Google Sheet with a handful of examples for your workflow. Your dataset should contain columns for:\n\n- The workflow input\n- (Optional) The expected or correct workflow output\n- The actual output\n\nLeave the actual output column or columns blank, since you'll be filling them during the evaluation.\n\nA [sample dataset](https://docs.google.com/spreadsheets/d/1uuPS5cHtSNZ6HNLOi75A2m8nVWZrdBZ_Ivf58osDAS8/edit?gid=294497137#gid=294497137) for the support ticket classification workflow.\n\n### 2. Wire the dataset up to your workflow\n\n#### Insert an evaluation trigger to pull in your dataset\n\nEach time the [evaluation trigger](../../../integrations/builtin/core-nodes/n8n-nodes-base.evaluationtrigger/) runs, it will output a single item representing one row of your dataset.\n\nClicking the 'Evaluate all' button to the left of the evaluation trigger will run your workflow multiple times in sequence, once for each row in your dataset. This is a special behavior of the evaluation trigger.\n\nWhile wiring the trigger up, you often only want to run it once. You can do this by either:\n\n- Setting the trigger's 'Max rows to process' to 1\n- Clicking on the 'Execute node' button on the trigger (rather than the 'Evaluate all' button)\n\n#### Wire the trigger up to your workflow\n\nYou can now connect the evaluation trigger to the rest of your workflow and reference the data that it outputs. At a minimum, you need to use the dataset’s input column(s) later in the workflow.\n\nIf you have multiple triggers in your workflow you will need to [merge their branches together](../tips-and-common-issues/#combining-multiple-triggers).\n\nThe support ticket classification workflow with the evaluation trigger added in and wired up.\n\n### 3. Write workflow outputs back to dataset\n\nTo populate the output column(s) of your dataset when the evaluation runs:\n\n- Insert the 'Set outputs' action of the [evaluation node](../../../integrations/builtin/core-nodes/n8n-nodes-base.evaluation/)\n- Wire it up to your workflow at a point after it has produced the outputs you're evaluating\n- In the node's parameters, map the workflow outputs into the correct dataset column\n\nThe support ticket classification workflow with the 'set outputs' node added in and wired up.\n\n### 4. Run evaluation\n\nClick on the **Execute workflow** button to the left of the evaluation trigger. The workflow will execute multiple times, once for each row of the dataset:\n\nReview the outputs of each execution in the data table or Google Sheet, and examine the execution details using the workflow's 'executions' tab if you need to.\n\nOnce your dataset grows past a handful of examples, consider [metric-based evaluation](../metric-based-evaluations/) to get a numerical view of performance. See also [tips and common issues](../tips-and-common-issues/).\n",
+        "excerpt": "# Light evaluations  Available on registered community and paid plans  Light evaluations are available to registered community users and on all paid plans.  ## What are light evaluations?  When building your workflow, you often want to test it with a handful of examples to get a sense of how it performs and make improvements. At this stage of workflow development, looking over workflow outputs for each example is often enough. The benefits of setting up more [formal scoring or metrics](../metric...",
+        "sections": [
+          {
+            "title": "Light evaluations",
+            "level": 1,
+            "content": "Available on registered community and paid plans\n\nLight evaluations are available to registered community users and on all paid plans."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "light",
+          "evaluations",
+          "what",
+          "evaluations?",
+          "works",
+          "create",
+          "dataset",
+          "wire",
+          "your",
+          "workflow",
+          "insert",
+          "evaluation",
+          "trigger",
+          "pull",
+          "write",
+          "outputs",
+          "back"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "4 min",
+        "contentLength": 4319,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "light evaluations # light evaluations\n\navailable on registered community and paid plans\n\nlight evaluations are available to registered community users and on all paid plans.\n\n## what are light evaluations?\n\nwhen building your workflow, you often want to test it with a handful of examples to get a sense of how it performs and make improvements. at this stage of workflow development, looking over workflow outputs for each example is often enough. the benefits of setting up more [formal scoring or metrics](../metric-based-evaluations/) don't yet justify the effort.\n\nlight evaluation allows you to run the examples in a test dataset through your workflow one-by-one, writing the outputs back to your dataset. you can then examine those outputs next to each other, and visually compare them to the expected outputs (if you have them).\n\n## how it works\n\ncredentials for google sheets\n\nevaluations use data tables or google sheets to store the test dataset. to use google sheets as a dataset source, configure a [google sheets credential](../../../integrations/builtin/credentials/google/).\n\nlight evaluations take place in the 'editor' tab of your workflow, although you’ll find instructions on how to set it up in the 'evaluations' tab.\n\nsteps:\n\n1. create a dataset\n1. wire the dataset up to the workflow\n1. write workflow outputs back to dataset\n1. run evaluation\n\nthe following explanation will use a sample workflow that assigns a category and priority to incoming support tickets.\n\n### 1. create a dataset\n\ncreate a data table or google sheet with a handful of examples for your workflow. your dataset should contain columns for:\n\n- the workflow input\n- (optional) the expected or correct workflow output\n- the actual output\n\nleave the actual output column or columns blank, since you'll be filling them during the evaluation.\n\na [sample dataset](https://docs.google.com/spreadsheets/d/1uups5chtsnz6hnloi75a2m8nvwzrdbz_ivf58osdas8/edit?gid=294497137#gid=294497137) for the support ticket classification workflow.\n\n### 2. wire the dataset up to your workflow\n\n#### insert an evaluation trigger to pull in your dataset\n\neach time the [evaluation trigger](../../../integrations/builtin/core-nodes/n8n-nodes-base.evaluationtrigger/) runs, it will output a single item representing one row of your dataset.\n\nclicking the 'evaluate all' button to the left of the evaluation trigger will run your workflow multiple times in sequence, once for each row in your dataset. this is a special behavior of the evaluation trigger.\n\nwhile wiring the trigger up, you often only want to run it once. you can do this by either:\n\n- setting the trigger's 'max rows to process' to 1\n- clicking on the 'execute node' button on the trigger (rather than the 'evaluate all' button)\n\n#### wire the trigger up to your workflow\n\nyou can now connect the evaluation trigger to the rest of your workflow and reference the data that it outputs. at a minimum, you need to use the dataset’s input column(s) later in the workflow.\n\nif you have multiple triggers in your workflow you will need to [merge their branches together](../tips-and-common-issues/#combining-multiple-triggers).\n\nthe support ticket classification workflow with the evaluation trigger added in and wired up.\n\n### 3. write workflow outputs back to dataset\n\nto populate the output column(s) of your dataset when the evaluation runs:\n\n- insert the 'set outputs' action of the [evaluation node](../../../integrations/builtin/core-nodes/n8n-nodes-base.evaluation/)\n- wire it up to your workflow at a point after it has produced the outputs you're evaluating\n- in the node's parameters, map the workflow outputs into the correct dataset column\n\nthe support ticket classification workflow with the 'set outputs' node added in and wired up.\n\n### 4. run evaluation\n\nclick on the **execute workflow** button to the left of the evaluation trigger. the workflow will execute multiple times, once for each row of the dataset:\n\nreview the outputs of each execution in the data table or google sheet, and examine the execution details using the workflow's 'executions' tab if you need to.\n\nonce your dataset grows past a handful of examples, consider [metric-based evaluation](../metric-based-evaluations/) to get a numerical view of performance. see also [tips and common issues](../tips-and-common-issues/).\n light evaluations",
+        "importantTerms": [
+          "workflow",
+          "dataset",
+          "your",
+          "evaluation",
+          "outputs",
+          "trigger",
+          "evaluations",
+          "google",
+          "light",
+          "each",
+          "will",
+          "output",
+          "with",
+          "examples",
+          "sheets",
+          "data",
+          "wire",
+          "support",
+          "column",
+          "nodes",
+          "button",
+          "multiple",
+          "once",
+          "node",
+          "often",
+          "test",
+          "handful",
+          "this",
+          "metric",
+          "based",
+          "back",
+          "them",
+          "integrations",
+          "builtin",
+          "create",
+          "ticket",
+          "classification",
+          "execute",
+          "need",
+          "tips",
+          "common",
+          "issues"
+        ]
+      }
+    },
     {
       "id": "page-0031",
       "title": "Set a human fallback for AI workflows",
@@ -9710,6 +9710,52 @@
     },
     {
       "id": "page-0103",
+      "title": "Referencing data",
+      "url": "https://docs.n8n.io/data/data-mapping/index.md",
+      "urlPath": "data/data-mapping/index.md",
+      "category": "data",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Referencing data\n\nReferencing data, or data mapping, means accessing information from previous nodes in your workflow. This allows you to use output from earlier steps as input for later nodes, creating dynamic workflows that pass data through multiple operations.\n\nWhen you reference data, you're not changing it. You're pointing to values that already exist so you can use them in node parameters, expressions, or custom code.\n\nIf you want to change the data you're referencing, see [Transforming data](../transforming-data/).\n\n## How to reference data\n\nThe main way to reference data is using [expressions](../expressions/#expressions). You can create expressions by typing them in a parameter's field or dragging and dropping fields from the Input panel in the UI. Expressions will automatically figure out the correct item to use using [item linking](data-item-linking/).\n",
+        "excerpt": "# Referencing data  Referencing data, or data mapping, means accessing information from previous nodes in your workflow. This allows you to use output from earlier steps as input for later nodes, creating dynamic workflows that pass data through multiple operations.  When you reference data, you're not changing it. You're pointing to values that already exist so you can use them in node parameters, expressions, or custom code.  If you want to change the data you're referencing, see [Transforming...",
+        "sections": [
+          {
+            "title": "Referencing data",
+            "level": 1,
+            "content": "Referencing data, or data mapping, means accessing information from previous nodes in your workflow. This allows you to use output from earlier steps as input for later nodes, creating dynamic workflows that pass data through multiple operations.\n\nWhen you reference data, you're not changing it. You're pointing to values that already exist so you can use them in node parameters, expressions, or custom code.\n\nIf you want to change the data you're referencing, see [Transforming data](../transforming-data/)."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "referencing",
+          "data",
+          "reference"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "1 min",
+        "contentLength": 879,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "referencing data # referencing data\n\nreferencing data, or data mapping, means accessing information from previous nodes in your workflow. this allows you to use output from earlier steps as input for later nodes, creating dynamic workflows that pass data through multiple operations.\n\nwhen you reference data, you're not changing it. you're pointing to values that already exist so you can use them in node parameters, expressions, or custom code.\n\nif you want to change the data you're referencing, see [transforming data](../transforming-data/).\n\n## how to reference data\n\nthe main way to reference data is using [expressions](../expressions/#expressions). you can create expressions by typing them in a parameter's field or dragging and dropping fields from the input panel in the ui. expressions will automatically figure out the correct item to use using [item linking](data-item-linking/).\n referencing data",
+        "importantTerms": [
+          "data",
+          "expressions",
+          "referencing",
+          "from",
+          "reference",
+          "item"
+        ]
+      }
+    },
+    {
+      "id": "page-0104",
       "title": "Referencing data in the UI",
       "url": "https://docs.n8n.io/data/data-mapping/data-mapping-ui/index.md",
       "urlPath": "data/data-mapping/data-mapping-ui/index.md",
@@ -9757,7 +9803,7 @@
       }
     },
     {
-      "id": "page-0104",
+      "id": "page-0105",
       "title": "Accessing linked items in the Code node",
       "url": "https://docs.n8n.io/data/data-mapping/itemmatching/index.md",
       "urlPath": "data/data-mapping/itemmatching/index.md",
@@ -9820,7 +9866,7 @@
       }
     },
     {
-      "id": "page-0105",
+      "id": "page-0106",
       "title": "Referencing previous nodes",
       "url": "https://docs.n8n.io/data/data-mapping/referencing-other-nodes/index.md",
       "urlPath": "data/data-mapping/referencing-other-nodes/index.md",
@@ -9918,7 +9964,7 @@
       }
     },
     {
-      "id": "page-0106",
+      "id": "page-0107",
       "title": "Linking data items",
       "url": "https://docs.n8n.io/data/data-mapping/data-item-linking/index.md",
       "urlPath": "data/data-mapping/data-item-linking/index.md",
@@ -9965,52 +10011,6 @@
         ]
       }
     },
-    {
-      "id": "page-0107",
-      "title": "Referencing data",
-      "url": "https://docs.n8n.io/data/data-mapping/index.md",
-      "urlPath": "data/data-mapping/index.md",
-      "category": "data",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Referencing data\n\nReferencing data, or data mapping, means accessing information from previous nodes in your workflow. This allows you to use output from earlier steps as input for later nodes, creating dynamic workflows that pass data through multiple operations.\n\nWhen you reference data, you're not changing it. You're pointing to values that already exist so you can use them in node parameters, expressions, or custom code.\n\nIf you want to change the data you're referencing, see [Transforming data](../transforming-data/).\n\n## How to reference data\n\nThe main way to reference data is using [expressions](../expressions/#expressions). You can create expressions by typing them in a parameter's field or dragging and dropping fields from the Input panel in the UI. Expressions will automatically figure out the correct item to use using [item linking](data-item-linking/).\n",
-        "excerpt": "# Referencing data  Referencing data, or data mapping, means accessing information from previous nodes in your workflow. This allows you to use output from earlier steps as input for later nodes, creating dynamic workflows that pass data through multiple operations.  When you reference data, you're not changing it. You're pointing to values that already exist so you can use them in node parameters, expressions, or custom code.  If you want to change the data you're referencing, see [Transforming...",
-        "sections": [
-          {
-            "title": "Referencing data",
-            "level": 1,
-            "content": "Referencing data, or data mapping, means accessing information from previous nodes in your workflow. This allows you to use output from earlier steps as input for later nodes, creating dynamic workflows that pass data through multiple operations.\n\nWhen you reference data, you're not changing it. You're pointing to values that already exist so you can use them in node parameters, expressions, or custom code.\n\nIf you want to change the data you're referencing, see [Transforming data](../transforming-data/)."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "referencing",
-          "data",
-          "reference"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "1 min",
-        "contentLength": 879,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "referencing data # referencing data\n\nreferencing data, or data mapping, means accessing information from previous nodes in your workflow. this allows you to use output from earlier steps as input for later nodes, creating dynamic workflows that pass data through multiple operations.\n\nwhen you reference data, you're not changing it. you're pointing to values that already exist so you can use them in node parameters, expressions, or custom code.\n\nif you want to change the data you're referencing, see [transforming data](../transforming-data/).\n\n## how to reference data\n\nthe main way to reference data is using [expressions](../expressions/#expressions). you can create expressions by typing them in a parameter's field or dragging and dropping fields from the input panel in the ui. expressions will automatically figure out the correct item to use using [item linking](data-item-linking/).\n referencing data",
-        "importantTerms": [
-          "data",
-          "expressions",
-          "referencing",
-          "from",
-          "reference",
-          "item"
-        ]
-      }
-    },
     {
       "id": "page-0108",
       "title": "Preserving linking in the Code node",
@@ -29355,6 +29355,78 @@
     },
     {
       "id": "page-0370",
+      "title": "Medium",
+      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.medium/index.md",
+      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.medium/index.md",
+      "category": "integrations",
+      "subcategory": "app-nodes",
+      "nodeName": "medium",
+      "nodeType": "n8n-nodes-base.medium",
+      "content": {
+        "markdown": "# Medium node\n\nUse the Medium node to automate work in Medium, and integrate Medium with other applications. n8n has built-in support for a wide range of Medium features, including creating posts, and getting publications.\n\nOn this page, you'll find a list of operations the Medium node supports and links to more resources.\n\nMedium API no longer supported\n\nMedium has stopped supporting the Medium API. The Medium node still appears within n8n, but you won't be able to configure new API keys to authenticate with.\n\nRefer to [Medium credentials](../../credentials/medium/) for guidance on setting up existing API keys.\n\nThis node can be used as an AI tool\n\nThis node can be used to enhance the capabilities of an AI agent. When used in this way, many parameters can be set automatically, or with information directed by AI - find out more in the [AI tool parameters documentation](../../../../advanced-ai/examples/using-the-fromai-function/).\n\n## Operations\n\n- Post\n  - Create a post\n- Publication\n  - Get all publications\n\n## Templates and examples\n\n**Cross-post your blog posts**\n\nby amudhan\n\n[View template details](https://n8n.io/workflows/418-cross-post-your-blog-posts/)\n\n**Posting from Wordpress to Medium**\n\nby Zacharia Kimotho\n\n[View template details](https://n8n.io/workflows/2062-posting-from-wordpress-to-medium/)\n\n**Publish a post to a publication on Medium**\n\nby Harshil Agrawal\n\n[View template details](https://n8n.io/workflows/594-publish-a-post-to-a-publication-on-medium/)\n\n[Browse Medium integration templates](https://n8n.io/integrations/medium/), or [search all templates](https://n8n.io/workflows/)\n\n## What to do if your operation isn't supported\n\nIf this node doesn't support the operation you want to do, you can use the [HTTP Request node](../../core-nodes/n8n-nodes-base.httprequest/) to call the service's API.\n\nYou can use the credential you created for this service in the HTTP Request node:\n\n1. In the HTTP Request node, select **Authentication** > **Predefined Credential Type**.\n1. Select the service you want to connect to.\n1. Select your credential.\n\nRefer to [Custom API operations](../../../custom-operations/) for more information.\n",
+        "excerpt": "# Medium node  Use the Medium node to automate work in Medium, and integrate Medium with other applications. n8n has built-in support for a wide range of Medium features, including creating posts, and getting publications.  On this page, you'll find a list of operations the Medium node supports and links to more resources.  Medium API no longer supported  Medium has stopped supporting the Medium API. The Medium node still appears within n8n, but you won't be able to configure new API keys to aut...",
+        "sections": [
+          {
+            "title": "Medium node",
+            "level": 1,
+            "content": "Use the Medium node to automate work in Medium, and integrate Medium with other applications. n8n has built-in support for a wide range of Medium features, including creating posts, and getting publications.\n\nOn this page, you'll find a list of operations the Medium node supports and links to more resources.\n\nMedium API no longer supported\n\nMedium has stopped supporting the Medium API. The Medium node still appears within n8n, but you won't be able to configure new API keys to authenticate with.\n\nRefer to [Medium credentials](../../credentials/medium/) for guidance on setting up existing API keys.\n\nThis node can be used as an AI tool\n\nThis node can be used to enhance the capabilities of an AI agent. When used in this way, many parameters can be set automatically, or with information directed by AI - find out more in the [AI tool parameters documentation](../../../../advanced-ai/examples/using-the-fromai-function/)."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "medium",
+          "node",
+          "operations",
+          "templates",
+          "examples",
+          "what",
+          "your",
+          "operation",
+          "isn't",
+          "supported"
+        ],
+        "useCases": [],
+        "operations": [
+          "",
+          "what to do if your  isn't supported"
+        ],
+        "codeExamples": 0,
+        "complexity": "intermediate",
+        "readingTime": "2 min",
+        "contentLength": 2171,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "medium # medium node\n\nuse the medium node to automate work in medium, and integrate medium with other applications. n8n has built-in support for a wide range of medium features, including creating posts, and getting publications.\n\non this page, you'll find a list of operations the medium node supports and links to more resources.\n\nmedium api no longer supported\n\nmedium has stopped supporting the medium api. the medium node still appears within n8n, but you won't be able to configure new api keys to authenticate with.\n\nrefer to [medium credentials](../../credentials/medium/) for guidance on setting up existing api keys.\n\nthis node can be used as an ai tool\n\nthis node can be used to enhance the capabilities of an ai agent. when used in this way, many parameters can be set automatically, or with information directed by ai - find out more in the [ai tool parameters documentation](../../../../advanced-ai/examples/using-the-fromai-function/).\n\n## operations\n\n- post\n  - create a post\n- publication\n  - get all publications\n\n## templates and examples\n\n**cross-post your blog posts**\n\nby amudhan\n\n[view template details](https://n8n.io/workflows/418-cross-post-your-blog-posts/)\n\n**posting from wordpress to medium**\n\nby zacharia kimotho\n\n[view template details](https://n8n.io/workflows/2062-posting-from-wordpress-to-medium/)\n\n**publish a post to a publication on medium**\n\nby harshil agrawal\n\n[view template details](https://n8n.io/workflows/594-publish-a-post-to-a-publication-on-medium/)\n\n[browse medium integration templates](https://n8n.io/integrations/medium/), or [search all templates](https://n8n.io/workflows/)\n\n## what to do if your operation isn't supported\n\nif this node doesn't support the operation you want to do, you can use the [http request node](../../core-nodes/n8n-nodes-base.httprequest/) to call the service's api.\n\nyou can use the credential you created for this service in the http request node:\n\n1. in the http request node, select **authentication** > **predefined credential type**.\n1. select the service you want to connect to.\n1. select your credential.\n\nrefer to [custom api operations](../../../custom-operations/) for more information.\n medium node",
+        "importantTerms": [
+          "medium",
+          "node",
+          "this",
+          "post",
+          "https",
+          "operations",
+          "your",
+          "workflows",
+          "with",
+          "posts",
+          "more",
+          "used",
+          "publication",
+          "templates",
+          "view",
+          "template",
+          "details",
+          "http",
+          "request",
+          "service",
+          "credential",
+          "select"
+        ]
+      }
+    },
+    {
+      "id": "page-0371",
       "title": "MessageBird",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.messagebird/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.messagebird/index.md",
@@ -29402,7 +29474,7 @@
       }
     },
     {
-      "id": "page-0371",
+      "id": "page-0372",
       "title": "Metabase",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.metabase/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.metabase/index.md",
@@ -29462,78 +29534,6 @@
         ]
       }
     },
-    {
-      "id": "page-0372",
-      "title": "Medium",
-      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.medium/index.md",
-      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.medium/index.md",
-      "category": "integrations",
-      "subcategory": "app-nodes",
-      "nodeName": "medium",
-      "nodeType": "n8n-nodes-base.medium",
-      "content": {
-        "markdown": "# Medium node\n\nUse the Medium node to automate work in Medium, and integrate Medium with other applications. n8n has built-in support for a wide range of Medium features, including creating posts, and getting publications.\n\nOn this page, you'll find a list of operations the Medium node supports and links to more resources.\n\nMedium API no longer supported\n\nMedium has stopped supporting the Medium API. The Medium node still appears within n8n, but you won't be able to configure new API keys to authenticate with.\n\nRefer to [Medium credentials](../../credentials/medium/) for guidance on setting up existing API keys.\n\nThis node can be used as an AI tool\n\nThis node can be used to enhance the capabilities of an AI agent. When used in this way, many parameters can be set automatically, or with information directed by AI - find out more in the [AI tool parameters documentation](../../../../advanced-ai/examples/using-the-fromai-function/).\n\n## Operations\n\n- Post\n  - Create a post\n- Publication\n  - Get all publications\n\n## Templates and examples\n\n**Cross-post your blog posts**\n\nby amudhan\n\n[View template details](https://n8n.io/workflows/418-cross-post-your-blog-posts/)\n\n**Posting from Wordpress to Medium**\n\nby Zacharia Kimotho\n\n[View template details](https://n8n.io/workflows/2062-posting-from-wordpress-to-medium/)\n\n**Publish a post to a publication on Medium**\n\nby Harshil Agrawal\n\n[View template details](https://n8n.io/workflows/594-publish-a-post-to-a-publication-on-medium/)\n\n[Browse Medium integration templates](https://n8n.io/integrations/medium/), or [search all templates](https://n8n.io/workflows/)\n\n## What to do if your operation isn't supported\n\nIf this node doesn't support the operation you want to do, you can use the [HTTP Request node](../../core-nodes/n8n-nodes-base.httprequest/) to call the service's API.\n\nYou can use the credential you created for this service in the HTTP Request node:\n\n1. In the HTTP Request node, select **Authentication** > **Predefined Credential Type**.\n1. Select the service you want to connect to.\n1. Select your credential.\n\nRefer to [Custom API operations](../../../custom-operations/) for more information.\n",
-        "excerpt": "# Medium node  Use the Medium node to automate work in Medium, and integrate Medium with other applications. n8n has built-in support for a wide range of Medium features, including creating posts, and getting publications.  On this page, you'll find a list of operations the Medium node supports and links to more resources.  Medium API no longer supported  Medium has stopped supporting the Medium API. The Medium node still appears within n8n, but you won't be able to configure new API keys to aut...",
-        "sections": [
-          {
-            "title": "Medium node",
-            "level": 1,
-            "content": "Use the Medium node to automate work in Medium, and integrate Medium with other applications. n8n has built-in support for a wide range of Medium features, including creating posts, and getting publications.\n\nOn this page, you'll find a list of operations the Medium node supports and links to more resources.\n\nMedium API no longer supported\n\nMedium has stopped supporting the Medium API. The Medium node still appears within n8n, but you won't be able to configure new API keys to authenticate with.\n\nRefer to [Medium credentials](../../credentials/medium/) for guidance on setting up existing API keys.\n\nThis node can be used as an AI tool\n\nThis node can be used to enhance the capabilities of an AI agent. When used in this way, many parameters can be set automatically, or with information directed by AI - find out more in the [AI tool parameters documentation](../../../../advanced-ai/examples/using-the-fromai-function/)."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "medium",
-          "node",
-          "operations",
-          "templates",
-          "examples",
-          "what",
-          "your",
-          "operation",
-          "isn't",
-          "supported"
-        ],
-        "useCases": [],
-        "operations": [
-          "",
-          "what to do if your  isn't supported"
-        ],
-        "codeExamples": 0,
-        "complexity": "intermediate",
-        "readingTime": "2 min",
-        "contentLength": 2171,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "medium # medium node\n\nuse the medium node to automate work in medium, and integrate medium with other applications. n8n has built-in support for a wide range of medium features, including creating posts, and getting publications.\n\non this page, you'll find a list of operations the medium node supports and links to more resources.\n\nmedium api no longer supported\n\nmedium has stopped supporting the medium api. the medium node still appears within n8n, but you won't be able to configure new api keys to authenticate with.\n\nrefer to [medium credentials](../../credentials/medium/) for guidance on setting up existing api keys.\n\nthis node can be used as an ai tool\n\nthis node can be used to enhance the capabilities of an ai agent. when used in this way, many parameters can be set automatically, or with information directed by ai - find out more in the [ai tool parameters documentation](../../../../advanced-ai/examples/using-the-fromai-function/).\n\n## operations\n\n- post\n  - create a post\n- publication\n  - get all publications\n\n## templates and examples\n\n**cross-post your blog posts**\n\nby amudhan\n\n[view template details](https://n8n.io/workflows/418-cross-post-your-blog-posts/)\n\n**posting from wordpress to medium**\n\nby zacharia kimotho\n\n[view template details](https://n8n.io/workflows/2062-posting-from-wordpress-to-medium/)\n\n**publish a post to a publication on medium**\n\nby harshil agrawal\n\n[view template details](https://n8n.io/workflows/594-publish-a-post-to-a-publication-on-medium/)\n\n[browse medium integration templates](https://n8n.io/integrations/medium/), or [search all templates](https://n8n.io/workflows/)\n\n## what to do if your operation isn't supported\n\nif this node doesn't support the operation you want to do, you can use the [http request node](../../core-nodes/n8n-nodes-base.httprequest/) to call the service's api.\n\nyou can use the credential you created for this service in the http request node:\n\n1. in the http request node, select **authentication** > **predefined credential type**.\n1. select the service you want to connect to.\n1. select your credential.\n\nrefer to [custom api operations](../../../custom-operations/) for more information.\n medium node",
-        "importantTerms": [
-          "medium",
-          "node",
-          "this",
-          "post",
-          "https",
-          "operations",
-          "your",
-          "workflows",
-          "with",
-          "posts",
-          "more",
-          "used",
-          "publication",
-          "templates",
-          "view",
-          "template",
-          "details",
-          "http",
-          "request",
-          "service",
-          "credential",
-          "select"
-        ]
-      }
-    },
     {
       "id": "page-0373",
       "title": "Microsoft Dynamics CRM",
@@ -75817,83 +75817,6 @@
     },
     {
       "id": "page-1008",
-      "title": "Wise credentials",
-      "url": "https://docs.n8n.io/integrations/builtin/credentials/wise/index.md",
-      "urlPath": "integrations/builtin/credentials/wise/index.md",
-      "category": "other",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Wise credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Wise](../../app-nodes/n8n-nodes-base.wise/)\n- [Wise Trigger](../../trigger-nodes/n8n-nodes-base.wisetrigger/)\n\n## Prerequisites\n\nCreate a [Wise](https://wise.com/) account.\n\n## Supported authentication methods\n\n- API token\n\n## Related resources\n\nRefer to [Wise's API documentation](https://docs.wise.com/api-docs/api-reference) for more information about the service.\n\n## Using API token\n\nTo configure this credential, you'll need:\n\n- An **API Token**: Go to your **user menu > Settings > API tokens** to generate an API token. Enter the generated API key in your n8n credential. Refer to [Getting started with the API](https://wise.com/help/articles/2958107/getting-started-with-the-api) for more information.\n- Your **Environment**: Select the environment that best matches your Wise account environment.\n  - If you're using a Wise test sandbox account, select **Test**.\n  - Otherwise, select **Live**.\n- **Private Key (Optional)**: For live endpoints requiring Strong Customer Authentication (SCA), generate a public and private key. Enter the private key here. Refer to [Add a private key](#add-a-private-key) for more information.\n  - If you're using a **Test** environment, you'll only need to enter a Private Key if you've enabled Strong Customer Authentication on the [public keys management page](https://sandbox.transferwise.tech/public-keys).\n\n## Add a private key\n\nWise protects some live endpoints and operations with Strong Customer Authentication (SCA). Refer to [Strong Customer Authentication & 2FA](https://docs.wise.com/api-docs/features/strong-customer-authentication-2fa) for details.\n\nIf you make a request to an endpoint that requires SCA, Wise returns a 403 Forbidden HTTP status code. The error returned will look like this:\n\n> This request requires Strong Customer Authentication (SCA). Please add a key pair to your account and n8n credentials. See https://api-docs.transferwise.com/#strong-customer-authentication-personal-token\n\nTo use endpoints requiring SCA, generate an RSA key pair and add the relevant key information to both Wise and n8n:\n\n1. Generate an RSA key pair:\n\n   ```\n   $ openssl genrsa -out private.pem 2048 \n   $ openssl rsa -pubout -in private.pem -out public.pem\n   ```\n\n1. Add the content of the public key `public.pem` to your Wise **user menu > Settings > API tokens > Manage public keys**.\n\n1. Add the content of the private key `private.pem` in n8n to the **Private Key (Optional)**.\n\nRefer to [Personal Token SCA](https://docs.wise.com/api-docs/guides/strong-customer-authentication-2fa/personal-token-sca) for more information.\n",
-        "excerpt": "# Wise credentials  You can use these credentials to authenticate the following nodes:  - [Wise](../../app-nodes/n8n-nodes-base.wise/) - [Wise Trigger](../../trigger-nodes/n8n-nodes-base.wisetrigger/)  ## Prerequisites  Create a [Wise](https://wise.com/) account.  ## Supported authentication methods  - API token  ## Related resources  Refer to [Wise's API documentation](https://docs.wise.com/api-docs/api-reference) for more information about the service.  ## Using API token  To configure this cr...",
-        "sections": [
-          {
-            "title": "Wise credentials",
-            "level": 1,
-            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Wise](../../app-nodes/n8n-nodes-base.wise/)\n- [Wise Trigger](../../trigger-nodes/n8n-nodes-base.wisetrigger/)"
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "wise",
-          "credentials",
-          "prerequisites",
-          "supported",
-          "authentication",
-          "methods",
-          "related",
-          "resources",
-          "using",
-          "token",
-          "private"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 1,
-        "complexity": "beginner",
-        "readingTime": "2 min",
-        "contentLength": 2675,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "wise credentials # wise credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [wise](../../app-nodes/n8n-nodes-base.wise/)\n- [wise trigger](../../trigger-nodes/n8n-nodes-base.wisetrigger/)\n\n## prerequisites\n\ncreate a [wise](https://wise.com/) account.\n\n## supported authentication methods\n\n- api token\n\n## related resources\n\nrefer to [wise's api documentation](https://docs.wise.com/api-docs/api-reference) for more information about the service.\n\n## using api token\n\nto configure this credential, you'll need:\n\n- an **api token**: go to your **user menu > settings > api tokens** to generate an api token. enter the generated api key in your n8n credential. refer to [getting started with the api](https://wise.com/help/articles/2958107/getting-started-with-the-api) for more information.\n- your **environment**: select the environment that best matches your wise account environment.\n  - if you're using a wise test sandbox account, select **test**.\n  - otherwise, select **live**.\n- **private key (optional)**: for live endpoints requiring strong customer authentication (sca), generate a public and private key. enter the private key here. refer to [add a private key](#add-a-private-key) for more information.\n  - if you're using a **test** environment, you'll only need to enter a private key if you've enabled strong customer authentication on the [public keys management page](https://sandbox.transferwise.tech/public-keys).\n\n## add a private key\n\nwise protects some live endpoints and operations with strong customer authentication (sca). refer to [strong customer authentication & 2fa](https://docs.wise.com/api-docs/features/strong-customer-authentication-2fa) for details.\n\nif you make a request to an endpoint that requires sca, wise returns a 403 forbidden http status code. the error returned will look like this:\n\n> this request requires strong customer authentication (sca). please add a key pair to your account and n8n credentials. see https://api-docs.transferwise.com/#strong-customer-authentication-personal-token\n\nto use endpoints requiring sca, generate an rsa key pair and add the relevant key information to both wise and n8n:\n\n1. generate an rsa key pair:\n\n   ```\n   $ openssl genrsa -out private.pem 2048 \n   $ openssl rsa -pubout -in private.pem -out public.pem\n   ```\n\n1. add the content of the public key `public.pem` to your wise **user menu > settings > api tokens > manage public keys**.\n\n1. add the content of the private key `private.pem` in n8n to the **private key (optional)**.\n\nrefer to [personal token sca](https://docs.wise.com/api-docs/guides/strong-customer-authentication-2fa/personal-token-sca) for more information.\n wise credentials",
-        "importantTerms": [
-          "wise",
-          "private",
-          "authentication",
-          "strong",
-          "customer",
-          "https",
-          "token",
-          "docs",
-          "public",
-          "your",
-          "credentials",
-          "nodes",
-          "refer",
-          "information",
-          "account",
-          "more",
-          "generate",
-          "environment",
-          "using",
-          "this",
-          "enter",
-          "with",
-          "select",
-          "test",
-          "live",
-          "endpoints",
-          "keys",
-          "pair",
-          "personal"
-        ]
-      }
-    },
-    {
-      "id": "page-1009",
       "title": "Wolfram|Alpha credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/wolframalpha/index.md",
       "urlPath": "integrations/builtin/credentials/wolframalpha/index.md",
@@ -75957,7 +75880,7 @@
       }
     },
     {
-      "id": "page-1010",
+      "id": "page-1009",
       "title": "WooCommerce credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/woocommerce/index.md",
       "urlPath": "integrations/builtin/credentials/woocommerce/index.md",
@@ -76021,7 +75944,7 @@
       }
     },
     {
-      "id": "page-1011",
+      "id": "page-1010",
       "title": "WordPress credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/wordpress/index.md",
       "urlPath": "integrations/builtin/credentials/wordpress/index.md",
@@ -76095,6 +76018,83 @@
         ]
       }
     },
+    {
+      "id": "page-1011",
+      "title": "Wise credentials",
+      "url": "https://docs.n8n.io/integrations/builtin/credentials/wise/index.md",
+      "urlPath": "integrations/builtin/credentials/wise/index.md",
+      "category": "other",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Wise credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Wise](../../app-nodes/n8n-nodes-base.wise/)\n- [Wise Trigger](../../trigger-nodes/n8n-nodes-base.wisetrigger/)\n\n## Prerequisites\n\nCreate a [Wise](https://wise.com/) account.\n\n## Supported authentication methods\n\n- API token\n\n## Related resources\n\nRefer to [Wise's API documentation](https://docs.wise.com/api-docs/api-reference) for more information about the service.\n\n## Using API token\n\nTo configure this credential, you'll need:\n\n- An **API Token**: Go to your **user menu > Settings > API tokens** to generate an API token. Enter the generated API key in your n8n credential. Refer to [Getting started with the API](https://wise.com/help/articles/2958107/getting-started-with-the-api) for more information.\n- Your **Environment**: Select the environment that best matches your Wise account environment.\n  - If you're using a Wise test sandbox account, select **Test**.\n  - Otherwise, select **Live**.\n- **Private Key (Optional)**: For live endpoints requiring Strong Customer Authentication (SCA), generate a public and private key. Enter the private key here. Refer to [Add a private key](#add-a-private-key) for more information.\n  - If you're using a **Test** environment, you'll only need to enter a Private Key if you've enabled Strong Customer Authentication on the [public keys management page](https://sandbox.transferwise.tech/public-keys).\n\n## Add a private key\n\nWise protects some live endpoints and operations with Strong Customer Authentication (SCA). Refer to [Strong Customer Authentication & 2FA](https://docs.wise.com/api-docs/features/strong-customer-authentication-2fa) for details.\n\nIf you make a request to an endpoint that requires SCA, Wise returns a 403 Forbidden HTTP status code. The error returned will look like this:\n\n> This request requires Strong Customer Authentication (SCA). Please add a key pair to your account and n8n credentials. See https://api-docs.transferwise.com/#strong-customer-authentication-personal-token\n\nTo use endpoints requiring SCA, generate an RSA key pair and add the relevant key information to both Wise and n8n:\n\n1. Generate an RSA key pair:\n\n   ```\n   $ openssl genrsa -out private.pem 2048 \n   $ openssl rsa -pubout -in private.pem -out public.pem\n   ```\n\n1. Add the content of the public key `public.pem` to your Wise **user menu > Settings > API tokens > Manage public keys**.\n\n1. Add the content of the private key `private.pem` in n8n to the **Private Key (Optional)**.\n\nRefer to [Personal Token SCA](https://docs.wise.com/api-docs/guides/strong-customer-authentication-2fa/personal-token-sca) for more information.\n",
+        "excerpt": "# Wise credentials  You can use these credentials to authenticate the following nodes:  - [Wise](../../app-nodes/n8n-nodes-base.wise/) - [Wise Trigger](../../trigger-nodes/n8n-nodes-base.wisetrigger/)  ## Prerequisites  Create a [Wise](https://wise.com/) account.  ## Supported authentication methods  - API token  ## Related resources  Refer to [Wise's API documentation](https://docs.wise.com/api-docs/api-reference) for more information about the service.  ## Using API token  To configure this cr...",
+        "sections": [
+          {
+            "title": "Wise credentials",
+            "level": 1,
+            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Wise](../../app-nodes/n8n-nodes-base.wise/)\n- [Wise Trigger](../../trigger-nodes/n8n-nodes-base.wisetrigger/)"
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "wise",
+          "credentials",
+          "prerequisites",
+          "supported",
+          "authentication",
+          "methods",
+          "related",
+          "resources",
+          "using",
+          "token",
+          "private"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 1,
+        "complexity": "beginner",
+        "readingTime": "2 min",
+        "contentLength": 2675,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "wise credentials # wise credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [wise](../../app-nodes/n8n-nodes-base.wise/)\n- [wise trigger](../../trigger-nodes/n8n-nodes-base.wisetrigger/)\n\n## prerequisites\n\ncreate a [wise](https://wise.com/) account.\n\n## supported authentication methods\n\n- api token\n\n## related resources\n\nrefer to [wise's api documentation](https://docs.wise.com/api-docs/api-reference) for more information about the service.\n\n## using api token\n\nto configure this credential, you'll need:\n\n- an **api token**: go to your **user menu > settings > api tokens** to generate an api token. enter the generated api key in your n8n credential. refer to [getting started with the api](https://wise.com/help/articles/2958107/getting-started-with-the-api) for more information.\n- your **environment**: select the environment that best matches your wise account environment.\n  - if you're using a wise test sandbox account, select **test**.\n  - otherwise, select **live**.\n- **private key (optional)**: for live endpoints requiring strong customer authentication (sca), generate a public and private key. enter the private key here. refer to [add a private key](#add-a-private-key) for more information.\n  - if you're using a **test** environment, you'll only need to enter a private key if you've enabled strong customer authentication on the [public keys management page](https://sandbox.transferwise.tech/public-keys).\n\n## add a private key\n\nwise protects some live endpoints and operations with strong customer authentication (sca). refer to [strong customer authentication & 2fa](https://docs.wise.com/api-docs/features/strong-customer-authentication-2fa) for details.\n\nif you make a request to an endpoint that requires sca, wise returns a 403 forbidden http status code. the error returned will look like this:\n\n> this request requires strong customer authentication (sca). please add a key pair to your account and n8n credentials. see https://api-docs.transferwise.com/#strong-customer-authentication-personal-token\n\nto use endpoints requiring sca, generate an rsa key pair and add the relevant key information to both wise and n8n:\n\n1. generate an rsa key pair:\n\n   ```\n   $ openssl genrsa -out private.pem 2048 \n   $ openssl rsa -pubout -in private.pem -out public.pem\n   ```\n\n1. add the content of the public key `public.pem` to your wise **user menu > settings > api tokens > manage public keys**.\n\n1. add the content of the private key `private.pem` in n8n to the **private key (optional)**.\n\nrefer to [personal token sca](https://docs.wise.com/api-docs/guides/strong-customer-authentication-2fa/personal-token-sca) for more information.\n wise credentials",
+        "importantTerms": [
+          "wise",
+          "private",
+          "authentication",
+          "strong",
+          "customer",
+          "https",
+          "token",
+          "docs",
+          "public",
+          "your",
+          "credentials",
+          "nodes",
+          "refer",
+          "information",
+          "account",
+          "more",
+          "generate",
+          "environment",
+          "using",
+          "this",
+          "enter",
+          "with",
+          "select",
+          "test",
+          "live",
+          "endpoints",
+          "keys",
+          "pair",
+          "personal"
+        ]
+      }
+    },
     {
       "id": "page-1012",
       "title": "Workable credentials",
@@ -92476,9 +92476,9 @@
       ],
       "features": [
         "page-0002",
+        "page-0027",
         "page-0028",
         "page-0029",
-        "page-0030",
         "page-0031",
         "page-0039",
         "page-0051",
@@ -92525,7 +92525,7 @@
         "page-0086",
         "page-0097",
         "page-0101",
-        "page-0104",
+        "page-0105",
         "page-0108",
         "page-0130",
         "page-0148",
@@ -92582,8 +92582,8 @@
         "page-0097",
         "page-0099",
         "page-0101",
-        "page-0104",
         "page-0105",
+        "page-0106",
         "page-0108",
         "page-0111",
         "page-0143",
@@ -93289,7 +93289,7 @@
         "page-0002",
         "page-0003",
         "page-0013",
-        "page-0027",
+        "page-0026",
         "page-1204"
       ],
       "changes": [
@@ -93373,8 +93373,8 @@
         "page-0019",
         "page-0022",
         "page-0024",
-        "page-0025",
-        "page-0027",
+        "page-0026",
+        "page-0030",
         "page-0061",
         "page-0072",
         "page-0074",
@@ -93562,7 +93562,7 @@
         "page-0097",
         "page-0098",
         "page-0101",
-        "page-0105",
+        "page-0106",
         "page-0130",
         "page-0143",
         "page-0144",
@@ -93648,9 +93648,9 @@
         "page-0018",
         "page-0019",
         "page-0023",
-        "page-0027",
+        "page-0026",
+        "page-0028",
         "page-0029",
-        "page-0030",
         "page-0050",
         "page-0059",
         "page-0060",
@@ -93674,7 +93674,7 @@
         "page-0101",
         "page-0102",
         "page-0103",
-        "page-0106",
+        "page-0104",
         "page-0107",
         "page-0130",
         "page-0135",
@@ -93836,7 +93836,7 @@
         "page-0002",
         "page-0003",
         "page-0012",
-        "page-0027",
+        "page-0026",
         "page-0100",
         "page-0233",
         "page-0348",
@@ -93965,7 +93965,7 @@
         "page-0007",
         "page-0018",
         "page-0021",
-        "page-0027",
+        "page-0026",
         "page-0130",
         "page-0208",
         "page-0332",
@@ -94355,7 +94355,7 @@
         "page-0869",
         "page-0870",
         "page-0955",
-        "page-1011",
+        "page-1010",
         "page-1027",
         "page-1028",
         "page-1029",
@@ -94395,8 +94395,8 @@
       "based": [
         "page-0003",
         "page-0013",
+        "page-0024",
         "page-0025",
-        "page-0026",
         "page-0694",
         "page-1167",
         "page-1230"
@@ -94407,7 +94407,7 @@
         "page-0012",
         "page-0013",
         "page-0021",
-        "page-0027",
+        "page-0026",
         "page-0036",
         "page-0038",
         "page-0531",
@@ -95085,7 +95085,7 @@
         "page-0015",
         "page-0018",
         "page-0023",
-        "page-0024",
+        "page-0030",
         "page-0042",
         "page-0046",
         "page-0049",
@@ -95189,7 +95189,7 @@
         "page-0364",
         "page-0368",
         "page-0369",
-        "page-0371",
+        "page-0370",
         "page-0372",
         "page-0373",
         "page-0374",
@@ -95840,9 +95840,9 @@
         "page-0020",
         "page-0021",
         "page-0023",
+        "page-0027",
         "page-0028",
         "page-0029",
-        "page-0030",
         "page-0031",
         "page-0039",
         "page-0046",
@@ -96194,8 +96194,8 @@
         "page-0015",
         "page-0019",
         "page-0022",
-        "page-0027",
-        "page-0030",
+        "page-0026",
+        "page-0029",
         "page-0042",
         "page-0050",
         "page-0064",
@@ -96324,8 +96324,8 @@
       ],
       "resolve": [
         "page-0005",
-        "page-1009",
-        "page-1010"
+        "page-1008",
+        "page-1009"
       ],
       "production": [
         "page-0005",
@@ -96470,7 +96470,7 @@
         "page-0778",
         "page-0816",
         "page-0831",
-        "page-1011",
+        "page-1010",
         "page-1027",
         "page-1028",
         "page-1029",
@@ -96509,7 +96509,7 @@
         "page-0024",
         "page-0025",
         "page-0026",
-        "page-0027",
+        "page-0030",
         "page-0654",
         "page-0655",
         "page-1205"
@@ -96602,7 +96602,7 @@
         "page-0017",
         "page-0018",
         "page-0022",
-        "page-0024",
+        "page-0030",
         "page-0041",
         "page-0072",
         "page-0083",
@@ -96855,8 +96855,8 @@
       ],
       "metrics": [
         "page-0007",
-        "page-0025",
-        "page-0027",
+        "page-0024",
+        "page-0026",
         "page-0168",
         "page-0210",
         "page-0654",
@@ -96961,7 +96961,7 @@
         "page-0008",
         "page-0013",
         "page-0019",
-        "page-0026",
+        "page-0025",
         "page-0526",
         "page-0680",
         "page-1140",
@@ -97294,9 +97294,9 @@
       "accessing": [
         "page-0012",
         "page-0018",
-        "page-0027",
+        "page-0026",
         "page-0059",
-        "page-0104",
+        "page-0105",
         "page-1196",
         "page-1214"
       ],
@@ -97547,7 +97547,7 @@
       ],
       "pull": [
         "page-0013",
-        "page-0024",
+        "page-0030",
         "page-0196",
         "page-0202",
         "page-0207",
@@ -97738,7 +97738,7 @@
       ],
       "multiple": [
         "page-0013",
-        "page-0027",
+        "page-0026",
         "page-0131",
         "page-0144",
         "page-0645",
@@ -97864,7 +97864,7 @@
         "page-0023",
         "page-0024",
         "page-0025",
-        "page-0026",
+        "page-0030",
         "page-0033",
         "page-0034",
         "page-0035",
@@ -97959,7 +97959,7 @@
         "page-0364",
         "page-0368",
         "page-0369",
-        "page-0371",
+        "page-0370",
         "page-0372",
         "page-0373",
         "page-0374",
@@ -98043,8 +98043,8 @@
         "page-0017",
         "page-0020",
         "page-0022",
-        "page-0027",
-        "page-0030",
+        "page-0026",
+        "page-0029",
         "page-0318",
         "page-0429",
         "page-0525",
@@ -98156,7 +98156,7 @@
       ],
       "source": [
         "page-0015",
-        "page-0030",
+        "page-0029",
         "page-0189",
         "page-0566",
         "page-0615",
@@ -98265,7 +98265,7 @@
         "page-0364",
         "page-0368",
         "page-0369",
-        "page-0371",
+        "page-0370",
         "page-0372",
         "page-0373",
         "page-0374",
@@ -98371,7 +98371,7 @@
       ],
       "back": [
         "page-0015",
-        "page-0024",
+        "page-0030",
         "page-0213",
         "page-1205"
       ],
@@ -98391,9 +98391,9 @@
       ],
       "example": [
         "page-0015",
+        "page-0027",
         "page-0028",
         "page-0029",
-        "page-0030",
         "page-0031",
         "page-0037",
         "page-0039",
@@ -98461,7 +98461,7 @@
       "create": [
         "page-0015",
         "page-0022",
-        "page-0024",
+        "page-0030",
         "page-0046",
         "page-0050",
         "page-0052",
@@ -98506,7 +98506,7 @@
         "page-0800",
         "page-0943",
         "page-0968",
-        "page-1011",
+        "page-1010",
         "page-1027",
         "page-1028",
         "page-1029",
@@ -98561,7 +98561,7 @@
         "page-0015",
         "page-0024",
         "page-0025",
-        "page-0026",
+        "page-0030",
         "page-1167"
       ],
       "switch": [
@@ -98576,7 +98576,7 @@
         "page-0066",
         "page-0096",
         "page-0097",
-        "page-0105",
+        "page-0106",
         "page-0110",
         "page-0711",
         "page-0712",
@@ -98610,13 +98610,13 @@
       ],
       "differences": [
         "page-0015",
-        "page-0028",
+        "page-0027",
         "page-1182"
       ],
       "between": [
         "page-0015",
         "page-0018",
-        "page-0028",
+        "page-0027",
         "page-0132",
         "page-0146",
         "page-0649",
@@ -99752,7 +99752,7 @@
       ],
       "types": [
         "page-0017",
-        "page-0026",
+        "page-0025",
         "page-0087",
         "page-0231",
         "page-0232",
@@ -100425,7 +100425,7 @@
         "page-0999",
         "page-1000",
         "page-1004",
-        "page-1008",
+        "page-1011",
         "page-1019",
         "page-1020",
         "page-1023",
@@ -100470,7 +100470,7 @@
       ],
       "input": [
         "page-0018",
-        "page-0105",
+        "page-0106",
         "page-0659",
         "page-0697",
         "page-0711",
@@ -100517,7 +100517,7 @@
         "page-0018",
         "page-0045",
         "page-0050",
-        "page-0107",
+        "page-0103",
         "page-0112",
         "page-0208",
         "page-0240",
@@ -100997,7 +100997,7 @@
       ],
       "google": [
         "page-0018",
-        "page-0030",
+        "page-0029",
         "page-0166",
         "page-0204",
         "page-0205",
@@ -101097,7 +101097,7 @@
       ],
       "overview": [
         "page-0020",
-        "page-0026",
+        "page-0025",
         "page-0043",
         "page-0057",
         "page-0095",
@@ -101133,7 +101133,7 @@
       "agents": [
         "page-0020",
         "page-0023",
-        "page-0028",
+        "page-0027",
         "page-0033",
         "page-0041",
         "page-0640"
@@ -101191,7 +101191,7 @@
       "works": [
         "page-0021",
         "page-0024",
-        "page-0025",
+        "page-0030",
         "page-0095",
         "page-0157",
         "page-0218",
@@ -101209,7 +101209,7 @@
         "page-0158",
         "page-0651",
         "page-0674",
-        "page-1011",
+        "page-1010",
         "page-1031",
         "page-1035",
         "page-1156",
@@ -101329,7 +101329,7 @@
       ],
       "learn": [
         "page-0022",
-        "page-0026",
+        "page-0025",
         "page-0044",
         "page-0070",
         "page-0085"
@@ -101476,61 +101476,23 @@
       "case?": [
         "page-0023"
       ],
+      "metric": [
+        "page-0024",
+        "page-0025"
+      ],
       "evaluations": [
         "page-0024",
-        "page-0025",
-        "page-0027",
+        "page-0026",
+        "page-0030",
         "page-1205"
       ],
       "evaluations?": [
         "page-0024",
         "page-0025",
-        "page-0026"
-      ],
-      "dataset": [
-        "page-0024",
-        "page-0050"
-      ],
-      "wire": [
-        "page-0024"
-      ],
-      "insert": [
-        "page-0024",
-        "page-0079",
-        "page-0518",
-        "page-0519",
-        "page-0548",
-        "page-0549",
-        "page-0550",
-        "page-0551",
-        "page-0552",
-        "page-0553",
-        "page-0554",
-        "page-0555",
-        "page-0556",
-        "page-0557",
-        "page-0558",
-        "page-0559",
-        "page-0705"
-      ],
-      "write": [
-        "page-0024",
-        "page-0678",
-        "page-1161"
-      ],
-      "outputs": [
-        "page-0024",
-        "page-0059",
-        "page-0544",
-        "page-0654",
-        "page-1205"
-      ],
-      "metric": [
-        "page-0025",
-        "page-0026"
+        "page-0030"
       ],
       "view": [
-        "page-0025",
+        "page-0024",
         "page-0208",
         "page-0218",
         "page-1204",
@@ -101541,8 +101503,8 @@
         "page-1262"
       ],
       "results": [
-        "page-0025",
-        "page-0027",
+        "page-0024",
+        "page-0026",
         "page-0233",
         "page-0548",
         "page-0549",
@@ -101558,31 +101520,31 @@
         "page-0559"
       ],
       "needed?": [
-        "page-0026"
+        "page-0025"
       ],
       "(pre": [
-        "page-0026"
+        "page-0025"
       ],
       "deployment)": [
-        "page-0026"
+        "page-0025"
       ],
       "(post": [
-        "page-0026"
+        "page-0025"
       ],
       "comparison": [
-        "page-0026",
+        "page-0025",
         "page-0212",
         "page-0645",
         "page-1195"
       ],
       "tips": [
-        "page-0027",
+        "page-0026",
         "page-1189"
       ],
       "common": [
-        "page-0027",
+        "page-0026",
         "page-0100",
-        "page-0105",
+        "page-0106",
         "page-0131",
         "page-0132",
         "page-0374",
@@ -101681,26 +101643,26 @@
         "page-1238"
       ],
       "combining": [
-        "page-0027",
+        "page-0026",
         "page-0660",
         "page-0667"
       ],
       "triggers": [
-        "page-0027",
+        "page-0026",
         "page-0232",
         "page-1038",
         "page-1254"
       ],
       "avoiding": [
-        "page-0027",
+        "page-0026",
         "page-0215"
       ],
       "calculating": [
-        "page-0027",
+        "page-0026",
         "page-0081"
       ],
       "same": [
-        "page-0027",
+        "page-0026",
         "page-0059",
         "page-0515",
         "page-0632",
@@ -101708,22 +101670,22 @@
         "page-1205"
       ],
       "dealing": [
-        "page-0027",
+        "page-0026",
         "page-0089"
       ],
       "inconsistent": [
-        "page-0027"
+        "page-0026"
       ],
       "chains": [
-        "page-0028",
+        "page-0027",
         "page-0034",
         "page-0041"
       ],
       "demonstration": [
-        "page-0028"
+        "page-0027"
       ],
       "call": [
-        "page-0029",
+        "page-0028",
         "page-0046",
         "page-0136",
         "page-0146",
@@ -101733,7 +101695,7 @@
         "page-0694"
       ],
       "fetch": [
-        "page-0029",
+        "page-0028",
         "page-0333",
         "page-0348",
         "page-0548",
@@ -101753,7 +101715,7 @@
         "page-1216"
       ],
       "sheets": [
-        "page-0030",
+        "page-0029",
         "page-0510",
         "page-0511",
         "page-0512",
@@ -101763,9 +101725,47 @@
         "page-1204"
       ],
       "sheet": [
-        "page-0030",
+        "page-0029",
         "page-0513"
       ],
+      "dataset": [
+        "page-0030",
+        "page-0050"
+      ],
+      "wire": [
+        "page-0030"
+      ],
+      "insert": [
+        "page-0030",
+        "page-0079",
+        "page-0518",
+        "page-0519",
+        "page-0548",
+        "page-0549",
+        "page-0550",
+        "page-0551",
+        "page-0552",
+        "page-0553",
+        "page-0554",
+        "page-0555",
+        "page-0556",
+        "page-0557",
+        "page-0558",
+        "page-0559",
+        "page-0705"
+      ],
+      "write": [
+        "page-0030",
+        "page-0678",
+        "page-1161"
+      ],
+      "outputs": [
+        "page-0030",
+        "page-0059",
+        "page-0544",
+        "page-0654",
+        "page-1205"
+      ],
       "fallback": [
         "page-0031"
       ],
@@ -102087,7 +102087,7 @@
         "page-0059",
         "page-0064",
         "page-0097",
-        "page-0105",
+        "page-0106",
         "page-0209",
         "page-0542",
         "page-0562",
@@ -102233,7 +102233,7 @@
       "other": [
         "page-0049",
         "page-0101",
-        "page-0105",
+        "page-0106",
         "page-0203",
         "page-1170",
         "page-1204",
@@ -102459,7 +102459,7 @@
         "page-0364",
         "page-0368",
         "page-0369",
-        "page-0371",
+        "page-0370",
         "page-0372",
         "page-0373",
         "page-0374",
@@ -102839,7 +102839,7 @@
         "page-0055",
         "page-0057",
         "page-0058",
-        "page-0105",
+        "page-0106",
         "page-0155",
         "page-0544",
         "page-0701",
@@ -103273,8 +103273,8 @@
         "page-0059",
         "page-0066",
         "page-0096",
-        "page-0104",
-        "page-0106",
+        "page-0105",
+        "page-0107",
         "page-0109",
         "page-0110",
         "page-0143",
@@ -103297,7 +103297,7 @@
       "current": [
         "page-0059",
         "page-0060",
-        "page-0105",
+        "page-0106",
         "page-0132",
         "page-0168",
         "page-0203",
@@ -103857,8 +103857,8 @@
       "referencing": [
         "page-0086",
         "page-0103",
-        "page-0105",
-        "page-0107"
+        "page-0104",
+        "page-0106"
       ],
       "transforming": [
         "page-0086",
@@ -104207,7 +104207,7 @@
         "page-1004",
         "page-1005",
         "page-1006",
-        "page-1008",
+        "page-1009",
         "page-1010",
         "page-1011",
         "page-1012",
@@ -104483,14 +104483,14 @@
         "page-1205"
       ],
       "linked": [
-        "page-0104"
+        "page-0105"
       ],
       "ways": [
-        "page-0105",
+        "page-0106",
         "page-1205"
       ],
       "linking": [
-        "page-0106",
+        "page-0107",
         "page-0108",
         "page-0109",
         "page-0110",
@@ -105464,8 +105464,8 @@
         "page-0653",
         "page-0690",
         "page-0955",
+        "page-1008",
         "page-1009",
-        "page-1010",
         "page-1137",
         "page-1140",
         "page-1163",
@@ -105734,7 +105734,7 @@
         "page-1000",
         "page-1005",
         "page-1006",
-        "page-1011",
+        "page-1010",
         "page-1019",
         "page-1024"
       ],
@@ -107009,7 +107009,7 @@
         "page-0960",
         "page-0961",
         "page-0965",
-        "page-1011",
+        "page-1010",
         "page-1031",
         "page-1035"
       ],
@@ -107492,7 +107492,7 @@
         "page-0943",
         "page-0980",
         "page-1003",
-        "page-1009",
+        "page-1008",
         "page-1253"
       ],
       "servers": [
@@ -108013,7 +108013,7 @@
         "page-0364",
         "page-0368",
         "page-0369",
-        "page-0371",
+        "page-0370",
         "page-0372",
         "page-0373",
         "page-0374",
@@ -108697,19 +108697,19 @@
         "page-0870",
         "page-1087"
       ],
-      "messagebird": [
+      "medium": [
         "page-0370",
+        "page-0871"
+      ],
+      "messagebird": [
+        "page-0371",
         "page-0872"
       ],
       "metabase": [
-        "page-0371",
+        "page-0372",
         "page-0873",
         "page-1204"
       ],
-      "medium": [
-        "page-0372",
-        "page-0871"
-      ],
       "dynamics": [
         "page-0373",
         "page-0874"
@@ -109199,17 +109199,17 @@
       ],
       "wise": [
         "page-0477",
-        "page-1008",
+        "page-1011",
         "page-1119"
       ],
       "woocommerce": [
         "page-0478",
-        "page-1010",
+        "page-1009",
         "page-1120"
       ],
       "wordpress": [
         "page-0479",
-        "page-1011"
+        "page-1010"
       ],
       "xero": [
         "page-0480",
@@ -109268,7 +109268,7 @@
         "page-0496",
         "page-0710",
         "page-0955",
-        "page-1009"
+        "page-1008"
       ],
       "perhaps": [
         "page-0492",
@@ -109740,7 +109740,7 @@
         "page-0985",
         "page-1005",
         "page-1006",
-        "page-1011",
+        "page-1010",
         "page-1019",
         "page-1024"
       ],
@@ -110386,7 +110386,7 @@
       ],
       "wolfram|alpha": [
         "page-0629",
-        "page-1009"
+        "page-1008"
       ],
       "remote": [
         "page-0632",
@@ -111083,7 +111083,7 @@
         "page-0740",
         "page-0874",
         "page-0877",
-        "page-1011",
+        "page-1010",
         "page-1126"
       ],
       "bitbucket": [
@@ -111147,7 +111147,7 @@
         "page-0797",
         "page-0845",
         "page-0965",
-        "page-1008",
+        "page-1011",
         "page-1179"
       ],
       "meta": [
@@ -111412,10 +111412,10 @@
         "page-1003"
       ],
       "\"consumer": [
-        "page-1010"
+        "page-1009"
       ],
       "missing\"": [
-        "page-1010"
+        "page-1009"
       ],
       "workable": [
         "page-1012",
@@ -114175,13 +114175,13 @@
       "mautic": [
         "page-0369"
       ],
-      "messagebird": [
+      "medium": [
         "page-0370"
       ],
-      "metabase": [
+      "messagebird": [
         "page-0371"
       ],
-      "medium": [
+      "metabase": [
         "page-0372"
       ],
       "microsoftdynamicscrm": [