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

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

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-03-17T10:30:32.807Z",
+  "generatedAt": "2026-03-17T11:31:22.125Z",
   "version": "1.0.0",
   "sourceUrl": "https://docs.n8n.io/llms.txt",
   "totalPages": 1254,
@@ -8731,6 +8731,66 @@
     },
     {
       "id": "page-0091",
+      "title": "Use case",
+      "url": "https://docs.n8n.io/courses/level-two/chapter-5/chapter-5.0/index.md",
+      "urlPath": "courses/level-two/chapter-5/chapter-5.0/index.md",
+      "category": "tutorials",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Automating a business workflow\n\nRemember [our friend Nathan](../../../level-one/chapter-3/)?\n\n**Nathan 🙋:** Hello, it's me again. My manager was so impressed with my first workflow automation solution that she entrusted me with more responsibility.\\\n**You 👩‍🔧:** More work and responsibility. Congratulations, I guess. What do you need to do now?\\\n**Nathan 🙋:** I got access to all our sales data and I'm now responsible for creating two reports: one for regional sales and one for orders prices. They're based on data from different sources and come in different formats.\\\n**You 👩‍🔧:** Sounds like a lot of manual work, but the kind that can be automated. Let's do it!\n\n## Workflow design\n\nNow that we know what Nathan wants to automate, let's list the steps he needs to take to achieve this:\n\n1. Get and combine data from all necessary sources.\n1. Sort the data and format the dates.\n1. Write binary files.\n1. Send notifications using email and Discord.\n\nn8n provides [core nodes](../../../../integrations/builtin/node-types/#core-nodes) for all these steps. This use case is somewhat complex. We should build it from three separate workflows:\n\n1. A workflow that merges the company data with external information.\n1. A workflow that generates the reports.\n1. A workflow that monitors errors in the second workflow.\n\n## Workflow prerequisites\n\nTo build the workflows, you will need the following:\n\n- An [Airtable](https://airtable.com/) account and [credentials](../../../../integrations/builtin/credentials/airtable/).\n- A [Google](https://www.google.com/account/about/) account and [credentials](../../../../integrations/builtin/credentials/google/) to access Gmail.\n- A [Discord](https://discord.com/) account and webhook URL (you receive this using email when you sign up for this course).\n\nNext, you will build these three workflows with step-by-step instructions.\n",
+        "excerpt": "# Automating a business workflow  Remember [our friend Nathan](../../../level-one/chapter-3/)?  **Nathan 🙋:** Hello, it's me again. My manager was so impressed with my first workflow automation solution that she entrusted me with more responsibility.\\ **You 👩‍🔧:** More work and responsibility. Congratulations, I guess. What do you need to do now?\\ **Nathan 🙋:** I got access to all our sales data and I'm now responsible for creating two reports: one for regional sales and one for orders price...",
+        "sections": [
+          {
+            "title": "Automating a business workflow",
+            "level": 1,
+            "content": "Remember [our friend Nathan](../../../level-one/chapter-3/)?\n\n**Nathan 🙋:** Hello, it's me again. My manager was so impressed with my first workflow automation solution that she entrusted me with more responsibility.\\\n**You 👩‍🔧:** More work and responsibility. Congratulations, I guess. What do you need to do now?\\\n**Nathan 🙋:** I got access to all our sales data and I'm now responsible for creating two reports: one for regional sales and one for orders prices. They're based on data from different sources and come in different formats.\\\n**You 👩‍🔧:** Sounds like a lot of manual work, but the kind that can be automated. Let's do it!"
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "case",
+          "automating",
+          "business",
+          "workflow",
+          "design",
+          "prerequisites"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "2 min",
+        "contentLength": 1880,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "use case # automating a business workflow\n\nremember [our friend nathan](../../../level-one/chapter-3/)?\n\n**nathan 🙋:** hello, it's me again. my manager was so impressed with my first workflow automation solution that she entrusted me with more responsibility.\\\n**you 👩‍🔧:** more work and responsibility. congratulations, i guess. what do you need to do now?\\\n**nathan 🙋:** i got access to all our sales data and i'm now responsible for creating two reports: one for regional sales and one for orders prices. they're based on data from different sources and come in different formats.\\\n**you 👩‍🔧:** sounds like a lot of manual work, but the kind that can be automated. let's do it!\n\n## workflow design\n\nnow that we know what nathan wants to automate, let's list the steps he needs to take to achieve this:\n\n1. get and combine data from all necessary sources.\n1. sort the data and format the dates.\n1. write binary files.\n1. send notifications using email and discord.\n\nn8n provides [core nodes](../../../../integrations/builtin/node-types/#core-nodes) for all these steps. this use case is somewhat complex. we should build it from three separate workflows:\n\n1. a workflow that merges the company data with external information.\n1. a workflow that generates the reports.\n1. a workflow that monitors errors in the second workflow.\n\n## workflow prerequisites\n\nto build the workflows, you will need the following:\n\n- an [airtable](https://airtable.com/) account and [credentials](../../../../integrations/builtin/credentials/airtable/).\n- a [google](https://www.google.com/account/about/) account and [credentials](../../../../integrations/builtin/credentials/google/) to access gmail.\n- a [discord](https://discord.com/) account and webhook url (you receive this using email when you sign up for this course).\n\nnext, you will build these three workflows with step-by-step instructions.\n automating a business workflow",
+        "importantTerms": [
+          "workflow",
+          "that",
+          "data",
+          "nathan",
+          "with",
+          "this",
+          "account",
+          "credentials",
+          "from",
+          "discord",
+          "integrations",
+          "builtin",
+          "build",
+          "workflows",
+          "airtable",
+          "https",
+          "google"
+        ]
+      }
+    },
+    {
+      "id": "page-0092",
       "title": "Workflow 1",
       "url": "https://docs.n8n.io/courses/level-two/chapter-5/chapter-5.1/index.md",
       "urlPath": "courses/level-two/chapter-5/chapter-5.1/index.md",
@@ -8794,7 +8854,7 @@
       }
     },
     {
-      "id": "page-0092",
+      "id": "page-0093",
       "title": "Workflow 2",
       "url": "https://docs.n8n.io/courses/level-two/chapter-5/chapter-5.2/index.md",
       "urlPath": "courses/level-two/chapter-5/chapter-5.2/index.md",
@@ -8895,7 +8955,7 @@
       }
     },
     {
-      "id": "page-0093",
+      "id": "page-0094",
       "title": "Workflow 3",
       "url": "https://docs.n8n.io/courses/level-two/chapter-5/chapter-5.3/index.md",
       "urlPath": "courses/level-two/chapter-5/chapter-5.3/index.md",
@@ -8950,66 +9010,6 @@
         ]
       }
     },
-    {
-      "id": "page-0094",
-      "title": "Use case",
-      "url": "https://docs.n8n.io/courses/level-two/chapter-5/chapter-5.0/index.md",
-      "urlPath": "courses/level-two/chapter-5/chapter-5.0/index.md",
-      "category": "tutorials",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Automating a business workflow\n\nRemember [our friend Nathan](../../../level-one/chapter-3/)?\n\n**Nathan 🙋:** Hello, it's me again. My manager was so impressed with my first workflow automation solution that she entrusted me with more responsibility.\\\n**You 👩‍🔧:** More work and responsibility. Congratulations, I guess. What do you need to do now?\\\n**Nathan 🙋:** I got access to all our sales data and I'm now responsible for creating two reports: one for regional sales and one for orders prices. They're based on data from different sources and come in different formats.\\\n**You 👩‍🔧:** Sounds like a lot of manual work, but the kind that can be automated. Let's do it!\n\n## Workflow design\n\nNow that we know what Nathan wants to automate, let's list the steps he needs to take to achieve this:\n\n1. Get and combine data from all necessary sources.\n1. Sort the data and format the dates.\n1. Write binary files.\n1. Send notifications using email and Discord.\n\nn8n provides [core nodes](../../../../integrations/builtin/node-types/#core-nodes) for all these steps. This use case is somewhat complex. We should build it from three separate workflows:\n\n1. A workflow that merges the company data with external information.\n1. A workflow that generates the reports.\n1. A workflow that monitors errors in the second workflow.\n\n## Workflow prerequisites\n\nTo build the workflows, you will need the following:\n\n- An [Airtable](https://airtable.com/) account and [credentials](../../../../integrations/builtin/credentials/airtable/).\n- A [Google](https://www.google.com/account/about/) account and [credentials](../../../../integrations/builtin/credentials/google/) to access Gmail.\n- A [Discord](https://discord.com/) account and webhook URL (you receive this using email when you sign up for this course).\n\nNext, you will build these three workflows with step-by-step instructions.\n",
-        "excerpt": "# Automating a business workflow  Remember [our friend Nathan](../../../level-one/chapter-3/)?  **Nathan 🙋:** Hello, it's me again. My manager was so impressed with my first workflow automation solution that she entrusted me with more responsibility.\\ **You 👩‍🔧:** More work and responsibility. Congratulations, I guess. What do you need to do now?\\ **Nathan 🙋:** I got access to all our sales data and I'm now responsible for creating two reports: one for regional sales and one for orders price...",
-        "sections": [
-          {
-            "title": "Automating a business workflow",
-            "level": 1,
-            "content": "Remember [our friend Nathan](../../../level-one/chapter-3/)?\n\n**Nathan 🙋:** Hello, it's me again. My manager was so impressed with my first workflow automation solution that she entrusted me with more responsibility.\\\n**You 👩‍🔧:** More work and responsibility. Congratulations, I guess. What do you need to do now?\\\n**Nathan 🙋:** I got access to all our sales data and I'm now responsible for creating two reports: one for regional sales and one for orders prices. They're based on data from different sources and come in different formats.\\\n**You 👩‍🔧:** Sounds like a lot of manual work, but the kind that can be automated. Let's do it!"
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "case",
-          "automating",
-          "business",
-          "workflow",
-          "design",
-          "prerequisites"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "2 min",
-        "contentLength": 1880,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "use case # automating a business workflow\n\nremember [our friend nathan](../../../level-one/chapter-3/)?\n\n**nathan 🙋:** hello, it's me again. my manager was so impressed with my first workflow automation solution that she entrusted me with more responsibility.\\\n**you 👩‍🔧:** more work and responsibility. congratulations, i guess. what do you need to do now?\\\n**nathan 🙋:** i got access to all our sales data and i'm now responsible for creating two reports: one for regional sales and one for orders prices. they're based on data from different sources and come in different formats.\\\n**you 👩‍🔧:** sounds like a lot of manual work, but the kind that can be automated. let's do it!\n\n## workflow design\n\nnow that we know what nathan wants to automate, let's list the steps he needs to take to achieve this:\n\n1. get and combine data from all necessary sources.\n1. sort the data and format the dates.\n1. write binary files.\n1. send notifications using email and discord.\n\nn8n provides [core nodes](../../../../integrations/builtin/node-types/#core-nodes) for all these steps. this use case is somewhat complex. we should build it from three separate workflows:\n\n1. a workflow that merges the company data with external information.\n1. a workflow that generates the reports.\n1. a workflow that monitors errors in the second workflow.\n\n## workflow prerequisites\n\nto build the workflows, you will need the following:\n\n- an [airtable](https://airtable.com/) account and [credentials](../../../../integrations/builtin/credentials/airtable/).\n- a [google](https://www.google.com/account/about/) account and [credentials](../../../../integrations/builtin/credentials/google/) to access gmail.\n- a [discord](https://discord.com/) account and webhook url (you receive this using email when you sign up for this course).\n\nnext, you will build these three workflows with step-by-step instructions.\n automating a business workflow",
-        "importantTerms": [
-          "workflow",
-          "that",
-          "data",
-          "nathan",
-          "with",
-          "this",
-          "account",
-          "credentials",
-          "from",
-          "discord",
-          "integrations",
-          "builtin",
-          "build",
-          "workflows",
-          "airtable",
-          "https",
-          "google"
-        ]
-      }
-    },
     {
       "id": "page-0095",
       "title": "Overview",
@@ -9419,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",
@@ -9601,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",
@@ -9657,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",
@@ -91253,7 +91253,7 @@
         "page-0081",
         "page-0086",
         "page-0097",
-        "page-0101",
+        "page-0100",
         "page-0105",
         "page-0108",
         "page-0130",
@@ -91310,7 +91310,7 @@
         "page-0086",
         "page-0097",
         "page-0099",
-        "page-0101",
+        "page-0100",
         "page-0105",
         "page-0106",
         "page-0108",
@@ -92160,7 +92160,7 @@
       "expression": [
         "page-0002",
         "page-0006",
-        "page-0100",
+        "page-0102",
         "page-0112",
         "page-0131",
         "page-0676",
@@ -92173,7 +92173,7 @@
       "errors": [
         "page-0002",
         "page-0089",
-        "page-0093",
+        "page-0094",
         "page-0110",
         "page-0211",
         "page-0213",
@@ -92278,7 +92278,7 @@
         "page-0071",
         "page-0097",
         "page-0098",
-        "page-0101",
+        "page-0100",
         "page-0106",
         "page-0130",
         "page-0143",
@@ -92346,7 +92346,7 @@
         "page-0002",
         "page-0050",
         "page-0100",
-        "page-0101",
+        "page-0102",
         "page-0638",
         "page-1197"
       ],
@@ -92380,8 +92380,8 @@
         "page-0086",
         "page-0087",
         "page-0088",
-        "page-0091",
         "page-0092",
+        "page-0093",
         "page-0095",
         "page-0096",
         "page-0097",
@@ -92488,7 +92488,7 @@
       ],
       "webhook": [
         "page-0002",
-        "page-0100",
+        "page-0102",
         "page-0153",
         "page-0170",
         "page-0216",
@@ -92550,7 +92550,7 @@
         "page-0003",
         "page-0012",
         "page-0027",
-        "page-0100",
+        "page-0102",
         "page-0231",
         "page-0345",
         "page-0371",
@@ -92705,10 +92705,10 @@
         "page-0039",
         "page-0068",
         "page-0077",
-        "page-0092",
+        "page-0093",
         "page-0096",
         "page-0097",
-        "page-0100",
+        "page-0102",
         "page-0110",
         "page-0132",
         "page-0144",
@@ -93004,7 +93004,7 @@
       "file": [
         "page-0003",
         "page-0051",
-        "page-0092",
+        "page-0093",
         "page-0155",
         "page-0195",
         "page-0199",
@@ -93674,7 +93674,7 @@
       ],
       "files": [
         "page-0003",
-        "page-0092",
+        "page-0093",
         "page-0134",
         "page-0155",
         "page-0201",
@@ -94164,7 +94164,7 @@
         "page-0013",
         "page-0014",
         "page-0022",
-        "page-0100",
+        "page-0102",
         "page-0136",
         "page-0151",
         "page-0153",
@@ -94520,7 +94520,7 @@
         "page-0067",
         "page-0068",
         "page-0097",
-        "page-0100",
+        "page-0102",
         "page-0134",
         "page-0136",
         "page-0141",
@@ -99470,7 +99470,7 @@
         "page-0059",
         "page-0071",
         "page-0077",
-        "page-0092",
+        "page-0093",
         "page-0567",
         "page-1181"
       ],
@@ -99652,7 +99652,7 @@
       "expressions": [
         "page-0021",
         "page-0100",
-        "page-0101",
+        "page-0102",
         "page-0110",
         "page-0131",
         "page-0515",
@@ -99999,7 +99999,7 @@
       ],
       "common": [
         "page-0027",
-        "page-0100",
+        "page-0102",
         "page-0106",
         "page-0131",
         "page-0132",
@@ -100658,7 +100658,7 @@
       ],
       "other": [
         "page-0049",
-        "page-0101",
+        "page-0100",
         "page-0106",
         "page-0202",
         "page-1162",
@@ -100715,7 +100715,7 @@
       ],
       "writing": [
         "page-0050",
-        "page-0100",
+        "page-0102",
         "page-1153",
         "page-1247"
       ],
@@ -100792,7 +100792,7 @@
       ],
       "javascript": [
         "page-0051",
-        "page-0100",
+        "page-0102",
         "page-0132",
         "page-0615",
         "page-0695"
@@ -101760,7 +101760,7 @@
       ],
       "item": [
         "page-0059",
-        "page-0100",
+        "page-0102",
         "page-0109",
         "page-0110",
         "page-0111",
@@ -101998,7 +101998,7 @@
       ],
       "body": [
         "page-0068",
-        "page-0100",
+        "page-0102",
         "page-0703",
         "page-0824"
       ],
@@ -102123,7 +102123,7 @@
       ],
       "automating": [
         "page-0073",
-        "page-0094"
+        "page-0091"
       ],
       "(real": [
         "page-0073"
@@ -102133,7 +102133,7 @@
       ],
       "case": [
         "page-0073",
-        "page-0094",
+        "page-0091",
         "page-1162",
         "page-1180"
       ],
@@ -102298,11 +102298,11 @@
       ],
       "transforming": [
         "page-0086",
-        "page-0102"
+        "page-0101"
       ],
       "different": [
         "page-0087",
-        "page-0092",
+        "page-0093",
         "page-0144",
         "page-0668",
         "page-0680"
@@ -102335,7 +102335,7 @@
       ],
       "merging": [
         "page-0088",
-        "page-0091",
+        "page-0092",
         "page-0144",
         "page-0668",
         "page-1216"
@@ -102385,37 +102385,8 @@
         "page-1176",
         "page-1178"
       ],
-      "generating": [
-        "page-0092"
-      ],
-      "reports": [
-        "page-0092"
-      ],
-      "part": [
-        "page-0092",
-        "page-0643",
-        "page-1240"
-      ],
-      "sources": [
-        "page-0092",
-        "page-0680"
-      ],
-      "regional": [
-        "page-0092"
-      ],
-      "sales": [
-        "page-0092"
-      ],
-      "total": [
-        "page-0092",
-        "page-0167"
-      ],
-      "monitoring": [
-        "page-0093",
-        "page-0208"
-      ],
       "business": [
-        "page-0094",
+        "page-0091",
         "page-0314",
         "page-0526",
         "page-0527",
@@ -102426,11 +102397,11 @@
         "page-1197"
       ],
       "design": [
-        "page-0094",
+        "page-0091",
         "page-1176"
       ],
       "prerequisites": [
-        "page-0094",
+        "page-0091",
         "page-0137",
         "page-0138",
         "page-0195",
@@ -102703,6 +102674,35 @@
         "page-1227",
         "page-1229"
       ],
+      "generating": [
+        "page-0093"
+      ],
+      "reports": [
+        "page-0093"
+      ],
+      "part": [
+        "page-0093",
+        "page-0643",
+        "page-1240"
+      ],
+      "sources": [
+        "page-0093",
+        "page-0680"
+      ],
+      "regional": [
+        "page-0093"
+      ],
+      "sales": [
+        "page-0093"
+      ],
+      "total": [
+        "page-0093",
+        "page-0167"
+      ],
+      "monitoring": [
+        "page-0094",
+        "page-0208"
+      ],
       "section": [
         "page-0095"
       ],
@@ -102755,7 +102755,7 @@
       ],
       "approaches": [
         "page-0097",
-        "page-0102"
+        "page-0101"
       ],
       "generate": [
         "page-0097",
@@ -102853,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",
@@ -102895,7 +102900,7 @@
         "page-1176"
       ],
       "can't": [
-        "page-0100",
+        "page-0102",
         "page-0512",
         "page-0519",
         "page-0566",
@@ -102905,14 +102910,9 @@
         "page-1021"
       ],
       "syntax": [
-        "page-0100",
+        "page-0102",
         "page-1174"
       ],
-      "transform": [
-        "page-0101",
-        "page-0638",
-        "page-1197"
-      ],
       "linked": [
         "page-0105"
       ],