@n8n-as-code/skills 1.1.3-next.12 → 1.1.3-next.13

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

@@ -1,15 +1,15 @@
 {
-  "generatedAt": "2026-03-17T10:51:10.634Z",
+  "generatedAt": "2026-03-17T11:31:22.125Z",
   "version": "1.0.0",
   "sourceUrl": "https://docs.n8n.io/llms.txt",
-  "totalPages": 1253,
+  "totalPages": 1254,
   "statistics": {
     "byCategory": {
       "other": 515,
       "tutorials": 27,
       "advanced-ai": 27,
       "api": 5,
-      "code": 19,
+      "code": 20,
       "data": 38,
       "flow-logic": 8,
       "hosting": 78,
@@ -624,7 +624,7 @@
     },
     "code": {
       "description": "Code node, expressions, and built-in methods",
-      "totalPages": 19,
+      "totalPages": 20,
       "pages": [
         "page-0049",
         "page-0050",
@@ -635,6 +635,7 @@
         "page-0055",
         "page-0056",
         "page-0057",
+        "page-0058",
         "page-0059",
         "page-0060",
         "page-0061",
@@ -6193,6 +6194,57 @@
     },
     {
       "id": "page-0057",
+      "title": "Overview",
+      "url": "https://docs.n8n.io/code/builtin/overview/index.md",
+      "urlPath": "code/builtin/overview/index.md",
+      "category": "code",
+      "subcategory": "builtin",
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Built-in methods and variables\n\nn8n provides built-in methods and variables for working with data and accessing n8n data. This section provides a reference of available methods and variables for use in [expressions](../../../glossary/#expression-n8n), with a short description.\n\nAvailability in the expressions editor and the Code node\n\nSome methods and variables aren't available in the Code node. These aren't in the documentation.\n\nAll data transformation functions are only available in the expressions editor.\n\nThe [Cookbook](../../) contains examples for some common tasks, including some [Code node only](../../cookbook/code-node/) functions.\n\n- [JMESPath](/code/builtin/jmespath/)\n- [HTTP node](/code/builtin/http-node-variables/)\n- [LangChain Code node](/code/builtin/langchain-methods/)\n- [n8n metadata](/code/builtin/n8n-metadata/)\n",
+        "excerpt": "# Built-in methods and variables  n8n provides built-in methods and variables for working with data and accessing n8n data. This section provides a reference of available methods and variables for use in [expressions](../../../glossary/#expression-n8n), with a short description.  Availability in the expressions editor and the Code node  Some methods and variables aren't available in the Code node. These aren't in the documentation.  All data transformation functions are only available in the exp...",
+        "sections": [
+          {
+            "title": "Built-in methods and variables",
+            "level": 1,
+            "content": "n8n provides built-in methods and variables for working with data and accessing n8n data. This section provides a reference of available methods and variables for use in [expressions](../../../glossary/#expression-n8n), with a short description.\n\nAvailability in the expressions editor and the Code node\n\nSome methods and variables aren't available in the Code node. These aren't in the documentation.\n\nAll data transformation functions are only available in the expressions editor.\n\nThe [Cookbook](../../) contains examples for some common tasks, including some [Code node only](../../cookbook/code-node/) functions.\n\n- [JMESPath](/code/builtin/jmespath/)\n- [HTTP node](/code/builtin/http-node-variables/)\n- [LangChain Code node](/code/builtin/langchain-methods/)\n- [n8n metadata](/code/builtin/n8n-metadata/)"
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "overview",
+          "built",
+          "methods",
+          "variables"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "1 min",
+        "contentLength": 845,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "overview # built-in methods and variables\n\nn8n provides built-in methods and variables for working with data and accessing n8n data. this section provides a reference of available methods and variables for use in [expressions](../../../glossary/#expression-n8n), with a short description.\n\navailability in the expressions editor and the code node\n\nsome methods and variables aren't available in the code node. these aren't in the documentation.\n\nall data transformation functions are only available in the expressions editor.\n\nthe [cookbook](../../) contains examples for some common tasks, including some [code node only](../../cookbook/code-node/) functions.\n\n- [jmespath](/code/builtin/jmespath/)\n- [http node](/code/builtin/http-node-variables/)\n- [langchain code node](/code/builtin/langchain-methods/)\n- [n8n metadata](/code/builtin/n8n-metadata/)\n built-in methods and variables",
+        "importantTerms": [
+          "code",
+          "node",
+          "methods",
+          "variables",
+          "builtin",
+          "built",
+          "data",
+          "available",
+          "expressions",
+          "some"
+        ]
+      }
+    },
+    {
+      "id": "page-0058",
       "title": "Examples using n8n's built-in methods and variables",
       "url": "https://docs.n8n.io/code/cookbook/builtin/index.md",
       "urlPath": "code/cookbook/builtin/index.md",
@@ -6201,7 +6253,7 @@
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Examples using n8n's built-in methods and variables\n\nn8n provides built-in methods and variables for working with data and accessing n8n data. This section provides usage examples.\n\n- [execution](/code/cookbook/builtin/execution/)\n- [getWorkflowStaticData](/code/cookbook/builtin/get-workflow-static-data/)\n- [(node-name).all](/code/cookbook/builtin/all/)\n- [vars](/code/cookbook/builtin/vars/)\n\n## Related resources\n\n- [Built-in methods and variables reference](../../builtin/overview/)\n- [Expressions](../../../data/expressions/)\n- [Code node](../../code-node/)\ne common tasks, including some [Code node only](../../cookbook/code-node/) functions.\n\n- [JMESPath](/code/builtin/jmespath/)\n- [HTTP node](/code/builtin/http-node-variables/)\n- [LangChain Code node](/code/builtin/langchain-methods/)\n- [n8n metadata](/code/builtin/n8n-metadata/)\n",
+        "markdown": "# Examples using n8n's built-in methods and variables\n\nn8n provides built-in methods and variables for working with data and accessing n8n data. This section provides usage examples.\n\n- [execution](/code/cookbook/builtin/execution/)\n- [getWorkflowStaticData](/code/cookbook/builtin/get-workflow-static-data/)\n- [(node-name).all](/code/cookbook/builtin/all/)\n- [vars](/code/cookbook/builtin/vars/)\n\n## Related resources\n\n- [Built-in methods and variables reference](../../builtin/overview/)\n- [Expressions](../../../data/expressions/)\n- [Code node](../../code-node/)\n",
         "excerpt": "# Examples using n8n's built-in methods and variables  n8n provides built-in methods and variables for working with data and accessing n8n data. This section provides usage examples.  - [execution](/code/cookbook/builtin/execution/) - [getWorkflowStaticData](/code/cookbook/builtin/get-workflow-static-data/) - [(node-name).all](/code/cookbook/builtin/all/) - [vars](/code/cookbook/builtin/vars/)  ## Related resources  - [Built-in methods and variables reference](../../builtin/overview/) - [Express...",
         "sections": [
           {
@@ -6227,22 +6279,22 @@
         "codeExamples": 0,
         "complexity": "beginner",
         "readingTime": "1 min",
-        "contentLength": 845,
+        "contentLength": 566,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "examples using n8n's built-in methods and variables # examples using n8n's built-in methods and variables\n\nn8n provides built-in methods and variables for working with data and accessing n8n data. this section provides usage examples.\n\n- [execution](/code/cookbook/builtin/execution/)\n- [getworkflowstaticdata](/code/cookbook/builtin/get-workflow-static-data/)\n- [(node-name).all](/code/cookbook/builtin/all/)\n- [vars](/code/cookbook/builtin/vars/)\n\n## related resources\n\n- [built-in methods and variables reference](../../builtin/overview/)\n- [expressions](../../../data/expressions/)\n- [code node](../../code-node/)\ne common tasks, including some [code node only](../../cookbook/code-node/) functions.\n\n- [jmespath](/code/builtin/jmespath/)\n- [http node](/code/builtin/http-node-variables/)\n- [langchain code node](/code/builtin/langchain-methods/)\n- [n8n metadata](/code/builtin/n8n-metadata/)\n examples using n8n's built-in methods and variables",
+        "fullText": "examples using n8n's built-in methods and variables # examples using n8n's built-in methods and variables\n\nn8n provides built-in methods and variables for working with data and accessing n8n data. this section provides usage examples.\n\n- [execution](/code/cookbook/builtin/execution/)\n- [getworkflowstaticdata](/code/cookbook/builtin/get-workflow-static-data/)\n- [(node-name).all](/code/cookbook/builtin/all/)\n- [vars](/code/cookbook/builtin/vars/)\n\n## related resources\n\n- [built-in methods and variables reference](../../builtin/overview/)\n- [expressions](../../../data/expressions/)\n- [code node](../../code-node/)\n examples using n8n's built-in methods and variables",
         "importantTerms": [
           "code",
-          "builtin",
-          "node",
+          "built",
           "methods",
           "variables",
-          "built",
-          "cookbook",
+          "builtin",
           "examples",
           "data",
-          "using"
+          "cookbook",
+          "using",
+          "node"
         ]
       }
     },
@@ -9367,109 +9419,6 @@
     },
     {
       "id": "page-0100",
-      "title": "Expressions for data transformation",
-      "url": "https://docs.n8n.io/data/expressions-for-transformation/index.md",
-      "urlPath": "data/expressions-for-transformation/index.md",
-      "category": "data",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Expressions for data transformation\n\nYou can use expression transformation functions anywhere expressions are supported in n8n.\n\nHowever, if your main goal is to transform data using expressions without performing any other operations, use the **Edit Fields (Set)** node. This node is designed specifically for data transformation, providing a clean interface to:\n\n- Add new fields with expression-based values\n- Modify existing field values using transformation functions\n- Remove or rename fields\n\nThis keeps your workflow organized by separating data transformation from business logic, making it easier to understand and maintain.\n\n**Best practice**: Instead of adding complex expressions to multiple parameters across different nodes, use Edit Fields to prepare your data first, then pass the transformed data to subsequent nodes.\n\nSee [Expression reference](../expression-reference/) for more information and examples.\n\n### Example: Get data from webhook body\n\nConsider the following scenario: you have a webhook trigger that receives data through the webhook body. You want to extract some of that data for use in the workflow.\n\nYour webhook data looks similar to this:\n\n```\n[\n  {\n    \"headers\": {\n      \"host\": \"n8n.instance.address\",\n      ...\n    },\n    \"params\": {},\n    \"query\": {},\n    \"body\": {\n      \"name\": \"Jim\",\n      \"age\": 30,\n      \"city\": \"New York\"\n    }\n  }\n]\n```\n\nIn the next node in the workflow, you want to get just the value of `city`. You can use the following expression:\n\n```\n{{$json.body.city}}\n```\n\nThis expression:\n\n1. Accesses the incoming JSON-formatted data using n8n's custom `$json` variable.\n1. Finds the value of `city` (in this example, \"New York\"). Note that this example uses JMESPath syntax to query the JSON data. You can also write this expression as `{{$json['body']['city']}}`.\n\n### Using expressions in credentials\n\nYou can also use expressions in credential fields. When you reference data using expressions (for example, `{{$json.body.city}}` or `{{ $('Webhook').item.json.headers.authorization }}`), n8n evaluates the expression within the context of the current workflow execution.\n\nThis means that:\n\n- Expressions in credentials can access data available in the current execution context, including data from previous nodes.\n- Each workflow execution has its own data context.\n- Expressions are evaluated per execution, so different executions don't share data.\n\nFor example, if a webhook node receives an access token and you reference it in a credential field using an expression, the value is resolved using the execution data of that specific workflow run.\n\n## Example: Writing longer JavaScript as expressions\n\nYou can do things like variable assignments or multiple statements in an expression, but you need to wrap your code using the syntax for an Immediately Invoked Function Expression (IIFE).\n\nThe following code use the Luxon date and time library to find the time between two dates in months. We surround the code in both the handlebar brackets for an expression and the IIFE syntax.\n\n```\n{{(()=>{\n  let end = DateTime.fromISO('2017-03-13');\n  let start = DateTime.fromISO('2017-02-13');\n  let diffInMonths = end.diff(start, 'months');\n  return diffInMonths.toObject();\n})()}}\n```\n\n## Common issues\n\nHere are some common errors and issues related to [expressions](../expressions/) and steps to resolve or troubleshoot them.\n\n### The 'JSON Output' in item 0 contains invalid JSON\n\nThis error occurs when you use JSON mode but don't provide a valid JSON object. Depending on the problem with the JSON object, the error sometimes displays as `The 'JSON Output' in item 0 does not contain a valid JSON object`.\n\nTo resolve this, make sure that the code you provide is valid JSON:\n\n- Check the JSON with a [JSON validator](https://jsonlint.com/).\n- Check that your JSON object doesn't reference undefined input data. This may occur if the incoming data doesn't always include the same fields.\n\n### Can't get data for expression\n\nThis error occurs when n8n can't retrieve the data referenced by an expression. Often, this happens when the preceding node hasn't been run yet.\n\nAnother variation of this may appear as `Referenced node is unexecuted`. In that case, the full text of this error will tell you the exact node that isn't executing in this format:\n\n> An expression references the node '<node-name>', but it hasn't been executed yet. Either change the expression, or re-wire your workflow to make sure that node executes first.\n\nTo begin troubleshooting, test the workflow up to the named node.\n\nFor nodes that use JavaScript or other custom code, you can check if a previous node has executed before trying to use its value by checking the following:\n\n```\n$(\"<node-name>\").isExecuted\n```\n\nAs an example, this JSON references the parameters of the input data. This error will display if you test this step without connecting it to another node:\n\n```\n{\n  \"my_field_1\": {{ $input.params }}\n}\n```\n\n### Invalid syntax\n\nThis error occurs when you use an expression that has a syntax error.\n\nFor example, the expression in this JSON includes a trailing period, which results in an invalid syntax error:\n\n```\n{\n  \"my_field_1\": \"value\",\n  \"my_field_2\": {{ $('If').item.json. }}\n}\n```\n\nTo resolve this error, check your [expression syntax](../expressions/) to make sure it follows the expected format.\n",
-        "excerpt": "# Expressions for data transformation  You can use expression transformation functions anywhere expressions are supported in n8n.  However, if your main goal is to transform data using expressions without performing any other operations, use the **Edit Fields (Set)** node. This node is designed specifically for data transformation, providing a clean interface to:  - Add new fields with expression-based values - Modify existing field values using transformation functions - Remove or rename fields...",
-        "sections": [
-          {
-            "title": "Expressions for data transformation",
-            "level": 1,
-            "content": "You can use expression transformation functions anywhere expressions are supported in n8n.\n\nHowever, if your main goal is to transform data using expressions without performing any other operations, use the **Edit Fields (Set)** node. This node is designed specifically for data transformation, providing a clean interface to:\n\n- Add new fields with expression-based values\n- Modify existing field values using transformation functions\n- Remove or rename fields\n\nThis keeps your workflow organized by separating data transformation from business logic, making it easier to understand and maintain.\n\n**Best practice**: Instead of adding complex expressions to multiple parameters across different nodes, use Edit Fields to prepare your data first, then pass the transformed data to subsequent nodes.\n\nSee [Expression reference](../expression-reference/) for more information and examples."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "expressions",
-          "data",
-          "transformation",
-          "example:",
-          "from",
-          "webhook",
-          "body",
-          "using",
-          "credentials",
-          "writing",
-          "longer",
-          "javascript",
-          "common",
-          "issues",
-          "'json",
-          "output'",
-          "item",
-          "contains",
-          "invalid",
-          "json",
-          "can't",
-          "expression",
-          "syntax"
-        ],
-        "useCases": [
-          "Get data from webhook body",
-          "you have a webhook trigger that receives data through the webhook body. You want to extract some of that data for use in the workflow.",
-          "Writing longer JavaScript as expressions"
-        ],
-        "operations": [],
-        "codeExamples": 6,
-        "complexity": "intermediate",
-        "readingTime": "5 min",
-        "contentLength": 5366,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "expressions for data transformation # expressions for data transformation\n\nyou can use expression transformation functions anywhere expressions are supported in n8n.\n\nhowever, if your main goal is to transform data using expressions without performing any other operations, use the **edit fields (set)** node. this node is designed specifically for data transformation, providing a clean interface to:\n\n- add new fields with expression-based values\n- modify existing field values using transformation functions\n- remove or rename fields\n\nthis keeps your workflow organized by separating data transformation from business logic, making it easier to understand and maintain.\n\n**best practice**: instead of adding complex expressions to multiple parameters across different nodes, use edit fields to prepare your data first, then pass the transformed data to subsequent nodes.\n\nsee [expression reference](../expression-reference/) for more information and examples.\n\n### example: get data from webhook body\n\nconsider the following scenario: you have a webhook trigger that receives data through the webhook body. you want to extract some of that data for use in the workflow.\n\nyour webhook data looks similar to this:\n\n```\n[\n  {\n    \"headers\": {\n      \"host\": \"n8n.instance.address\",\n      ...\n    },\n    \"params\": {},\n    \"query\": {},\n    \"body\": {\n      \"name\": \"jim\",\n      \"age\": 30,\n      \"city\": \"new york\"\n    }\n  }\n]\n```\n\nin the next node in the workflow, you want to get just the value of `city`. you can use the following expression:\n\n```\n{{$json.body.city}}\n```\n\nthis expression:\n\n1. accesses the incoming json-formatted data using n8n's custom `$json` variable.\n1. finds the value of `city` (in this example, \"new york\"). note that this example uses jmespath syntax to query the json data. you can also write this expression as `{{$json['body']['city']}}`.\n\n### using expressions in credentials\n\nyou can also use expressions in credential fields. when you reference data using expressions (for example, `{{$json.body.city}}` or `{{ $('webhook').item.json.headers.authorization }}`), n8n evaluates the expression within the context of the current workflow execution.\n\nthis means that:\n\n- expressions in credentials can access data available in the current execution context, including data from previous nodes.\n- each workflow execution has its own data context.\n- expressions are evaluated per execution, so different executions don't share data.\n\nfor example, if a webhook node receives an access token and you reference it in a credential field using an expression, the value is resolved using the execution data of that specific workflow run.\n\n## example: writing longer javascript as expressions\n\nyou can do things like variable assignments or multiple statements in an expression, but you need to wrap your code using the syntax for an immediately invoked function expression (iife).\n\nthe following code use the luxon date and time library to find the time between two dates in months. we surround the code in both the handlebar brackets for an expression and the iife syntax.\n\n```\n{{(()=>{\n  let end = datetime.fromiso('2017-03-13');\n  let start = datetime.fromiso('2017-02-13');\n  let diffinmonths = end.diff(start, 'months');\n  return diffinmonths.toobject();\n})()}}\n```\n\n## common issues\n\nhere are some common errors and issues related to [expressions](../expressions/) and steps to resolve or troubleshoot them.\n\n### the 'json output' in item 0 contains invalid json\n\nthis error occurs when you use json mode but don't provide a valid json object. depending on the problem with the json object, the error sometimes displays as `the 'json output' in item 0 does not contain a valid json object`.\n\nto resolve this, make sure that the code you provide is valid json:\n\n- check the json with a [json validator](https://jsonlint.com/).\n- check that your json object doesn't reference undefined input data. this may occur if the incoming data doesn't always include the same fields.\n\n### can't get data for expression\n\nthis error occurs when n8n can't retrieve the data referenced by an expression. often, this happens when the preceding node hasn't been run yet.\n\nanother variation of this may appear as `referenced node is unexecuted`. in that case, the full text of this error will tell you the exact node that isn't executing in this format:\n\n> an expression references the node '<node-name>', but it hasn't been executed yet. either change the expression, or re-wire your workflow to make sure that node executes first.\n\nto begin troubleshooting, test the workflow up to the named node.\n\nfor nodes that use javascript or other custom code, you can check if a previous node has executed before trying to use its value by checking the following:\n\n```\n$(\"<node-name>\").isexecuted\n```\n\nas an example, this json references the parameters of the input data. this error will display if you test this step without connecting it to another node:\n\n```\n{\n  \"my_field_1\": {{ $input.params }}\n}\n```\n\n### invalid syntax\n\nthis error occurs when you use an expression that has a syntax error.\n\nfor example, the expression in this json includes a trailing period, which results in an invalid syntax error:\n\n```\n{\n  \"my_field_1\": \"value\",\n  \"my_field_2\": {{ $('if').item.json. }}\n}\n```\n\nto resolve this error, check your [expression syntax](../expressions/) to make sure it follows the expected format.\n expressions for data transformation",
-        "importantTerms": [
-          "data",
-          "this",
-          "json",
-          "expression",
-          "expressions",
-          "node",
-          "that",
-          "error",
-          "your",
-          "using",
-          "workflow",
-          "example",
-          "transformation",
-          "syntax",
-          "fields",
-          "webhook",
-          "body",
-          "city",
-          "reference",
-          "value",
-          "when",
-          "execution",
-          "code",
-          "nodes",
-          "following",
-          "item",
-          "object",
-          "check",
-          "with",
-          "from",
-          "name",
-          "context",
-          "resolve",
-          "invalid",
-          "occurs",
-          "valid",
-          "make",
-          "sure",
-          "input"
-        ]
-      }
-    },
-    {
-      "id": "page-0101",
       "title": "Expressions versus data nodes",
       "url": "https://docs.n8n.io/data/expressions/index.md",
       "urlPath": "data/expressions/index.md",
@@ -9549,7 +9498,7 @@
       }
     },
     {
-      "id": "page-0102",
+      "id": "page-0101",
       "title": "Approaches for transforming data",
       "url": "https://docs.n8n.io/data/transforming-data/index.md",
       "urlPath": "data/transforming-data/index.md",
@@ -9605,6 +9554,109 @@
         ]
       }
     },
+    {
+      "id": "page-0102",
+      "title": "Expressions for data transformation",
+      "url": "https://docs.n8n.io/data/expressions-for-transformation/index.md",
+      "urlPath": "data/expressions-for-transformation/index.md",
+      "category": "data",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Expressions for data transformation\n\nYou can use expression transformation functions anywhere expressions are supported in n8n.\n\nHowever, if your main goal is to transform data using expressions without performing any other operations, use the **Edit Fields (Set)** node. This node is designed specifically for data transformation, providing a clean interface to:\n\n- Add new fields with expression-based values\n- Modify existing field values using transformation functions\n- Remove or rename fields\n\nThis keeps your workflow organized by separating data transformation from business logic, making it easier to understand and maintain.\n\n**Best practice**: Instead of adding complex expressions to multiple parameters across different nodes, use Edit Fields to prepare your data first, then pass the transformed data to subsequent nodes.\n\nSee [Expression reference](../expression-reference/) for more information and examples.\n\n### Example: Get data from webhook body\n\nConsider the following scenario: you have a webhook trigger that receives data through the webhook body. You want to extract some of that data for use in the workflow.\n\nYour webhook data looks similar to this:\n\n```\n[\n  {\n    \"headers\": {\n      \"host\": \"n8n.instance.address\",\n      ...\n    },\n    \"params\": {},\n    \"query\": {},\n    \"body\": {\n      \"name\": \"Jim\",\n      \"age\": 30,\n      \"city\": \"New York\"\n    }\n  }\n]\n```\n\nIn the next node in the workflow, you want to get just the value of `city`. You can use the following expression:\n\n```\n{{$json.body.city}}\n```\n\nThis expression:\n\n1. Accesses the incoming JSON-formatted data using n8n's custom `$json` variable.\n1. Finds the value of `city` (in this example, \"New York\"). Note that this example uses JMESPath syntax to query the JSON data. You can also write this expression as `{{$json['body']['city']}}`.\n\n### Using expressions in credentials\n\nYou can also use expressions in credential fields. When you reference data using expressions (for example, `{{$json.body.city}}` or `{{ $('Webhook').item.json.headers.authorization }}`), n8n evaluates the expression within the context of the current workflow execution.\n\nThis means that:\n\n- Expressions in credentials can access data available in the current execution context, including data from previous nodes.\n- Each workflow execution has its own data context.\n- Expressions are evaluated per execution, so different executions don't share data.\n\nFor example, if a webhook node receives an access token and you reference it in a credential field using an expression, the value is resolved using the execution data of that specific workflow run.\n\n## Example: Writing longer JavaScript as expressions\n\nYou can do things like variable assignments or multiple statements in an expression, but you need to wrap your code using the syntax for an Immediately Invoked Function Expression (IIFE).\n\nThe following code use the Luxon date and time library to find the time between two dates in months. We surround the code in both the handlebar brackets for an expression and the IIFE syntax.\n\n```\n{{(()=>{\n  let end = DateTime.fromISO('2017-03-13');\n  let start = DateTime.fromISO('2017-02-13');\n  let diffInMonths = end.diff(start, 'months');\n  return diffInMonths.toObject();\n})()}}\n```\n\n## Common issues\n\nHere are some common errors and issues related to [expressions](../expressions/) and steps to resolve or troubleshoot them.\n\n### The 'JSON Output' in item 0 contains invalid JSON\n\nThis error occurs when you use JSON mode but don't provide a valid JSON object. Depending on the problem with the JSON object, the error sometimes displays as `The 'JSON Output' in item 0 does not contain a valid JSON object`.\n\nTo resolve this, make sure that the code you provide is valid JSON:\n\n- Check the JSON with a [JSON validator](https://jsonlint.com/).\n- Check that your JSON object doesn't reference undefined input data. This may occur if the incoming data doesn't always include the same fields.\n\n### Can't get data for expression\n\nThis error occurs when n8n can't retrieve the data referenced by an expression. Often, this happens when the preceding node hasn't been run yet.\n\nAnother variation of this may appear as `Referenced node is unexecuted`. In that case, the full text of this error will tell you the exact node that isn't executing in this format:\n\n> An expression references the node '<node-name>', but it hasn't been executed yet. Either change the expression, or re-wire your workflow to make sure that node executes first.\n\nTo begin troubleshooting, test the workflow up to the named node.\n\nFor nodes that use JavaScript or other custom code, you can check if a previous node has executed before trying to use its value by checking the following:\n\n```\n$(\"<node-name>\").isExecuted\n```\n\nAs an example, this JSON references the parameters of the input data. This error will display if you test this step without connecting it to another node:\n\n```\n{\n  \"my_field_1\": {{ $input.params }}\n}\n```\n\n### Invalid syntax\n\nThis error occurs when you use an expression that has a syntax error.\n\nFor example, the expression in this JSON includes a trailing period, which results in an invalid syntax error:\n\n```\n{\n  \"my_field_1\": \"value\",\n  \"my_field_2\": {{ $('If').item.json. }}\n}\n```\n\nTo resolve this error, check your [expression syntax](../expressions/) to make sure it follows the expected format.\n",
+        "excerpt": "# Expressions for data transformation  You can use expression transformation functions anywhere expressions are supported in n8n.  However, if your main goal is to transform data using expressions without performing any other operations, use the **Edit Fields (Set)** node. This node is designed specifically for data transformation, providing a clean interface to:  - Add new fields with expression-based values - Modify existing field values using transformation functions - Remove or rename fields...",
+        "sections": [
+          {
+            "title": "Expressions for data transformation",
+            "level": 1,
+            "content": "You can use expression transformation functions anywhere expressions are supported in n8n.\n\nHowever, if your main goal is to transform data using expressions without performing any other operations, use the **Edit Fields (Set)** node. This node is designed specifically for data transformation, providing a clean interface to:\n\n- Add new fields with expression-based values\n- Modify existing field values using transformation functions\n- Remove or rename fields\n\nThis keeps your workflow organized by separating data transformation from business logic, making it easier to understand and maintain.\n\n**Best practice**: Instead of adding complex expressions to multiple parameters across different nodes, use Edit Fields to prepare your data first, then pass the transformed data to subsequent nodes.\n\nSee [Expression reference](../expression-reference/) for more information and examples."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "expressions",
+          "data",
+          "transformation",
+          "example:",
+          "from",
+          "webhook",
+          "body",
+          "using",
+          "credentials",
+          "writing",
+          "longer",
+          "javascript",
+          "common",
+          "issues",
+          "'json",
+          "output'",
+          "item",
+          "contains",
+          "invalid",
+          "json",
+          "can't",
+          "expression",
+          "syntax"
+        ],
+        "useCases": [
+          "Get data from webhook body",
+          "you have a webhook trigger that receives data through the webhook body. You want to extract some of that data for use in the workflow.",
+          "Writing longer JavaScript as expressions"
+        ],
+        "operations": [],
+        "codeExamples": 6,
+        "complexity": "intermediate",
+        "readingTime": "5 min",
+        "contentLength": 5366,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "expressions for data transformation # expressions for data transformation\n\nyou can use expression transformation functions anywhere expressions are supported in n8n.\n\nhowever, if your main goal is to transform data using expressions without performing any other operations, use the **edit fields (set)** node. this node is designed specifically for data transformation, providing a clean interface to:\n\n- add new fields with expression-based values\n- modify existing field values using transformation functions\n- remove or rename fields\n\nthis keeps your workflow organized by separating data transformation from business logic, making it easier to understand and maintain.\n\n**best practice**: instead of adding complex expressions to multiple parameters across different nodes, use edit fields to prepare your data first, then pass the transformed data to subsequent nodes.\n\nsee [expression reference](../expression-reference/) for more information and examples.\n\n### example: get data from webhook body\n\nconsider the following scenario: you have a webhook trigger that receives data through the webhook body. you want to extract some of that data for use in the workflow.\n\nyour webhook data looks similar to this:\n\n```\n[\n  {\n    \"headers\": {\n      \"host\": \"n8n.instance.address\",\n      ...\n    },\n    \"params\": {},\n    \"query\": {},\n    \"body\": {\n      \"name\": \"jim\",\n      \"age\": 30,\n      \"city\": \"new york\"\n    }\n  }\n]\n```\n\nin the next node in the workflow, you want to get just the value of `city`. you can use the following expression:\n\n```\n{{$json.body.city}}\n```\n\nthis expression:\n\n1. accesses the incoming json-formatted data using n8n's custom `$json` variable.\n1. finds the value of `city` (in this example, \"new york\"). note that this example uses jmespath syntax to query the json data. you can also write this expression as `{{$json['body']['city']}}`.\n\n### using expressions in credentials\n\nyou can also use expressions in credential fields. when you reference data using expressions (for example, `{{$json.body.city}}` or `{{ $('webhook').item.json.headers.authorization }}`), n8n evaluates the expression within the context of the current workflow execution.\n\nthis means that:\n\n- expressions in credentials can access data available in the current execution context, including data from previous nodes.\n- each workflow execution has its own data context.\n- expressions are evaluated per execution, so different executions don't share data.\n\nfor example, if a webhook node receives an access token and you reference it in a credential field using an expression, the value is resolved using the execution data of that specific workflow run.\n\n## example: writing longer javascript as expressions\n\nyou can do things like variable assignments or multiple statements in an expression, but you need to wrap your code using the syntax for an immediately invoked function expression (iife).\n\nthe following code use the luxon date and time library to find the time between two dates in months. we surround the code in both the handlebar brackets for an expression and the iife syntax.\n\n```\n{{(()=>{\n  let end = datetime.fromiso('2017-03-13');\n  let start = datetime.fromiso('2017-02-13');\n  let diffinmonths = end.diff(start, 'months');\n  return diffinmonths.toobject();\n})()}}\n```\n\n## common issues\n\nhere are some common errors and issues related to [expressions](../expressions/) and steps to resolve or troubleshoot them.\n\n### the 'json output' in item 0 contains invalid json\n\nthis error occurs when you use json mode but don't provide a valid json object. depending on the problem with the json object, the error sometimes displays as `the 'json output' in item 0 does not contain a valid json object`.\n\nto resolve this, make sure that the code you provide is valid json:\n\n- check the json with a [json validator](https://jsonlint.com/).\n- check that your json object doesn't reference undefined input data. this may occur if the incoming data doesn't always include the same fields.\n\n### can't get data for expression\n\nthis error occurs when n8n can't retrieve the data referenced by an expression. often, this happens when the preceding node hasn't been run yet.\n\nanother variation of this may appear as `referenced node is unexecuted`. in that case, the full text of this error will tell you the exact node that isn't executing in this format:\n\n> an expression references the node '<node-name>', but it hasn't been executed yet. either change the expression, or re-wire your workflow to make sure that node executes first.\n\nto begin troubleshooting, test the workflow up to the named node.\n\nfor nodes that use javascript or other custom code, you can check if a previous node has executed before trying to use its value by checking the following:\n\n```\n$(\"<node-name>\").isexecuted\n```\n\nas an example, this json references the parameters of the input data. this error will display if you test this step without connecting it to another node:\n\n```\n{\n  \"my_field_1\": {{ $input.params }}\n}\n```\n\n### invalid syntax\n\nthis error occurs when you use an expression that has a syntax error.\n\nfor example, the expression in this json includes a trailing period, which results in an invalid syntax error:\n\n```\n{\n  \"my_field_1\": \"value\",\n  \"my_field_2\": {{ $('if').item.json. }}\n}\n```\n\nto resolve this error, check your [expression syntax](../expressions/) to make sure it follows the expected format.\n expressions for data transformation",
+        "importantTerms": [
+          "data",
+          "this",
+          "json",
+          "expression",
+          "expressions",
+          "node",
+          "that",
+          "error",
+          "your",
+          "using",
+          "workflow",
+          "example",
+          "transformation",
+          "syntax",
+          "fields",
+          "webhook",
+          "body",
+          "city",
+          "reference",
+          "value",
+          "when",
+          "execution",
+          "code",
+          "nodes",
+          "following",
+          "item",
+          "object",
+          "check",
+          "with",
+          "from",
+          "name",
+          "context",
+          "resolve",
+          "invalid",
+          "occurs",
+          "valid",
+          "make",
+          "sure",
+          "input"
+        ]
+      }
+    },
     {
       "id": "page-0103",
       "title": "Referencing data",
@@ -34868,27 +34920,28 @@
     },
     {
       "id": "page-0463",
-      "title": "UpLead",
-      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.uplead/index.md",
-      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.uplead/index.md",
+      "title": "Unleashed Software",
+      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.unleashedsoftware/index.md",
+      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.unleashedsoftware/index.md",
       "category": "integrations",
       "subcategory": "app-nodes",
-      "nodeName": "uplead",
-      "nodeType": "n8n-nodes-base.uplead",
+      "nodeName": "unleashedsoftware",
+      "nodeType": "n8n-nodes-base.unleashedsoftware",
       "content": {
-        "markdown": "# UpLead node\n\nUse the UpLead node to automate work in UpLead, and integrate UpLead with other applications. n8n supports several UpLead operations, including getting company information.\n\nOn this page, you'll find a list of operations the UpLead node supports and links to more resources.\n\nCredentials\n\nRefer to [UpLead credentials](../../credentials/uplead/) for guidance on setting up authentication.\n\n## Operations\n\n- Company\n  - Enrich\n- Person\n  - Enrich\n\n## Templates and examples\n\n[Browse UpLead integration templates](https://n8n.io/integrations/uplead/), or [search all templates](https://n8n.io/workflows/)\n",
-        "excerpt": "# UpLead node  Use the UpLead node to automate work in UpLead, and integrate UpLead with other applications. n8n supports several UpLead operations, including getting company information.  On this page, you'll find a list of operations the UpLead node supports and links to more resources.  Credentials  Refer to [UpLead credentials](../../credentials/uplead/) for guidance on setting up authentication.  ## Operations  - Company   - Enrich - Person   - Enrich  ## Templates and examples  [Browse UpL...",
+        "markdown": "# Unleashed Software node\n\nUse the Unleashed Software node to automate work in Unleashed Software, and integrate Unleashed Software with other applications. n8n has built-in support for a wide range of Unleashed Software features, including getting sales orders and stock on hand.\n\nOn this page, you'll find a list of operations the Unleashed Software node supports and links to more resources.\n\nCredentials\n\nRefer to [Unleashed Software credentials](../../credentials/unleashedsoftware/) for guidance on setting up authentication.\n\n## Operations\n\n- Sales Order\n  - Get all sales orders\n- Stock On Hand\n  - Get a stock on hand\n  - Get all stocks on hand\n\n## Templates and examples\n\n[Browse Unleashed Software integration templates](https://n8n.io/integrations/unleashed-software/), or [search all templates](https://n8n.io/workflows/)\n",
+        "excerpt": "# Unleashed Software node  Use the Unleashed Software node to automate work in Unleashed Software, and integrate Unleashed Software with other applications. n8n has built-in support for a wide range of Unleashed Software features, including getting sales orders and stock on hand.  On this page, you'll find a list of operations the Unleashed Software node supports and links to more resources.  Credentials  Refer to [Unleashed Software credentials](../../credentials/unleashedsoftware/) for guidanc...",
         "sections": [
           {
-            "title": "UpLead node",
+            "title": "Unleashed Software node",
             "level": 1,
-            "content": "Use the UpLead node to automate work in UpLead, and integrate UpLead with other applications. n8n supports several UpLead operations, including getting company information.\n\nOn this page, you'll find a list of operations the UpLead node supports and links to more resources.\n\nCredentials\n\nRefer to [UpLead credentials](../../credentials/uplead/) for guidance on setting up authentication."
+            "content": "Use the Unleashed Software node to automate work in Unleashed Software, and integrate Unleashed Software with other applications. n8n has built-in support for a wide range of Unleashed Software features, including getting sales orders and stock on hand.\n\nOn this page, you'll find a list of operations the Unleashed Software node supports and links to more resources.\n\nCredentials\n\nRefer to [Unleashed Software credentials](../../credentials/unleashedsoftware/) for guidance on setting up authentication."
           }
         ]
       },
       "metadata": {
         "keywords": [
-          "uplead",
+          "unleashed",
+          "software",
           "node",
           "operations",
           "templates",
@@ -34901,15 +34954,18 @@
         "codeExamples": 0,
         "complexity": "beginner",
         "readingTime": "1 min",
-        "contentLength": 618,
+        "contentLength": 835,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "uplead # uplead node\n\nuse the uplead node to automate work in uplead, and integrate uplead with other applications. n8n supports several uplead operations, including getting company information.\n\non this page, you'll find a list of operations the uplead node supports and links to more resources.\n\ncredentials\n\nrefer to [uplead credentials](../../credentials/uplead/) for guidance on setting up authentication.\n\n## operations\n\n- company\n  - enrich\n- person\n  - enrich\n\n## templates and examples\n\n[browse uplead integration templates](https://n8n.io/integrations/uplead/), or [search all templates](https://n8n.io/workflows/)\n uplead node",
+        "fullText": "unleashed software # unleashed software node\n\nuse the unleashed software node to automate work in unleashed software, and integrate unleashed software with other applications. n8n has built-in support for a wide range of unleashed software features, including getting sales orders and stock on hand.\n\non this page, you'll find a list of operations the unleashed software node supports and links to more resources.\n\ncredentials\n\nrefer to [unleashed software credentials](../../credentials/unleashedsoftware/) for guidance on setting up authentication.\n\n## operations\n\n- sales order\n  - get all sales orders\n- stock on hand\n  - get a stock on hand\n  - get all stocks on hand\n\n## templates and examples\n\n[browse unleashed software integration templates](https://n8n.io/integrations/unleashed-software/), or [search all templates](https://n8n.io/workflows/)\n unleashed software node",
         "importantTerms": [
-          "uplead",
+          "unleashed",
+          "software",
           "node",
-          "operations",
+          "hand",
+          "sales",
+          "stock",
           "credentials",
           "templates"
         ]
@@ -34917,28 +34973,27 @@
     },
     {
       "id": "page-0464",
-      "title": "Unleashed Software",
-      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.unleashedsoftware/index.md",
-      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.unleashedsoftware/index.md",
+      "title": "UpLead",
+      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.uplead/index.md",
+      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.uplead/index.md",
       "category": "integrations",
       "subcategory": "app-nodes",
-      "nodeName": "unleashedsoftware",
-      "nodeType": "n8n-nodes-base.unleashedsoftware",
+      "nodeName": "uplead",
+      "nodeType": "n8n-nodes-base.uplead",
       "content": {
-        "markdown": "# Unleashed Software node\n\nUse the Unleashed Software node to automate work in Unleashed Software, and integrate Unleashed Software with other applications. n8n has built-in support for a wide range of Unleashed Software features, including getting sales orders and stock on hand.\n\nOn this page, you'll find a list of operations the Unleashed Software node supports and links to more resources.\n\nCredentials\n\nRefer to [Unleashed Software credentials](../../credentials/unleashedsoftware/) for guidance on setting up authentication.\n\n## Operations\n\n- Sales Order\n  - Get all sales orders\n- Stock On Hand\n  - Get a stock on hand\n  - Get all stocks on hand\n\n## Templates and examples\n\n[Browse Unleashed Software integration templates](https://n8n.io/integrations/unleashed-software/), or [search all templates](https://n8n.io/workflows/)\n",
-        "excerpt": "# Unleashed Software node  Use the Unleashed Software node to automate work in Unleashed Software, and integrate Unleashed Software with other applications. n8n has built-in support for a wide range of Unleashed Software features, including getting sales orders and stock on hand.  On this page, you'll find a list of operations the Unleashed Software node supports and links to more resources.  Credentials  Refer to [Unleashed Software credentials](../../credentials/unleashedsoftware/) for guidanc...",
+        "markdown": "# UpLead node\n\nUse the UpLead node to automate work in UpLead, and integrate UpLead with other applications. n8n supports several UpLead operations, including getting company information.\n\nOn this page, you'll find a list of operations the UpLead node supports and links to more resources.\n\nCredentials\n\nRefer to [UpLead credentials](../../credentials/uplead/) for guidance on setting up authentication.\n\n## Operations\n\n- Company\n  - Enrich\n- Person\n  - Enrich\n\n## Templates and examples\n\n[Browse UpLead integration templates](https://n8n.io/integrations/uplead/), or [search all templates](https://n8n.io/workflows/)\n",
+        "excerpt": "# UpLead node  Use the UpLead node to automate work in UpLead, and integrate UpLead with other applications. n8n supports several UpLead operations, including getting company information.  On this page, you'll find a list of operations the UpLead node supports and links to more resources.  Credentials  Refer to [UpLead credentials](../../credentials/uplead/) for guidance on setting up authentication.  ## Operations  - Company   - Enrich - Person   - Enrich  ## Templates and examples  [Browse UpL...",
         "sections": [
           {
-            "title": "Unleashed Software node",
+            "title": "UpLead node",
             "level": 1,
-            "content": "Use the Unleashed Software node to automate work in Unleashed Software, and integrate Unleashed Software with other applications. n8n has built-in support for a wide range of Unleashed Software features, including getting sales orders and stock on hand.\n\nOn this page, you'll find a list of operations the Unleashed Software node supports and links to more resources.\n\nCredentials\n\nRefer to [Unleashed Software credentials](../../credentials/unleashedsoftware/) for guidance on setting up authentication."
+            "content": "Use the UpLead node to automate work in UpLead, and integrate UpLead with other applications. n8n supports several UpLead operations, including getting company information.\n\nOn this page, you'll find a list of operations the UpLead node supports and links to more resources.\n\nCredentials\n\nRefer to [UpLead credentials](../../credentials/uplead/) for guidance on setting up authentication."
           }
         ]
       },
       "metadata": {
         "keywords": [
-          "unleashed",
-          "software",
+          "uplead",
           "node",
           "operations",
           "templates",
@@ -34951,18 +35006,15 @@
         "codeExamples": 0,
         "complexity": "beginner",
         "readingTime": "1 min",
-        "contentLength": 835,
+        "contentLength": 618,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "unleashed software # unleashed software node\n\nuse the unleashed software node to automate work in unleashed software, and integrate unleashed software with other applications. n8n has built-in support for a wide range of unleashed software features, including getting sales orders and stock on hand.\n\non this page, you'll find a list of operations the unleashed software node supports and links to more resources.\n\ncredentials\n\nrefer to [unleashed software credentials](../../credentials/unleashedsoftware/) for guidance on setting up authentication.\n\n## operations\n\n- sales order\n  - get all sales orders\n- stock on hand\n  - get a stock on hand\n  - get all stocks on hand\n\n## templates and examples\n\n[browse unleashed software integration templates](https://n8n.io/integrations/unleashed-software/), or [search all templates](https://n8n.io/workflows/)\n unleashed software node",
+        "fullText": "uplead # uplead node\n\nuse the uplead node to automate work in uplead, and integrate uplead with other applications. n8n supports several uplead operations, including getting company information.\n\non this page, you'll find a list of operations the uplead node supports and links to more resources.\n\ncredentials\n\nrefer to [uplead credentials](../../credentials/uplead/) for guidance on setting up authentication.\n\n## operations\n\n- company\n  - enrich\n- person\n  - enrich\n\n## templates and examples\n\n[browse uplead integration templates](https://n8n.io/integrations/uplead/), or [search all templates](https://n8n.io/workflows/)\n uplead node",
         "importantTerms": [
-          "unleashed",
-          "software",
+          "uplead",
           "node",
-          "hand",
-          "sales",
-          "stock",
+          "operations",
           "credentials",
           "templates"
         ]
@@ -91201,7 +91253,7 @@
         "page-0081",
         "page-0086",
         "page-0097",
-        "page-0101",
+        "page-0100",
         "page-0105",
         "page-0108",
         "page-0130",
@@ -91258,7 +91310,7 @@
         "page-0086",
         "page-0097",
         "page-0099",
-        "page-0101",
+        "page-0100",
         "page-0105",
         "page-0106",
         "page-0108",
@@ -92108,7 +92160,7 @@
       "expression": [
         "page-0002",
         "page-0006",
-        "page-0100",
+        "page-0102",
         "page-0112",
         "page-0131",
         "page-0676",
@@ -92226,7 +92278,7 @@
         "page-0071",
         "page-0097",
         "page-0098",
-        "page-0101",
+        "page-0100",
         "page-0106",
         "page-0130",
         "page-0143",
@@ -92294,7 +92346,7 @@
         "page-0002",
         "page-0050",
         "page-0100",
-        "page-0101",
+        "page-0102",
         "page-0638",
         "page-1197"
       ],
@@ -92436,7 +92488,7 @@
       ],
       "webhook": [
         "page-0002",
-        "page-0100",
+        "page-0102",
         "page-0153",
         "page-0170",
         "page-0216",
@@ -92498,7 +92550,7 @@
         "page-0003",
         "page-0012",
         "page-0027",
-        "page-0100",
+        "page-0102",
         "page-0231",
         "page-0345",
         "page-0371",
@@ -92656,7 +92708,7 @@
         "page-0093",
         "page-0096",
         "page-0097",
-        "page-0100",
+        "page-0102",
         "page-0110",
         "page-0132",
         "page-0144",
@@ -94112,7 +94164,7 @@
         "page-0013",
         "page-0014",
         "page-0022",
-        "page-0100",
+        "page-0102",
         "page-0136",
         "page-0151",
         "page-0153",
@@ -94464,11 +94516,11 @@
         "page-0046",
         "page-0048",
         "page-0051",
-        "page-0057",
+        "page-0058",
         "page-0067",
         "page-0068",
         "page-0097",
-        "page-0100",
+        "page-0102",
         "page-0134",
         "page-0136",
         "page-0141",
@@ -95792,6 +95844,7 @@
         "page-0052",
         "page-0053",
         "page-0057",
+        "page-0058",
         "page-0099",
         "page-0134",
         "page-0153",
@@ -96730,7 +96783,7 @@
       ],
       "n8n's": [
         "page-0015",
-        "page-0057",
+        "page-0058",
         "page-0067",
         "page-0109",
         "page-0160",
@@ -97048,7 +97101,7 @@
         "page-0017",
         "page-0021",
         "page-0050",
-        "page-0057",
+        "page-0058",
         "page-0063",
         "page-0067",
         "page-0140",
@@ -97578,7 +97631,7 @@
         "page-0040",
         "page-0049",
         "page-0050",
-        "page-0057",
+        "page-0058",
         "page-0063",
         "page-0067",
         "page-0199",
@@ -98900,7 +98953,7 @@
         "page-0018",
         "page-0032",
         "page-0038",
-        "page-0057",
+        "page-0058",
         "page-0061",
         "page-0067",
         "page-0159",
@@ -99437,6 +99490,7 @@
         "page-0020",
         "page-0026",
         "page-0043",
+        "page-0057",
         "page-0095",
         "page-0099",
         "page-0150",
@@ -99598,7 +99652,7 @@
       "expressions": [
         "page-0021",
         "page-0100",
-        "page-0101",
+        "page-0102",
         "page-0110",
         "page-0131",
         "page-0515",
@@ -99945,7 +99999,7 @@
       ],
       "common": [
         "page-0027",
-        "page-0100",
+        "page-0102",
         "page-0106",
         "page-0131",
         "page-0132",
@@ -100591,6 +100645,7 @@
         "page-0048",
         "page-0051",
         "page-0057",
+        "page-0058",
         "page-0228",
         "page-0230",
         "page-0535",
@@ -100603,7 +100658,7 @@
       ],
       "other": [
         "page-0049",
-        "page-0101",
+        "page-0100",
         "page-0106",
         "page-0202",
         "page-1162",
@@ -100660,7 +100715,7 @@
       ],
       "writing": [
         "page-0050",
-        "page-0100",
+        "page-0102",
         "page-1153",
         "page-1247"
       ],
@@ -100737,7 +100792,7 @@
       ],
       "javascript": [
         "page-0051",
-        "page-0100",
+        "page-0102",
         "page-0132",
         "page-0615",
         "page-0695"
@@ -101205,6 +101260,7 @@
         "page-0051",
         "page-0055",
         "page-0057",
+        "page-0058",
         "page-0106",
         "page-0155",
         "page-0541",
@@ -101704,7 +101760,7 @@
       ],
       "item": [
         "page-0059",
-        "page-0100",
+        "page-0102",
         "page-0109",
         "page-0110",
         "page-0111",
@@ -101942,7 +101998,7 @@
       ],
       "body": [
         "page-0068",
-        "page-0100",
+        "page-0102",
         "page-0703",
         "page-0824"
       ],
@@ -102242,7 +102298,7 @@
       ],
       "transforming": [
         "page-0086",
-        "page-0102"
+        "page-0101"
       ],
       "different": [
         "page-0087",
@@ -102699,7 +102755,7 @@
       ],
       "approaches": [
         "page-0097",
-        "page-0102"
+        "page-0101"
       ],
       "generate": [
         "page-0097",
@@ -102797,36 +102853,41 @@
       ],
       "versus": [
         "page-0099",
-        "page-0101",
+        "page-0100",
         "page-0710"
       ],
-      "example:": [
+      "transform": [
         "page-0100",
+        "page-0638",
+        "page-1197"
+      ],
+      "example:": [
+        "page-0102",
         "page-0132",
         "page-0215"
       ],
       "longer": [
-        "page-0100",
+        "page-0102",
         "page-0132",
         "page-0566",
         "page-1211"
       ],
       "'json": [
-        "page-0100"
+        "page-0102"
       ],
       "output'": [
-        "page-0100"
+        "page-0102"
       ],
       "contains": [
-        "page-0100"
+        "page-0102"
       ],
       "invalid": [
-        "page-0100",
+        "page-0102",
         "page-0558",
         "page-0708"
       ],
       "json": [
-        "page-0100",
+        "page-0102",
         "page-0131",
         "page-0515",
         "page-0641",
@@ -102839,7 +102900,7 @@
         "page-1176"
       ],
       "can't": [
-        "page-0100",
+        "page-0102",
         "page-0512",
         "page-0519",
         "page-0566",
@@ -102849,14 +102910,9 @@
         "page-1021"
       ],
       "syntax": [
-        "page-0100",
+        "page-0102",
         "page-1174"
       ],
-      "transform": [
-        "page-0101",
-        "page-0638",
-        "page-1197"
-      ],
       "linked": [
         "page-0105"
       ],
@@ -106479,7 +106535,7 @@
       ],
       "software": [
         "page-0345",
-        "page-0464",
+        "page-0463",
         "page-0984"
       ],
       "kafka": [
@@ -107048,13 +107104,13 @@
         "page-0462",
         "page-0982"
       ],
-      "uplead": [
+      "unleashed": [
         "page-0463",
-        "page-0985"
+        "page-0984"
       ],
-      "unleashed": [
+      "uplead": [
         "page-0464",
-        "page-0984"
+        "page-0985"
       ],
       "uproc": [
         "page-0465",
@@ -111066,6 +111122,7 @@
         "page-0055",
         "page-0056",
         "page-0057",
+        "page-0058",
         "page-0059",
         "page-0060",
         "page-0061",
@@ -112445,10 +112502,10 @@
       "twitter": [
         "page-0462"
       ],
-      "uplead": [
+      "unleashedsoftware": [
         "page-0463"
       ],
-      "unleashedsoftware": [
+      "uplead": [
         "page-0464"
       ],
       "uproc": [