@n8n-as-code/skills 1.5.1 → 1.6.0-next.5

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

@@ -1,8 +1,8 @@
 {
-  "generatedAt": "2026-04-02T14:22:26.993Z",
+  "generatedAt": "2026-04-02T15:40:59.107Z",
   "version": "1.0.0",
   "sourceUrl": "https://docs.n8n.io/llms.txt",
-  "totalPages": 1263,
+  "totalPages": 1262,
   "statistics": {
     "byCategory": {
       "other": 517,
@@ -17,7 +17,7 @@
       "cluster-nodes": 101,
       "trigger-nodes": 107,
       "try-it-out": 3,
-      "workflows": 24
+      "workflows": 23
     },
     "withNodeNames": 471,
     "withUseCases": 39,
@@ -1337,7 +1337,7 @@
     },
     "workflows": {
       "description": "Documentation pages",
-      "totalPages": 24,
+      "totalPages": 23,
       "pages": [
         "page-1240",
         "page-1241",
@@ -1361,8 +1361,7 @@
         "page-1259",
         "page-1260",
         "page-1261",
-        "page-1262",
-        "page-1263"
+        "page-1262"
       ]
     }
   },
@@ -2564,7 +2563,7 @@
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Log streaming\n\nFeature availability\n\nLog Streaming is available on all Enterprise plans.\n\nLog streaming allows you to send events from n8n to your own logging tools. This allows you to manage your n8n monitoring in your own alerting and logging processes.\n\n## Set up log streaming\n\nTo use log streaming, you have to add a streaming destination.\n\n1. Navigate to **Settings** > **Log Streaming**.\n1. Select **Add new destination**.\n1. Choose your destination type. n8n opens the **New Event Destination** modal.\n1. In the **New Event Destination** modal, enter the configuration information for your event destination. These depend on the type of destination you're using.\n1. Select **Events** to choose which events to stream.\n1. Select **Save**.\n\nSelf-hosted users\n\nIf you self-host n8n, you can configure additional log streaming behavior using [Environment variables](../hosting/configuration/environment-variables/logs/#log-streaming).\n\n## Events\n\nThe following events are available. You can choose which events to stream in **Settings** > **Log Streaming** > **Events**.\n\n- Workflow\n  - Started\n  - Success\n  - Failed\n  - Cancelled\n- Node executions\n  - Started\n  - Finished\n- Audit\n  - User login success\n  - User login failed\n  - User signed up\n  - User updated\n  - User deleted\n  - User invited\n  - User invitation accepted\n  - User re-invited\n  - User email failed\n  - User reset requested\n  - User reset\n  - User credentials created\n  - User credentials shared\n  - User credentials updated\n  - User credentials deleted\n  - User API created\n  - User API deleted\n  - User MFA enabled\n  - User MFA disabled\n  - User execution deleted\n  - Execution data revealed\n  - Execution data reveal failed\n  - Workflow executed\n  - Package installed\n  - Package updated\n  - Package deleted\n  - Workflow created\n  - Workflow deleted\n  - Workflow updated\n  - Workflow archived\n  - Workflow unarchived\n  - Workflow activated\n  - Workflow deactivated\n  - Workflow version updated\n  - Variable created\n  - Variable updated\n  - Variable deleted\n  - External secrets provider settings saved\n  - External secrets provider reloaded\n  - Personal publishing restricted enabled\n  - Personal publishing restricted disabled\n  - Personal sharing restricted enabled\n  - Personal sharing restricted disabled\n  - 2FA enforcement enabled\n  - 2FA enforcement disabled\n- Worker\n  - Started\n  - Stopped\n- AI node logs\n  - Memory get messages\n  - Memory added message\n  - Output parser parsed\n  - Retriever get relevant documents\n  - Embeddings embedded document\n  - Embeddings embedded query\n  - Document processed\n  - Text splitter split\n  - Tool called\n  - Vector store searched\n  - LLM generated\n  - LLM error\n  - Vector store populated\n  - Vector store updated\n- Runner\n  - Task requested\n  - Response received\n- Queue\n  - Job enqueued\n  - Job dequeued\n  - Job completed\n  - Job failed\n  - Job stalled\n\n## Destinations\n\nn8n supports three destination types:\n\n- A syslog server\n- A generic webhook\n- A Sentry client\n",
+        "markdown": "# Log streaming\n\nFeature availability\n\nLog Streaming is available on all Enterprise plans.\n\nLog streaming allows you to send events from n8n to your own logging tools. This allows you to manage your n8n monitoring in your own alerting and logging processes.\n\n## Set up log streaming\n\nTo use log streaming, you have to add a streaming destination.\n\n1. Navigate to **Settings** > **Log Streaming**.\n1. Select **Add new destination**.\n1. Choose your destination type. n8n opens the **New Event Destination** modal.\n1. In the **New Event Destination** modal, enter the configuration information for your event destination. These depend on the type of destination you're using.\n1. Select **Events** to choose which events to stream.\n1. Select **Save**.\n\nSelf-hosted users\n\nIf you self-host n8n, you can configure additional log streaming behavior using [Environment variables](../hosting/configuration/environment-variables/logs/#log-streaming).\n\n## Events\n\nThe following events are available. You can choose which events to stream in **Settings** > **Log Streaming** > **Events**.\n\n- Workflow\n  - Started\n  - Success\n  - Failed\n  - Cancelled\n- Node executions\n  - Started\n  - Finished\n- Audit\n  - User login success\n  - User login failed\n  - User signed up\n  - User updated\n  - User deleted\n  - User invited\n  - User invitation accepted\n  - User re-invited\n  - User email failed\n  - User reset requested\n  - User reset\n  - User credentials created\n  - User credentials shared\n  - User credentials updated\n  - User credentials deleted\n  - User API created\n  - User API deleted\n  - User MFA enabled\n  - User MFA disabled\n  - User execution deleted\n  - Workflow executed\n  - Package installed\n  - Package updated\n  - Package deleted\n  - Workflow created\n  - Workflow deleted\n  - Workflow updated\n  - Workflow archived\n  - Workflow unarchived\n  - Workflow activated\n  - Workflow deactivated\n  - Workflow version updated\n  - Variable created\n  - Variable updated\n  - Variable deleted\n  - External secrets provider settings saved\n  - External secrets provider reloaded\n  - Personal publishing restricted enabled\n  - Personal publishing restricted disabled\n  - Personal sharing restricted enabled\n  - Personal sharing restricted disabled\n  - 2FA enforcement enabled\n  - 2FA enforcement disabled\n- Worker\n  - Started\n  - Stopped\n- AI node logs\n  - Memory get messages\n  - Memory added message\n  - Output parser parsed\n  - Retriever get relevant documents\n  - Embeddings embedded document\n  - Embeddings embedded query\n  - Document processed\n  - Text splitter split\n  - Tool called\n  - Vector store searched\n  - LLM generated\n  - LLM error\n  - Vector store populated\n  - Vector store updated\n- Runner\n  - Task requested\n  - Response received\n- Queue\n  - Job enqueued\n  - Job dequeued\n  - Job completed\n  - Job failed\n  - Job stalled\n\n## Destinations\n\nn8n supports three destination types:\n\n- A syslog server\n- A generic webhook\n- A Sentry client\n",
         "excerpt": "# Log streaming  Feature availability  Log Streaming is available on all Enterprise plans.  Log streaming allows you to send events from n8n to your own logging tools. This allows you to manage your n8n monitoring in your own alerting and logging processes.  ## Set up log streaming  To use log streaming, you have to add a streaming destination.  1. Navigate to **Settings** > **Log Streaming**. 1. Select **Add new destination**. 1. Choose your destination type. n8n opens the **New Event Destinati...",
         "sections": [
           {
@@ -2585,11 +2584,11 @@
         "codeExamples": 0,
         "complexity": "beginner",
         "readingTime": "3 min",
-        "contentLength": 2994,
+        "contentLength": 2933,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "log streaming # log streaming\n\nfeature availability\n\nlog streaming is available on all enterprise plans.\n\nlog streaming allows you to send events from n8n to your own logging tools. this allows you to manage your n8n monitoring in your own alerting and logging processes.\n\n## set up log streaming\n\nto use log streaming, you have to add a streaming destination.\n\n1. navigate to **settings** > **log streaming**.\n1. select **add new destination**.\n1. choose your destination type. n8n opens the **new event destination** modal.\n1. in the **new event destination** modal, enter the configuration information for your event destination. these depend on the type of destination you're using.\n1. select **events** to choose which events to stream.\n1. select **save**.\n\nself-hosted users\n\nif you self-host n8n, you can configure additional log streaming behavior using [environment variables](../hosting/configuration/environment-variables/logs/#log-streaming).\n\n## events\n\nthe following events are available. you can choose which events to stream in **settings** > **log streaming** > **events**.\n\n- workflow\n  - started\n  - success\n  - failed\n  - cancelled\n- node executions\n  - started\n  - finished\n- audit\n  - user login success\n  - user login failed\n  - user signed up\n  - user updated\n  - user deleted\n  - user invited\n  - user invitation accepted\n  - user re-invited\n  - user email failed\n  - user reset requested\n  - user reset\n  - user credentials created\n  - user credentials shared\n  - user credentials updated\n  - user credentials deleted\n  - user api created\n  - user api deleted\n  - user mfa enabled\n  - user mfa disabled\n  - user execution deleted\n  - execution data revealed\n  - execution data reveal failed\n  - workflow executed\n  - package installed\n  - package updated\n  - package deleted\n  - workflow created\n  - workflow deleted\n  - workflow updated\n  - workflow archived\n  - workflow unarchived\n  - workflow activated\n  - workflow deactivated\n  - workflow version updated\n  - variable created\n  - variable updated\n  - variable deleted\n  - external secrets provider settings saved\n  - external secrets provider reloaded\n  - personal publishing restricted enabled\n  - personal publishing restricted disabled\n  - personal sharing restricted enabled\n  - personal sharing restricted disabled\n  - 2fa enforcement enabled\n  - 2fa enforcement disabled\n- worker\n  - started\n  - stopped\n- ai node logs\n  - memory get messages\n  - memory added message\n  - output parser parsed\n  - retriever get relevant documents\n  - embeddings embedded document\n  - embeddings embedded query\n  - document processed\n  - text splitter split\n  - tool called\n  - vector store searched\n  - llm generated\n  - llm error\n  - vector store populated\n  - vector store updated\n- runner\n  - task requested\n  - response received\n- queue\n  - job enqueued\n  - job dequeued\n  - job completed\n  - job failed\n  - job stalled\n\n## destinations\n\nn8n supports three destination types:\n\n- a syslog server\n- a generic webhook\n- a sentry client\n log streaming",
+        "fullText": "log streaming # log streaming\n\nfeature availability\n\nlog streaming is available on all enterprise plans.\n\nlog streaming allows you to send events from n8n to your own logging tools. this allows you to manage your n8n monitoring in your own alerting and logging processes.\n\n## set up log streaming\n\nto use log streaming, you have to add a streaming destination.\n\n1. navigate to **settings** > **log streaming**.\n1. select **add new destination**.\n1. choose your destination type. n8n opens the **new event destination** modal.\n1. in the **new event destination** modal, enter the configuration information for your event destination. these depend on the type of destination you're using.\n1. select **events** to choose which events to stream.\n1. select **save**.\n\nself-hosted users\n\nif you self-host n8n, you can configure additional log streaming behavior using [environment variables](../hosting/configuration/environment-variables/logs/#log-streaming).\n\n## events\n\nthe following events are available. you can choose which events to stream in **settings** > **log streaming** > **events**.\n\n- workflow\n  - started\n  - success\n  - failed\n  - cancelled\n- node executions\n  - started\n  - finished\n- audit\n  - user login success\n  - user login failed\n  - user signed up\n  - user updated\n  - user deleted\n  - user invited\n  - user invitation accepted\n  - user re-invited\n  - user email failed\n  - user reset requested\n  - user reset\n  - user credentials created\n  - user credentials shared\n  - user credentials updated\n  - user credentials deleted\n  - user api created\n  - user api deleted\n  - user mfa enabled\n  - user mfa disabled\n  - user execution deleted\n  - workflow executed\n  - package installed\n  - package updated\n  - package deleted\n  - workflow created\n  - workflow deleted\n  - workflow updated\n  - workflow archived\n  - workflow unarchived\n  - workflow activated\n  - workflow deactivated\n  - workflow version updated\n  - variable created\n  - variable updated\n  - variable deleted\n  - external secrets provider settings saved\n  - external secrets provider reloaded\n  - personal publishing restricted enabled\n  - personal publishing restricted disabled\n  - personal sharing restricted enabled\n  - personal sharing restricted disabled\n  - 2fa enforcement enabled\n  - 2fa enforcement disabled\n- worker\n  - started\n  - stopped\n- ai node logs\n  - memory get messages\n  - memory added message\n  - output parser parsed\n  - retriever get relevant documents\n  - embeddings embedded document\n  - embeddings embedded query\n  - document processed\n  - text splitter split\n  - tool called\n  - vector store searched\n  - llm generated\n  - llm error\n  - vector store populated\n  - vector store updated\n- runner\n  - task requested\n  - response received\n- queue\n  - job enqueued\n  - job dequeued\n  - job completed\n  - job failed\n  - job stalled\n\n## destinations\n\nn8n supports three destination types:\n\n- a syslog server\n- a generic webhook\n- a sentry client\n log streaming",
         "importantTerms": [
           "user",
           "streaming",
@@ -2611,7 +2610,6 @@
           "choose",
           "event",
           "started",
-          "execution",
           "package",
           "variable",
           "vector",
@@ -13026,49 +13024,6 @@
     },
     {
       "id": "page-0146",
-      "title": "Waiting",
-      "url": "https://docs.n8n.io/flow-logic/waiting/index.md",
-      "urlPath": "flow-logic/waiting/index.md",
-      "category": "flow-logic",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Waiting\n\nWaiting allows you to pause a workflow mid-execution, then resume where the workflow left off, with the same data. This is useful if you need to rate limit your calls to a service, or wait for an external event to complete. You can wait for a specified duration, or until a webhook fires.\n\nMaking a workflow wait uses the [Wait](../../integrations/builtin/core-nodes/n8n-nodes-base.wait/) node. Refer to the node documentation for usage details.\n\nn8n provides a workflow template with a basic example of [Rate limiting and waiting for external events](https://n8n.io/workflows/1749-rate-limiting-and-waiting-for-external-events/).\n",
-        "excerpt": "# Waiting  Waiting allows you to pause a workflow mid-execution, then resume where the workflow left off, with the same data. This is useful if you need to rate limit your calls to a service, or wait for an external event to complete. You can wait for a specified duration, or until a webhook fires.  Making a workflow wait uses the [Wait](../../integrations/builtin/core-nodes/n8n-nodes-base.wait/) node. Refer to the node documentation for usage details.  n8n provides a workflow template with a ba...",
-        "sections": [
-          {
-            "title": "Waiting",
-            "level": 1,
-            "content": "Waiting allows you to pause a workflow mid-execution, then resume where the workflow left off, with the same data. This is useful if you need to rate limit your calls to a service, or wait for an external event to complete. You can wait for a specified duration, or until a webhook fires.\n\nMaking a workflow wait uses the [Wait](../../integrations/builtin/core-nodes/n8n-nodes-base.wait/) node. Refer to the node documentation for usage details.\n\nn8n provides a workflow template with a basic example of [Rate limiting and waiting for external events](https://n8n.io/workflows/1749-rate-limiting-and-waiting-for-external-events/)."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "waiting"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "1 min",
-        "contentLength": 642,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "waiting # waiting\n\nwaiting allows you to pause a workflow mid-execution, then resume where the workflow left off, with the same data. this is useful if you need to rate limit your calls to a service, or wait for an external event to complete. you can wait for a specified duration, or until a webhook fires.\n\nmaking a workflow wait uses the [wait](../../integrations/builtin/core-nodes/n8n-nodes-base.wait/) node. refer to the node documentation for usage details.\n\nn8n provides a workflow template with a basic example of [rate limiting and waiting for external events](https://n8n.io/workflows/1749-rate-limiting-and-waiting-for-external-events/).\n waiting",
-        "importantTerms": [
-          "waiting",
-          "wait",
-          "workflow",
-          "rate",
-          "external"
-        ]
-      }
-    },
-    {
-      "id": "page-0147",
       "title": "Sub-workflows",
       "url": "https://docs.n8n.io/flow-logic/subworkflows/index.md",
       "urlPath": "flow-logic/subworkflows/index.md",
@@ -13156,6 +13111,49 @@
         ]
       }
     },
+    {
+      "id": "page-0147",
+      "title": "Waiting",
+      "url": "https://docs.n8n.io/flow-logic/waiting/index.md",
+      "urlPath": "flow-logic/waiting/index.md",
+      "category": "flow-logic",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Waiting\n\nWaiting allows you to pause a workflow mid-execution, then resume where the workflow left off, with the same data. This is useful if you need to rate limit your calls to a service, or wait for an external event to complete. You can wait for a specified duration, or until a webhook fires.\n\nMaking a workflow wait uses the [Wait](../../integrations/builtin/core-nodes/n8n-nodes-base.wait/) node. Refer to the node documentation for usage details.\n\nn8n provides a workflow template with a basic example of [Rate limiting and waiting for external events](https://n8n.io/workflows/1749-rate-limiting-and-waiting-for-external-events/).\n",
+        "excerpt": "# Waiting  Waiting allows you to pause a workflow mid-execution, then resume where the workflow left off, with the same data. This is useful if you need to rate limit your calls to a service, or wait for an external event to complete. You can wait for a specified duration, or until a webhook fires.  Making a workflow wait uses the [Wait](../../integrations/builtin/core-nodes/n8n-nodes-base.wait/) node. Refer to the node documentation for usage details.  n8n provides a workflow template with a ba...",
+        "sections": [
+          {
+            "title": "Waiting",
+            "level": 1,
+            "content": "Waiting allows you to pause a workflow mid-execution, then resume where the workflow left off, with the same data. This is useful if you need to rate limit your calls to a service, or wait for an external event to complete. You can wait for a specified duration, or until a webhook fires.\n\nMaking a workflow wait uses the [Wait](../../integrations/builtin/core-nodes/n8n-nodes-base.wait/) node. Refer to the node documentation for usage details.\n\nn8n provides a workflow template with a basic example of [Rate limiting and waiting for external events](https://n8n.io/workflows/1749-rate-limiting-and-waiting-for-external-events/)."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "waiting"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "1 min",
+        "contentLength": 642,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "waiting # waiting\n\nwaiting allows you to pause a workflow mid-execution, then resume where the workflow left off, with the same data. this is useful if you need to rate limit your calls to a service, or wait for an external event to complete. you can wait for a specified duration, or until a webhook fires.\n\nmaking a workflow wait uses the [wait](../../integrations/builtin/core-nodes/n8n-nodes-base.wait/) node. refer to the node documentation for usage details.\n\nn8n provides a workflow template with a basic example of [rate limiting and waiting for external events](https://n8n.io/workflows/1749-rate-limiting-and-waiting-for-external-events/).\n waiting",
+        "importantTerms": [
+          "waiting",
+          "wait",
+          "workflow",
+          "rate",
+          "external"
+        ]
+      }
+    },
     {
       "id": "page-0148",
       "title": "Contributing",
@@ -19335,13 +19333,13 @@
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Securing n8n\n\nSecuring your n8n instance can take several forms.\n\nAt a high level, you can:\n\n- Conduct a [security audit](../security-audit/) to identify security risks.\n- [Set up SSL](../set-up-ssl/) to enforce secure connections.\n- [Set up Single Sign-On](../set-up-sso/) for user account management.\n- Use [two-factor authentication (2FA)](../../../user-management/two-factor-auth/) for your users.\n\nYou can also protect sensitive data processed by your workflows:\n\n- [Redact execution data](../../../workflows/executions/execution-data-redaction/) to hide input and output data from workflow executions.\n\nMore granularly, consider blocking or opting out of features or data collection you don't want:\n\n- [Disable the public API](../disable-public-api/) if you aren't using it.\n- [Opt out of data collection](../telemetry-opt-out/) of the anonymous data n8n collects automatically.\n- [Block certain nodes](../blocking-nodes/) from being available to your users.\n- [Protect against SSRF attacks](../ssrf-protection/) to control which hosts and IP ranges workflow nodes can connect to.\n- [Restrict account registration](../restrict-by-email-verification/) to email-verified users.\n",
-        "excerpt": "# Securing n8n  Securing your n8n instance can take several forms.  At a high level, you can:  - Conduct a [security audit](../security-audit/) to identify security risks. - [Set up SSL](../set-up-ssl/) to enforce secure connections. - [Set up Single Sign-On](../set-up-sso/) for user account management. - Use [two-factor authentication (2FA)](../../../user-management/two-factor-auth/) for your users.  You can also protect sensitive data processed by your workflows:  - [Redact execution data](../...",
+        "markdown": "# Securing n8n\n\nSecuring your n8n instance can take several forms.\n\nAt a high level, you can:\n\n- Conduct a [security audit](../security-audit/) to identify security risks.\n- [Set up SSL](../set-up-ssl/) to enforce secure connections.\n- [Set up Single Sign-On](../set-up-sso/) for user account management.\n- Use [two-factor authentication (2FA)](../../../user-management/two-factor-auth/) for your users.\n\nMore granularly, consider blocking or opting out of features or data collection you don't want:\n\n- [Disable the public API](../disable-public-api/) if you aren't using it.\n- [Opt out of data collection](../telemetry-opt-out/) of the anonymous data n8n collects automatically.\n- [Block certain nodes](../blocking-nodes/) from being available to your users.\n- [Protect against SSRF attacks](../ssrf-protection/) to control which hosts and IP ranges workflow nodes can connect to.\n- [Restrict account registration](../restrict-by-email-verification/) to email-verified users.\n",
+        "excerpt": "# Securing n8n  Securing your n8n instance can take several forms.  At a high level, you can:  - Conduct a [security audit](../security-audit/) to identify security risks. - [Set up SSL](../set-up-ssl/) to enforce secure connections. - [Set up Single Sign-On](../set-up-sso/) for user account management. - Use [two-factor authentication (2FA)](../../../user-management/two-factor-auth/) for your users.  More granularly, consider blocking or opting out of features or data collection you don't want:...",
         "sections": [
           {
             "title": "Securing n8n",
             "level": 1,
-            "content": "Securing your n8n instance can take several forms.\n\nAt a high level, you can:\n\n- Conduct a [security audit](../security-audit/) to identify security risks.\n- [Set up SSL](../set-up-ssl/) to enforce secure connections.\n- [Set up Single Sign-On](../set-up-sso/) for user account management.\n- Use [two-factor authentication (2FA)](../../../user-management/two-factor-auth/) for your users.\n\nYou can also protect sensitive data processed by your workflows:\n\n- [Redact execution data](../../../workflows/executions/execution-data-redaction/) to hide input and output data from workflow executions.\n\nMore granularly, consider blocking or opting out of features or data collection you don't want:\n\n- [Disable the public API](../disable-public-api/) if you aren't using it.\n- [Opt out of data collection](../telemetry-opt-out/) of the anonymous data n8n collects automatically.\n- [Block certain nodes](../blocking-nodes/) from being available to your users.\n- [Protect against SSRF attacks](../ssrf-protecti"
+            "content": "Securing your n8n instance can take several forms.\n\nAt a high level, you can:\n\n- Conduct a [security audit](../security-audit/) to identify security risks.\n- [Set up SSL](../set-up-ssl/) to enforce secure connections.\n- [Set up Single Sign-On](../set-up-sso/) for user account management.\n- Use [two-factor authentication (2FA)](../../../user-management/two-factor-auth/) for your users.\n\nMore granularly, consider blocking or opting out of features or data collection you don't want:\n\n- [Disable the public API](../disable-public-api/) if you aren't using it.\n- [Opt out of data collection](../telemetry-opt-out/) of the anonymous data n8n collects automatically.\n- [Block certain nodes](../blocking-nodes/) from being available to your users.\n- [Protect against SSRF attacks](../ssrf-protection/) to control which hosts and IP ranges workflow nodes can connect to.\n- [Restrict account registration](../restrict-by-email-verification/) to email-verified users."
           }
         ]
       },
@@ -19359,17 +19357,17 @@
         "codeExamples": 0,
         "complexity": "beginner",
         "readingTime": "1 min",
-        "contentLength": 1184,
+        "contentLength": 978,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "overview # securing n8n\n\nsecuring your n8n instance can take several forms.\n\nat a high level, you can:\n\n- conduct a [security audit](../security-audit/) to identify security risks.\n- [set up ssl](../set-up-ssl/) to enforce secure connections.\n- [set up single sign-on](../set-up-sso/) for user account management.\n- use [two-factor authentication (2fa)](../../../user-management/two-factor-auth/) for your users.\n\nyou can also protect sensitive data processed by your workflows:\n\n- [redact execution data](../../../workflows/executions/execution-data-redaction/) to hide input and output data from workflow executions.\n\nmore granularly, consider blocking or opting out of features or data collection you don't want:\n\n- [disable the public api](../disable-public-api/) if you aren't using it.\n- [opt out of data collection](../telemetry-opt-out/) of the anonymous data n8n collects automatically.\n- [block certain nodes](../blocking-nodes/) from being available to your users.\n- [protect against ssrf attacks](../ssrf-protection/) to control which hosts and ip ranges workflow nodes can connect to.\n- [restrict account registration](../restrict-by-email-verification/) to email-verified users.\n securing n8n",
+        "fullText": "overview # securing n8n\n\nsecuring your n8n instance can take several forms.\n\nat a high level, you can:\n\n- conduct a [security audit](../security-audit/) to identify security risks.\n- [set up ssl](../set-up-ssl/) to enforce secure connections.\n- [set up single sign-on](../set-up-sso/) for user account management.\n- use [two-factor authentication (2fa)](../../../user-management/two-factor-auth/) for your users.\n\nmore granularly, consider blocking or opting out of features or data collection you don't want:\n\n- [disable the public api](../disable-public-api/) if you aren't using it.\n- [opt out of data collection](../telemetry-opt-out/) of the anonymous data n8n collects automatically.\n- [block certain nodes](../blocking-nodes/) from being available to your users.\n- [protect against ssrf attacks](../ssrf-protection/) to control which hosts and ip ranges workflow nodes can connect to.\n- [restrict account registration](../restrict-by-email-verification/) to email-verified users.\n securing n8n",
         "importantTerms": [
-          "data",
-          "your",
           "securing",
+          "your",
           "security",
           "users",
+          "data",
           "nodes"
         ]
       }
@@ -29429,54 +29427,6 @@
     },
     {
       "id": "page-0371",
-      "title": "MessageBird",
-      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.messagebird/index.md",
-      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.messagebird/index.md",
-      "category": "integrations",
-      "subcategory": "app-nodes",
-      "nodeName": "messagebird",
-      "nodeType": "n8n-nodes-base.messagebird",
-      "content": {
-        "markdown": "# MessageBird node\n\nUse the MessageBird node to automate work in MessageBird, and integrate MessageBird with other applications. n8n has built-in support for a wide range of MessageBird features, including sending messages, and getting balances.\n\nOn this page, you'll find a list of operations the MessageBird node supports and links to more resources.\n\nCredentials\n\nRefer to [MessageBird credentials](../../credentials/messagebird/) for guidance on setting up authentication.\n\n## Operations\n\n- SMS\n  - Send text messages (SMS)\n- Balance\n  - Get the balance\n\n## Templates and examples\n\n[Browse MessageBird integration templates](https://n8n.io/integrations/messagebird/), or [search all templates](https://n8n.io/workflows/)\n",
-        "excerpt": "# MessageBird node  Use the MessageBird node to automate work in MessageBird, and integrate MessageBird with other applications. n8n has built-in support for a wide range of MessageBird features, including sending messages, and getting balances.  On this page, you'll find a list of operations the MessageBird node supports and links to more resources.  Credentials  Refer to [MessageBird credentials](../../credentials/messagebird/) for guidance on setting up authentication.  ## Operations  - SMS...",
-        "sections": [
-          {
-            "title": "MessageBird node",
-            "level": 1,
-            "content": "Use the MessageBird node to automate work in MessageBird, and integrate MessageBird with other applications. n8n has built-in support for a wide range of MessageBird features, including sending messages, and getting balances.\n\nOn this page, you'll find a list of operations the MessageBird node supports and links to more resources.\n\nCredentials\n\nRefer to [MessageBird credentials](../../credentials/messagebird/) for guidance on setting up authentication."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "messagebird",
-          "node",
-          "operations",
-          "templates",
-          "examples"
-        ],
-        "useCases": [],
-        "operations": [
-          ""
-        ],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "1 min",
-        "contentLength": 725,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "messagebird # messagebird node\n\nuse the messagebird node to automate work in messagebird, and integrate messagebird with other applications. n8n has built-in support for a wide range of messagebird features, including sending messages, and getting balances.\n\non this page, you'll find a list of operations the messagebird node supports and links to more resources.\n\ncredentials\n\nrefer to [messagebird credentials](../../credentials/messagebird/) for guidance on setting up authentication.\n\n## operations\n\n- sms\n  - send text messages (sms)\n- balance\n  - get the balance\n\n## templates and examples\n\n[browse messagebird integration templates](https://n8n.io/integrations/messagebird/), or [search all templates](https://n8n.io/workflows/)\n messagebird node",
-        "importantTerms": [
-          "messagebird",
-          "node",
-          "credentials",
-          "templates"
-        ]
-      }
-    },
-    {
-      "id": "page-0372",
       "title": "Metabase",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.metabase/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.metabase/index.md",
@@ -29537,7 +29487,7 @@
       }
     },
     {
-      "id": "page-0373",
+      "id": "page-0372",
       "title": "Microsoft Dynamics CRM",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.microsoftdynamicscrm/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.microsoftdynamicscrm/index.md",
@@ -29599,6 +29549,54 @@
         ]
       }
     },
+    {
+      "id": "page-0373",
+      "title": "MessageBird",
+      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.messagebird/index.md",
+      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.messagebird/index.md",
+      "category": "integrations",
+      "subcategory": "app-nodes",
+      "nodeName": "messagebird",
+      "nodeType": "n8n-nodes-base.messagebird",
+      "content": {
+        "markdown": "# MessageBird node\n\nUse the MessageBird node to automate work in MessageBird, and integrate MessageBird with other applications. n8n has built-in support for a wide range of MessageBird features, including sending messages, and getting balances.\n\nOn this page, you'll find a list of operations the MessageBird node supports and links to more resources.\n\nCredentials\n\nRefer to [MessageBird credentials](../../credentials/messagebird/) for guidance on setting up authentication.\n\n## Operations\n\n- SMS\n  - Send text messages (SMS)\n- Balance\n  - Get the balance\n\n## Templates and examples\n\n[Browse MessageBird integration templates](https://n8n.io/integrations/messagebird/), or [search all templates](https://n8n.io/workflows/)\n",
+        "excerpt": "# MessageBird node  Use the MessageBird node to automate work in MessageBird, and integrate MessageBird with other applications. n8n has built-in support for a wide range of MessageBird features, including sending messages, and getting balances.  On this page, you'll find a list of operations the MessageBird node supports and links to more resources.  Credentials  Refer to [MessageBird credentials](../../credentials/messagebird/) for guidance on setting up authentication.  ## Operations  - SMS...",
+        "sections": [
+          {
+            "title": "MessageBird node",
+            "level": 1,
+            "content": "Use the MessageBird node to automate work in MessageBird, and integrate MessageBird with other applications. n8n has built-in support for a wide range of MessageBird features, including sending messages, and getting balances.\n\nOn this page, you'll find a list of operations the MessageBird node supports and links to more resources.\n\nCredentials\n\nRefer to [MessageBird credentials](../../credentials/messagebird/) for guidance on setting up authentication."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "messagebird",
+          "node",
+          "operations",
+          "templates",
+          "examples"
+        ],
+        "useCases": [],
+        "operations": [
+          ""
+        ],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "1 min",
+        "contentLength": 725,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "messagebird # messagebird node\n\nuse the messagebird node to automate work in messagebird, and integrate messagebird with other applications. n8n has built-in support for a wide range of messagebird features, including sending messages, and getting balances.\n\non this page, you'll find a list of operations the messagebird node supports and links to more resources.\n\ncredentials\n\nrefer to [messagebird credentials](../../credentials/messagebird/) for guidance on setting up authentication.\n\n## operations\n\n- sms\n  - send text messages (sms)\n- balance\n  - get the balance\n\n## templates and examples\n\n[browse messagebird integration templates](https://n8n.io/integrations/messagebird/), or [search all templates](https://n8n.io/workflows/)\n messagebird node",
+        "importantTerms": [
+          "messagebird",
+          "node",
+          "credentials",
+          "templates"
+        ]
+      }
+    },
     {
       "id": "page-0374",
       "title": "Microsoft Entra ID",
@@ -39306,68 +39304,6 @@
     },
     {
       "id": "page-0511",
-      "title": "Common issues",
-      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/common-issues/index.md",
-      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/common-issues/index.md",
-      "category": "integrations",
-      "subcategory": "app-nodes",
-      "nodeName": "googlesheets",
-      "nodeType": "n8n-nodes-base.googlesheets",
-      "content": {
-        "markdown": "# Google Sheets node common issues\n\nHere are some common errors and issues with the [Google Sheets node](../) and steps to resolve or troubleshoot them.\n\n## Append an array\n\nTo insert an array of data into Google Sheets, you must convert the array into a valid JSON (key, value) format.\n\nTo do so, consider using:\n\n1. The [Split Out](../../../core-nodes/n8n-nodes-base.splitout/) node.\n\n1. The [AI Transform](../../../core-nodes/n8n-nodes-base.aitransform/) node. For example, try entering something like:\n\n   ```\n   Convert 'languages' array to JSON (key, value) pairs.\n   ```\n\n1. The [Code node](../../../core-nodes/n8n-nodes-base.code/).\n\n## Column names were updated after the node's setup\n\nYou'll receive this error if the Google Sheet's column names have changed since you set up the node.\n\nTo refresh the column names, re-select **Mapping Column Mode**. This should prompt the node to fetch the column names again.\n\nOnce the column names refresh, update the node parameters.\n",
-        "excerpt": "# Google Sheets node common issues  Here are some common errors and issues with the [Google Sheets node](../) and steps to resolve or troubleshoot them.  ## Append an array  To insert an array of data into Google Sheets, you must convert the array into a valid JSON (key, value) format.  To do so, consider using:  1. The [Split Out](../../../core-nodes/n8n-nodes-base.splitout/) node.  1. The [AI Transform](../../../core-nodes/n8n-nodes-base.aitransform/) node. For example, try entering something...",
-        "sections": [
-          {
-            "title": "Google Sheets node common issues",
-            "level": 1,
-            "content": "Here are some common errors and issues with the [Google Sheets node](../) and steps to resolve or troubleshoot them."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "common",
-          "issues",
-          "google",
-          "sheets",
-          "node",
-          "append",
-          "array",
-          "column",
-          "names",
-          "were",
-          "updated",
-          "after",
-          "node's",
-          "setup"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 1,
-        "complexity": "beginner",
-        "readingTime": "1 min",
-        "contentLength": 982,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "common issues # google sheets node common issues\n\nhere are some common errors and issues with the [google sheets node](../) and steps to resolve or troubleshoot them.\n\n## append an array\n\nto insert an array of data into google sheets, you must convert the array into a valid json (key, value) format.\n\nto do so, consider using:\n\n1. the [split out](../../../core-nodes/n8n-nodes-base.splitout/) node.\n\n1. the [ai transform](../../../core-nodes/n8n-nodes-base.aitransform/) node. for example, try entering something like:\n\n   ```\n   convert 'languages' array to json (key, value) pairs.\n   ```\n\n1. the [code node](../../../core-nodes/n8n-nodes-base.code/).\n\n## column names were updated after the node's setup\n\nyou'll receive this error if the google sheet's column names have changed since you set up the node.\n\nto refresh the column names, re-select **mapping column mode**. this should prompt the node to fetch the column names again.\n\nonce the column names refresh, update the node parameters.\n google sheets node common issues",
-        "importantTerms": [
-          "node",
-          "nodes",
-          "column",
-          "google",
-          "names",
-          "common",
-          "issues",
-          "sheets",
-          "array",
-          "core",
-          "base"
-        ]
-      }
-    },
-    {
-      "id": "page-0512",
       "title": "Document operations",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/document-operations/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/document-operations/index.md",
@@ -39445,7 +39381,7 @@
       }
     },
     {
-      "id": "page-0513",
+      "id": "page-0512",
       "title": "Sheet within Document operations",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/sheet-operations/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/sheet-operations/index.md",
@@ -39547,7 +39483,7 @@
       }
     },
     {
-      "id": "page-0514",
+      "id": "page-0513",
       "title": "MySQL",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.mysql/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.mysql/index.md",
@@ -39627,7 +39563,7 @@
       }
     },
     {
-      "id": "page-0515",
+      "id": "page-0514",
       "title": "Common issues",
       "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.mysql/common-issues/index.md",
       "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.mysql/common-issues/index.md",
@@ -39737,6 +39673,68 @@
         ]
       }
     },
+    {
+      "id": "page-0515",
+      "title": "Common issues",
+      "url": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/common-issues/index.md",
+      "urlPath": "integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/common-issues/index.md",
+      "category": "integrations",
+      "subcategory": "app-nodes",
+      "nodeName": "googlesheets",
+      "nodeType": "n8n-nodes-base.googlesheets",
+      "content": {
+        "markdown": "# Google Sheets node common issues\n\nHere are some common errors and issues with the [Google Sheets node](../) and steps to resolve or troubleshoot them.\n\n## Append an array\n\nTo insert an array of data into Google Sheets, you must convert the array into a valid JSON (key, value) format.\n\nTo do so, consider using:\n\n1. The [Split Out](../../../core-nodes/n8n-nodes-base.splitout/) node.\n\n1. The [AI Transform](../../../core-nodes/n8n-nodes-base.aitransform/) node. For example, try entering something like:\n\n   ```\n   Convert 'languages' array to JSON (key, value) pairs.\n   ```\n\n1. The [Code node](../../../core-nodes/n8n-nodes-base.code/).\n\n## Column names were updated after the node's setup\n\nYou'll receive this error if the Google Sheet's column names have changed since you set up the node.\n\nTo refresh the column names, re-select **Mapping Column Mode**. This should prompt the node to fetch the column names again.\n\nOnce the column names refresh, update the node parameters.\n",
+        "excerpt": "# Google Sheets node common issues  Here are some common errors and issues with the [Google Sheets node](../) and steps to resolve or troubleshoot them.  ## Append an array  To insert an array of data into Google Sheets, you must convert the array into a valid JSON (key, value) format.  To do so, consider using:  1. The [Split Out](../../../core-nodes/n8n-nodes-base.splitout/) node.  1. The [AI Transform](../../../core-nodes/n8n-nodes-base.aitransform/) node. For example, try entering something...",
+        "sections": [
+          {
+            "title": "Google Sheets node common issues",
+            "level": 1,
+            "content": "Here are some common errors and issues with the [Google Sheets node](../) and steps to resolve or troubleshoot them."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "common",
+          "issues",
+          "google",
+          "sheets",
+          "node",
+          "append",
+          "array",
+          "column",
+          "names",
+          "were",
+          "updated",
+          "after",
+          "node's",
+          "setup"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 1,
+        "complexity": "beginner",
+        "readingTime": "1 min",
+        "contentLength": 982,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "common issues # google sheets node common issues\n\nhere are some common errors and issues with the [google sheets node](../) and steps to resolve or troubleshoot them.\n\n## append an array\n\nto insert an array of data into google sheets, you must convert the array into a valid json (key, value) format.\n\nto do so, consider using:\n\n1. the [split out](../../../core-nodes/n8n-nodes-base.splitout/) node.\n\n1. the [ai transform](../../../core-nodes/n8n-nodes-base.aitransform/) node. for example, try entering something like:\n\n   ```\n   convert 'languages' array to json (key, value) pairs.\n   ```\n\n1. the [code node](../../../core-nodes/n8n-nodes-base.code/).\n\n## column names were updated after the node's setup\n\nyou'll receive this error if the google sheet's column names have changed since you set up the node.\n\nto refresh the column names, re-select **mapping column mode**. this should prompt the node to fetch the column names again.\n\nonce the column names refresh, update the node parameters.\n google sheets node common issues",
+        "importantTerms": [
+          "node",
+          "nodes",
+          "column",
+          "google",
+          "names",
+          "common",
+          "issues",
+          "sheets",
+          "array",
+          "core",
+          "base"
+        ]
+      }
+    },
     {
       "id": "page-0516",
       "title": "Notion",
@@ -73089,75 +73087,6 @@
     },
     {
       "id": "page-0965",
-      "title": "SSH credentials",
-      "url": "https://docs.n8n.io/integrations/builtin/credentials/ssh/index.md",
-      "urlPath": "integrations/builtin/credentials/ssh/index.md",
-      "category": "other",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# SSH credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [SSH](../../core-nodes/n8n-nodes-base.ssh/)\n\n## Prerequisites\n\n- Create a remote server with SSH enabled.\n- Create a user account that can `ssh` into the server using one of the following:\n  - Their own [password](#using-password)\n  - An SSH [private key](#using-private-key)\n\n## Supported authentication methods\n\n- [Password](#using-password): Use this method if you have a user account that can `ssh` into the server using their own password.\n- [Private key](#using-private-key): Use this method if you have a user account that uses an SSH key for the server or service.\n\n## Related resources\n\nSecure Shell (SSH) protocol is a method for securely sending commands over a network. Refer to [Connecting to GitHub with SSH](https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh) for an example of SSH setup.\n\n## Using password\n\nUse this method if you have a user account that can `ssh` into the server using their own password.\n\nTo configure this credential, you'll need to:\n\n1. Enter the IP address of the server you're connecting to as the **Host**.\n1. Enter the **Port** to use for the connection. SSH uses port `22` by default.\n1. Enter the **Username** for a user account with `ssh` access on the server.\n1. Enter the **Password** for that user account.\n\n## Using private key\n\nUse this method if you have a user account that uses an SSH key for the server or service.\n\nTo configure this credential, you'll need to:\n\n1. Enter the IP address of the server you're connecting to as the **Host**.\n1. Enter the **Port** to use for the connection. SSH uses port `22` by default.\n1. Enter the **Username** of the account that generated the private key.\n1. Enter the entire contents of your SSH **Private Key**.\n1. If you created a **Passphrase** for the **Private Key**, enter the passphrase.\n   - If you didn't create a passphrase for the key, leave blank.\n",
-        "excerpt": "# SSH credentials  You can use these credentials to authenticate the following nodes:  - [SSH](../../core-nodes/n8n-nodes-base.ssh/)  ## Prerequisites  - Create a remote server with SSH enabled. - Create a user account that can `ssh` into the server using one of the following:   - Their own [password](#using-password)   - An SSH [private key](#using-private-key)  ## Supported authentication methods  - [Password](#using-password): Use this method if you have a user account that can `ssh` into the...",
-        "sections": [
-          {
-            "title": "SSH credentials",
-            "level": 1,
-            "content": "You can use these credentials to authenticate the following nodes:\n\n- [SSH](../../core-nodes/n8n-nodes-base.ssh/)"
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "credentials",
-          "prerequisites",
-          "supported",
-          "authentication",
-          "methods",
-          "related",
-          "resources",
-          "using",
-          "password",
-          "private"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "2 min",
-        "contentLength": 1978,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "ssh credentials # ssh credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [ssh](../../core-nodes/n8n-nodes-base.ssh/)\n\n## prerequisites\n\n- create a remote server with ssh enabled.\n- create a user account that can `ssh` into the server using one of the following:\n  - their own [password](#using-password)\n  - an ssh [private key](#using-private-key)\n\n## supported authentication methods\n\n- [password](#using-password): use this method if you have a user account that can `ssh` into the server using their own password.\n- [private key](#using-private-key): use this method if you have a user account that uses an ssh key for the server or service.\n\n## related resources\n\nsecure shell (ssh) protocol is a method for securely sending commands over a network. refer to [connecting to github with ssh](https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh) for an example of ssh setup.\n\n## using password\n\nuse this method if you have a user account that can `ssh` into the server using their own password.\n\nto configure this credential, you'll need to:\n\n1. enter the ip address of the server you're connecting to as the **host**.\n1. enter the **port** to use for the connection. ssh uses port `22` by default.\n1. enter the **username** for a user account with `ssh` access on the server.\n1. enter the **password** for that user account.\n\n## using private key\n\nuse this method if you have a user account that uses an ssh key for the server or service.\n\nto configure this credential, you'll need to:\n\n1. enter the ip address of the server you're connecting to as the **host**.\n1. enter the **port** to use for the connection. ssh uses port `22` by default.\n1. enter the **username** of the account that generated the private key.\n1. enter the entire contents of your ssh **private key**.\n1. if you created a **passphrase** for the **private key**, enter the passphrase.\n   - if you didn't create a passphrase for the key, leave blank.\n ssh credentials",
-        "importantTerms": [
-          "server",
-          "using",
-          "enter",
-          "account",
-          "password",
-          "private",
-          "user",
-          "that",
-          "this",
-          "method",
-          "github",
-          "credentials",
-          "with",
-          "have",
-          "uses",
-          "connecting",
-          "port",
-          "nodes",
-          "create",
-          "into",
-          "their",
-          "passphrase"
-        ]
-      }
-    },
-    {
-      "id": "page-0966",
       "title": "Stackby credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/stackby/index.md",
       "urlPath": "integrations/builtin/credentials/stackby/index.md",
@@ -73208,7 +73137,7 @@
       }
     },
     {
-      "id": "page-0967",
+      "id": "page-0966",
       "title": "Storyblok credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/storyblok/index.md",
       "urlPath": "integrations/builtin/credentials/storyblok/index.md",
@@ -73274,6 +73203,75 @@
         ]
       }
     },
+    {
+      "id": "page-0967",
+      "title": "SSH credentials",
+      "url": "https://docs.n8n.io/integrations/builtin/credentials/ssh/index.md",
+      "urlPath": "integrations/builtin/credentials/ssh/index.md",
+      "category": "other",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# SSH credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [SSH](../../core-nodes/n8n-nodes-base.ssh/)\n\n## Prerequisites\n\n- Create a remote server with SSH enabled.\n- Create a user account that can `ssh` into the server using one of the following:\n  - Their own [password](#using-password)\n  - An SSH [private key](#using-private-key)\n\n## Supported authentication methods\n\n- [Password](#using-password): Use this method if you have a user account that can `ssh` into the server using their own password.\n- [Private key](#using-private-key): Use this method if you have a user account that uses an SSH key for the server or service.\n\n## Related resources\n\nSecure Shell (SSH) protocol is a method for securely sending commands over a network. Refer to [Connecting to GitHub with SSH](https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh) for an example of SSH setup.\n\n## Using password\n\nUse this method if you have a user account that can `ssh` into the server using their own password.\n\nTo configure this credential, you'll need to:\n\n1. Enter the IP address of the server you're connecting to as the **Host**.\n1. Enter the **Port** to use for the connection. SSH uses port `22` by default.\n1. Enter the **Username** for a user account with `ssh` access on the server.\n1. Enter the **Password** for that user account.\n\n## Using private key\n\nUse this method if you have a user account that uses an SSH key for the server or service.\n\nTo configure this credential, you'll need to:\n\n1. Enter the IP address of the server you're connecting to as the **Host**.\n1. Enter the **Port** to use for the connection. SSH uses port `22` by default.\n1. Enter the **Username** of the account that generated the private key.\n1. Enter the entire contents of your SSH **Private Key**.\n1. If you created a **Passphrase** for the **Private Key**, enter the passphrase.\n   - If you didn't create a passphrase for the key, leave blank.\n",
+        "excerpt": "# SSH credentials  You can use these credentials to authenticate the following nodes:  - [SSH](../../core-nodes/n8n-nodes-base.ssh/)  ## Prerequisites  - Create a remote server with SSH enabled. - Create a user account that can `ssh` into the server using one of the following:   - Their own [password](#using-password)   - An SSH [private key](#using-private-key)  ## Supported authentication methods  - [Password](#using-password): Use this method if you have a user account that can `ssh` into the...",
+        "sections": [
+          {
+            "title": "SSH credentials",
+            "level": 1,
+            "content": "You can use these credentials to authenticate the following nodes:\n\n- [SSH](../../core-nodes/n8n-nodes-base.ssh/)"
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "credentials",
+          "prerequisites",
+          "supported",
+          "authentication",
+          "methods",
+          "related",
+          "resources",
+          "using",
+          "password",
+          "private"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "2 min",
+        "contentLength": 1978,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "ssh credentials # ssh credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [ssh](../../core-nodes/n8n-nodes-base.ssh/)\n\n## prerequisites\n\n- create a remote server with ssh enabled.\n- create a user account that can `ssh` into the server using one of the following:\n  - their own [password](#using-password)\n  - an ssh [private key](#using-private-key)\n\n## supported authentication methods\n\n- [password](#using-password): use this method if you have a user account that can `ssh` into the server using their own password.\n- [private key](#using-private-key): use this method if you have a user account that uses an ssh key for the server or service.\n\n## related resources\n\nsecure shell (ssh) protocol is a method for securely sending commands over a network. refer to [connecting to github with ssh](https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh) for an example of ssh setup.\n\n## using password\n\nuse this method if you have a user account that can `ssh` into the server using their own password.\n\nto configure this credential, you'll need to:\n\n1. enter the ip address of the server you're connecting to as the **host**.\n1. enter the **port** to use for the connection. ssh uses port `22` by default.\n1. enter the **username** for a user account with `ssh` access on the server.\n1. enter the **password** for that user account.\n\n## using private key\n\nuse this method if you have a user account that uses an ssh key for the server or service.\n\nto configure this credential, you'll need to:\n\n1. enter the ip address of the server you're connecting to as the **host**.\n1. enter the **port** to use for the connection. ssh uses port `22` by default.\n1. enter the **username** of the account that generated the private key.\n1. enter the entire contents of your ssh **private key**.\n1. if you created a **passphrase** for the **private key**, enter the passphrase.\n   - if you didn't create a passphrase for the key, leave blank.\n ssh credentials",
+        "importantTerms": [
+          "server",
+          "using",
+          "enter",
+          "account",
+          "password",
+          "private",
+          "user",
+          "that",
+          "this",
+          "method",
+          "github",
+          "credentials",
+          "with",
+          "have",
+          "uses",
+          "connecting",
+          "port",
+          "nodes",
+          "create",
+          "into",
+          "their",
+          "passphrase"
+        ]
+      }
+    },
     {
       "id": "page-0968",
       "title": "Strapi credentials",
@@ -80560,6 +80558,55 @@
     },
     {
       "id": "page-1093",
+      "title": "Notion Trigger",
+      "url": "https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.notiontrigger/index.md",
+      "urlPath": "integrations/builtin/trigger-nodes/n8n-nodes-base.notiontrigger/index.md",
+      "category": "trigger-nodes",
+      "subcategory": null,
+      "nodeName": "notiontrigger",
+      "nodeType": "n8n-nodes-base.notiontrigger",
+      "content": {
+        "markdown": "# Notion Trigger node\n\n[Notion](https://notion.so) is an all-in-one workspace for your notes, tasks, wikis, and databases.\n\nCredentials\n\nYou can find authentication information for this node [here](../../credentials/notion/).\n\nExamples and templates\n\nFor usage examples and templates to help you get started, refer to n8n's [Notion Trigger integrations](https://n8n.io/integrations/notion-trigger-beta/) page.\n\n## Events\n\n- Page added to database\n- Page updated in database\n\n## Related resources\n\nn8n provides an app node for Notion. You can find the node docs [here](../../app-nodes/n8n-nodes-base.notion/).\n\nView [example workflows and related content](https://n8n.io/integrations/notion-trigger-beta/) on n8n's website.\n\nRefer to [Notion's documentation](https://developers.notion.com/) for details about their API.\n",
+        "excerpt": "# Notion Trigger node  [Notion](https://notion.so) is an all-in-one workspace for your notes, tasks, wikis, and databases.  Credentials  You can find authentication information for this node [here](../../credentials/notion/).  Examples and templates  For usage examples and templates to help you get started, refer to n8n's [Notion Trigger integrations](https://n8n.io/integrations/notion-trigger-beta/) page.  ## Events  - Page added to database - Page updated in database  ## Related resources  n8n...",
+        "sections": [
+          {
+            "title": "Notion Trigger node",
+            "level": 1,
+            "content": "[Notion](https://notion.so) is an all-in-one workspace for your notes, tasks, wikis, and databases.\n\nCredentials\n\nYou can find authentication information for this node [here](../../credentials/notion/).\n\nExamples and templates\n\nFor usage examples and templates to help you get started, refer to n8n's [Notion Trigger integrations](https://n8n.io/integrations/notion-trigger-beta/) page."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "notion",
+          "trigger",
+          "node",
+          "events",
+          "related",
+          "resources"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "1 min",
+        "contentLength": 819,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "notion trigger # notion trigger node\n\n[notion](https://notion.so) is an all-in-one workspace for your notes, tasks, wikis, and databases.\n\ncredentials\n\nyou can find authentication information for this node [here](../../credentials/notion/).\n\nexamples and templates\n\nfor usage examples and templates to help you get started, refer to n8n's [notion trigger integrations](https://n8n.io/integrations/notion-trigger-beta/) page.\n\n## events\n\n- page added to database\n- page updated in database\n\n## related resources\n\nn8n provides an app node for notion. you can find the node docs [here](../../app-nodes/n8n-nodes-base.notion/).\n\nview [example workflows and related content](https://n8n.io/integrations/notion-trigger-beta/) on n8n's website.\n\nrefer to [notion's documentation](https://developers.notion.com/) for details about their api.\n notion trigger node",
+        "importantTerms": [
+          "notion",
+          "trigger",
+          "node",
+          "https",
+          "integrations",
+          "page"
+        ]
+      }
+    },
+    {
+      "id": "page-1094",
       "title": "Onfleet Trigger",
       "url": "https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.onfleettrigger/index.md",
       "urlPath": "integrations/builtin/trigger-nodes/n8n-nodes-base.onfleettrigger/index.md",
@@ -80605,7 +80652,7 @@
       }
     },
     {
-      "id": "page-1094",
+      "id": "page-1095",
       "title": "PayPal Trigger",
       "url": "https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.paypaltrigger/index.md",
       "urlPath": "integrations/builtin/trigger-nodes/n8n-nodes-base.paypaltrigger/index.md",
@@ -80647,55 +80694,6 @@
         ]
       }
     },
-    {
-      "id": "page-1095",
-      "title": "Notion Trigger",
-      "url": "https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.notiontrigger/index.md",
-      "urlPath": "integrations/builtin/trigger-nodes/n8n-nodes-base.notiontrigger/index.md",
-      "category": "trigger-nodes",
-      "subcategory": null,
-      "nodeName": "notiontrigger",
-      "nodeType": "n8n-nodes-base.notiontrigger",
-      "content": {
-        "markdown": "# Notion Trigger node\n\n[Notion](https://notion.so) is an all-in-one workspace for your notes, tasks, wikis, and databases.\n\nCredentials\n\nYou can find authentication information for this node [here](../../credentials/notion/).\n\nExamples and templates\n\nFor usage examples and templates to help you get started, refer to n8n's [Notion Trigger integrations](https://n8n.io/integrations/notion-trigger-beta/) page.\n\n## Events\n\n- Page added to database\n- Page updated in database\n\n## Related resources\n\nn8n provides an app node for Notion. You can find the node docs [here](../../app-nodes/n8n-nodes-base.notion/).\n\nView [example workflows and related content](https://n8n.io/integrations/notion-trigger-beta/) on n8n's website.\n\nRefer to [Notion's documentation](https://developers.notion.com/) for details about their API.\n",
-        "excerpt": "# Notion Trigger node  [Notion](https://notion.so) is an all-in-one workspace for your notes, tasks, wikis, and databases.  Credentials  You can find authentication information for this node [here](../../credentials/notion/).  Examples and templates  For usage examples and templates to help you get started, refer to n8n's [Notion Trigger integrations](https://n8n.io/integrations/notion-trigger-beta/) page.  ## Events  - Page added to database - Page updated in database  ## Related resources  n8n...",
-        "sections": [
-          {
-            "title": "Notion Trigger node",
-            "level": 1,
-            "content": "[Notion](https://notion.so) is an all-in-one workspace for your notes, tasks, wikis, and databases.\n\nCredentials\n\nYou can find authentication information for this node [here](../../credentials/notion/).\n\nExamples and templates\n\nFor usage examples and templates to help you get started, refer to n8n's [Notion Trigger integrations](https://n8n.io/integrations/notion-trigger-beta/) page."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "notion",
-          "trigger",
-          "node",
-          "events",
-          "related",
-          "resources"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "1 min",
-        "contentLength": 819,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "notion trigger # notion trigger node\n\n[notion](https://notion.so) is an all-in-one workspace for your notes, tasks, wikis, and databases.\n\ncredentials\n\nyou can find authentication information for this node [here](../../credentials/notion/).\n\nexamples and templates\n\nfor usage examples and templates to help you get started, refer to n8n's [notion trigger integrations](https://n8n.io/integrations/notion-trigger-beta/) page.\n\n## events\n\n- page added to database\n- page updated in database\n\n## related resources\n\nn8n provides an app node for notion. you can find the node docs [here](../../app-nodes/n8n-nodes-base.notion/).\n\nview [example workflows and related content](https://n8n.io/integrations/notion-trigger-beta/) on n8n's website.\n\nrefer to [notion's documentation](https://developers.notion.com/) for details about their api.\n notion trigger node",
-        "importantTerms": [
-          "notion",
-          "trigger",
-          "node",
-          "https",
-          "integrations",
-          "page"
-        ]
-      }
-    },
     {
       "id": "page-1096",
       "title": "Pipedrive Trigger",
@@ -90180,7 +90178,7 @@
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Custom project roles\n\nFeature availability\n\nCustom roles are available on Self-hosted Enterprise and Cloud Enterprise plans. Refer to n8n's [pricing page](https://n8n.io/pricing/) for plan details.\n\n**Available from:** n8n version 1.122.0 (released November 24, 2025)\n\nSecret vault scopes are available from n8n version `2.13.0`\n\nInstance roles vs project roles\n\nn8n has two types of roles: * **Instance roles** ([account types](../../account-types/)): Owner, Admin, and Member roles that span the entire n8n instance and all projects * **Project roles**: Roles that apply within a specific project (Admin, Editor, Viewer, and custom roles)\n\nCustom roles are project-level roles. They define permissions within individual projects, not across the entire instance.\n\nCustom project roles allow you to create roles with specific permissions tailored to your team's needs. Unlike the built-in project roles (Admin, Editor, Viewer), custom roles let you define granular access to workflows, credentials, and other project resources.\n\n## Create a custom role\n\nInstance owners and instance admins can create custom roles.\n\nTo create a custom role:\n\n1. Go to **Settings** > **Project roles**.\n1. Select **Create role**.\n1. Enter a role name and optional description.\n1. Select the permissions (scopes) for this role:\n   - **Workflow permissions**: Create, read, update, publish, delete, list, execute, move, or share workflows\n   - **Credential permissions**: Create, read, update, delete, list, move, or share credentials\n   - **Project permissions**: List, read, update, or delete projects\n   - **Folder permissions**: Create, read, update, delete, list, or move folders\n   - **Data table permissions**: Create, read, update, delete, list project tables, read/write rows\n   - **Project variable permissions**: Create, read, update, delete, or list project variables\n   - **Secret vault permissions**: Create, view, update, delete, and sync (reload) vaults of a project\n   - **Secrets permission**: Use secrets in credentials\n   - **Source control**: Push to source control\n1. Select **Create role**.\n\n## Assign a custom role to users\n\nProject admins can assign custom roles to project members. Custom roles apply only within the specific project where they're assigned. A user can have different roles in different projects.\n\nTo assign a custom role:\n\n1. Select the project.\n1. Select **Project settings**.\n1. Under **Project members**, browse or search for users.\n1. Select the user and choose the custom role from the dropdown.\n1. Select **Save**.\n\nProject-level permissions\n\nCustom role permissions only apply within the project where the role is assigned. To grant the same permissions across multiple projects, assign the custom role in each project individually.\n\n## Edit a custom role\n\nTo modify an existing custom role:\n\n1. Go to **Settings** > **Project roles**.\n1. Find the custom role you want to edit.\n1. Select the **three-dot menu** > **Edit**.\n1. Update the role name, description, or permissions.\n1. Select **Save changes**.\n\nEditing affects all assigned users\n\nChanges to a custom role immediately affect all users assigned to that role in any project. If the role is used across multiple projects, the permission changes apply everywhere the role is assigned.\n\n## Duplicate a custom role\n\nTo create a new role based on an existing one:\n\n1. Go to **Settings** > **Project roles**.\n1. Find the role you want to duplicate.\n1. Select the **three-dot menu** > **Duplicate**.\n1. Modify the role name and permissions as needed.\n1. Select **Create role**.\n\n## Delete a custom role\n\nTo delete a custom role:\n\n1. Go to **Settings** > **Project roles**.\n1. Find the role you want to delete.\n1. Select the **three-dot menu** > **Delete**.\n1. Confirm the deletion.\n\nReassign users before deletion\n\nIf users are assigned to this role, you must first reassign them to a different role before deleting it.\n\n## Permission scopes reference\n\nCustom roles use permission scopes to define what users can do within a project. Here are the available scopes by resource:\n\n### Workflow scopes\n\n- `workflow:create` - Create new workflows\n- `workflow:read` - View workflow details\n- `workflow:update` - Edit workflows\n- `workflow:publish` - Publish workflows\n- `workflow:unpublish` - Unpublish workflows\n- `workflow:delete` - Delete workflows\n- `workflow:list` - View workflows in project\n- `workflow:execute-chat` - Execute workflows via chat interface\n- `workflow:move` - Move workflows between projects\n- `workflow:share` - Share workflows with other users\n- `workflow:updateRedactionSetting` - Manage the data redaction policy for workflows\n\n### Execution scopes\n\n- `execution:reveal` - Reveal redacted execution data (refer to [Execution data redaction](../../../workflows/executions/execution-data-redaction/))\n\n### Credential scopes\n\n- `credential:create` - Create new credentials\n- `credential:read` - View credential details\n- `credential:update` - Edit credentials\n- `credential:delete` - Delete credentials\n- `credential:list` - View credentials in project\n- `credential:move` - Move credentials between projects\n- `credential:share` - Share credentials with other users\n\n### Project scopes\n\n- `project:list` - View available projects\n- `project:read` - View project details\n- `project:update` - Edit project settings (Admin only)\n- `project:delete` - Delete projects (Admin only)\n\n### Folder scopes\n\n- `folder:create` - Create new folders\n- `folder:read` - View folder contents\n- `folder:update` - Rename folders\n- `folder:delete` - Delete folders\n- `folder:list` - View folders in project\n- `folder:move` - Move folders\n\n### Data table scopes\n\n- `dataTable:create` - Create new data tables\n- `dataTable:read` - View data table schema\n- `dataTable:update` - Modify data table schema\n- `dataTable:delete` - Delete data tables\n- `dataTable:listProject` - View data tables in project\n- `dataTable:readRow` - Read rows from data tables\n- `dataTable:writeRow` - Insert or update rows in data tables\n\n### Project variable scopes\n\n- `projectVariable:list` - View project variables\n- `projectVariable:read` - View variable values\n- `projectVariable:create` - Create new variables\n- `projectVariable:update` - Edit variable values\n- `projectVariable:delete` - Delete variables\n\n### Secret vault scopes\n\n- `secretsVaults:view` - View secret vaults in a project\n- `secretsVaults:create` - Create new secret vaults within project\n- `secretsVaults:edit` - Edit secret vault configuration\n- `secretsVaults:delete` - Delete secret vaults of a project\n- `secretsVaults:sync` - Reload a vault's secrets\n- `secrets:list` - Use secrets in credentials\n\n### Source control scopes\n\n- `sourceControl:push` - Push changes to source control\n\n## Common custom role examples\n\nThese are example custom project roles you can create for common use cases. Remember that these roles apply within individual projects, not across your entire n8n instance.\n\n### Workflow Developer\n\nA role for users who work only with workflows: * `workflow:create`, `workflow:read`, `workflow:update`, `workflow:delete`, `workflow:list` * `credential:read`, `credential:list` (view credentials but not modify) * `project:list`, `project:read`\n\n### Credential Manager\n\nA role for users who manage credentials: * `credential:create`, `credential:read`, `credential:update`, `credential:delete`, `credential:list`, `credential:share` * `workflow:read`, `workflow:list` (view workflows to understand credential usage) * `project:list`, `project:read`\n\n### Secrets User\n\nA role for users who need to use external secrets in credentials but not manage vaults: * `secrets:list` (use secrets in credentials expressions) * `credential:create`, `credential:read`, `credential:update`, `credential:list` (manage credentials with secrets) * `workflow:read`, `workflow:list` * `project:list`, `project:read`\n\n### Workflow Publisher\n\nA role for users who can publish workflows without full edit access: * `workflow:read`, `workflow:list`, `workflow:publish`, `workflow:unpublish` * `credential:read`, `credential:list` * `project:list`, `project:read`\n\nCombining scopes\n\nYou can combine any scopes to create roles that match your specific needs. Consider the principle of least privilege: grant only the permissions users need to perform their tasks.\n",
+        "markdown": "# Custom project roles\n\nFeature availability\n\nCustom roles are available on Self-hosted Enterprise and Cloud Enterprise plans. Refer to n8n's [pricing page](https://n8n.io/pricing/) for plan details.\n\n**Available from:** n8n version 1.122.0 (released November 24, 2025)\n\nSecret vault scopes are available from n8n version `2.13.0`\n\nInstance roles vs project roles\n\nn8n has two types of roles: * **Instance roles** ([account types](../../account-types/)): Owner, Admin, and Member roles that span the entire n8n instance and all projects * **Project roles**: Roles that apply within a specific project (Admin, Editor, Viewer, and custom roles)\n\nCustom roles are project-level roles. They define permissions within individual projects, not across the entire instance.\n\nCustom project roles allow you to create roles with specific permissions tailored to your team's needs. Unlike the built-in project roles (Admin, Editor, Viewer), custom roles let you define granular access to workflows, credentials, and other project resources.\n\n## Create a custom role\n\nInstance owners and instance admins can create custom roles.\n\nTo create a custom role:\n\n1. Go to **Settings** > **Project roles**.\n1. Select **Create role**.\n1. Enter a role name and optional description.\n1. Select the permissions (scopes) for this role:\n   - **Workflow permissions**: Create, read, update, publish, delete, list, execute, move, or share workflows\n   - **Credential permissions**: Create, read, update, delete, list, move, or share credentials\n   - **Project permissions**: List, read, update, or delete projects\n   - **Folder permissions**: Create, read, update, delete, list, or move folders\n   - **Data table permissions**: Create, read, update, delete, list project tables, read/write rows\n   - **Project variable permissions**: Create, read, update, delete, or list project variables\n   - **Secret vault permissions**: Create, view, update, delete, and sync (reload) vaults of a project\n   - **Secrets permission**: Use secrets in credentials\n   - **Source control**: Push to source control\n1. Select **Create role**.\n\n## Assign a custom role to users\n\nProject admins can assign custom roles to project members. Custom roles apply only within the specific project where they're assigned. A user can have different roles in different projects.\n\nTo assign a custom role:\n\n1. Select the project.\n1. Select **Project settings**.\n1. Under **Project members**, browse or search for users.\n1. Select the user and choose the custom role from the dropdown.\n1. Select **Save**.\n\nProject-level permissions\n\nCustom role permissions only apply within the project where the role is assigned. To grant the same permissions across multiple projects, assign the custom role in each project individually.\n\n## Edit a custom role\n\nTo modify an existing custom role:\n\n1. Go to **Settings** > **Project roles**.\n1. Find the custom role you want to edit.\n1. Select the **three-dot menu** > **Edit**.\n1. Update the role name, description, or permissions.\n1. Select **Save changes**.\n\nEditing affects all assigned users\n\nChanges to a custom role immediately affect all users assigned to that role in any project. If the role is used across multiple projects, the permission changes apply everywhere the role is assigned.\n\n## Duplicate a custom role\n\nTo create a new role based on an existing one:\n\n1. Go to **Settings** > **Project roles**.\n1. Find the role you want to duplicate.\n1. Select the **three-dot menu** > **Duplicate**.\n1. Modify the role name and permissions as needed.\n1. Select **Create role**.\n\n## Delete a custom role\n\nTo delete a custom role:\n\n1. Go to **Settings** > **Project roles**.\n1. Find the role you want to delete.\n1. Select the **three-dot menu** > **Delete**.\n1. Confirm the deletion.\n\nReassign users before deletion\n\nIf users are assigned to this role, you must first reassign them to a different role before deleting it.\n\n## Permission scopes reference\n\nCustom roles use permission scopes to define what users can do within a project. Here are the available scopes by resource:\n\n### Workflow scopes\n\n- `workflow:create` - Create new workflows\n- `workflow:read` - View workflow details\n- `workflow:update` - Edit workflows\n- `workflow:publish` - Publish workflows\n- `workflow:unpublish` - Unpublish workflows\n- `workflow:delete` - Delete workflows\n- `workflow:list` - View workflows in project\n- `workflow:execute-chat` - Execute workflows via chat interface\n- `workflow:move` - Move workflows between projects\n- `workflow:share` - Share workflows with other users\n\n### Credential scopes\n\n- `credential:create` - Create new credentials\n- `credential:read` - View credential details\n- `credential:update` - Edit credentials\n- `credential:delete` - Delete credentials\n- `credential:list` - View credentials in project\n- `credential:move` - Move credentials between projects\n- `credential:share` - Share credentials with other users\n\n### Project scopes\n\n- `project:list` - View available projects\n- `project:read` - View project details\n- `project:update` - Edit project settings (Admin only)\n- `project:delete` - Delete projects (Admin only)\n\n### Folder scopes\n\n- `folder:create` - Create new folders\n- `folder:read` - View folder contents\n- `folder:update` - Rename folders\n- `folder:delete` - Delete folders\n- `folder:list` - View folders in project\n- `folder:move` - Move folders\n\n### Data table scopes\n\n- `dataTable:create` - Create new data tables\n- `dataTable:read` - View data table schema\n- `dataTable:update` - Modify data table schema\n- `dataTable:delete` - Delete data tables\n- `dataTable:listProject` - View data tables in project\n- `dataTable:readRow` - Read rows from data tables\n- `dataTable:writeRow` - Insert or update rows in data tables\n\n### Project variable scopes\n\n- `projectVariable:list` - View project variables\n- `projectVariable:read` - View variable values\n- `projectVariable:create` - Create new variables\n- `projectVariable:update` - Edit variable values\n- `projectVariable:delete` - Delete variables\n\n### Secret vault scopes\n\n- `secretsVaults:view` - View secret vaults in a project\n- `secretsVaults:create` - Create new secret vaults within project\n- `secretsVaults:edit` - Edit secret vault configuration\n- `secretsVaults:delete` - Delete secret vaults of a project\n- `secretsVaults:sync` - Reload a vault's secrets\n- `secrets:list` - Use secrets in credentials\n\n### Source control scopes\n\n- `sourceControl:push` - Push changes to source control\n\n## Common custom role examples\n\nThese are example custom project roles you can create for common use cases. Remember that these roles apply within individual projects, not across your entire n8n instance.\n\n### Workflow Developer\n\nA role for users who work only with workflows: * `workflow:create`, `workflow:read`, `workflow:update`, `workflow:delete`, `workflow:list` * `credential:read`, `credential:list` (view credentials but not modify) * `project:list`, `project:read`\n\n### Credential Manager\n\nA role for users who manage credentials: * `credential:create`, `credential:read`, `credential:update`, `credential:delete`, `credential:list`, `credential:share` * `workflow:read`, `workflow:list` (view workflows to understand credential usage) * `project:list`, `project:read`\n\n### Secrets User\n\nA role for users who need to use external secrets in credentials but not manage vaults: * `secrets:list` (use secrets in credentials expressions) * `credential:create`, `credential:read`, `credential:update`, `credential:list` (manage credentials with secrets) * `workflow:read`, `workflow:list` * `project:list`, `project:read`\n\n### Workflow Publisher\n\nA role for users who can publish workflows without full edit access: * `workflow:read`, `workflow:list`, `workflow:publish`, `workflow:unpublish` * `credential:read`, `credential:list` * `project:list`, `project:read`\n\nCombining scopes\n\nYou can combine any scopes to create roles that match your specific needs. Consider the principle of least privilege: grant only the permissions users need to perform their tasks.\n",
         "excerpt": "# Custom project roles  Feature availability  Custom roles are available on Self-hosted Enterprise and Cloud Enterprise plans. Refer to n8n's [pricing page](https://n8n.io/pricing/) for plan details.  **Available from:** n8n version 1.122.0 (released November 24, 2025)  Secret vault scopes are available from n8n version `2.13.0`  Instance roles vs project roles  n8n has two types of roles: * **Instance roles** ([account types](../../account-types/)): Owner, Admin, and Member roles that span the...",
         "sections": [
           {
@@ -90206,7 +90204,6 @@
           "scopes",
           "reference",
           "workflow",
-          "execution",
           "credential",
           "folder",
           "data",
@@ -90229,36 +90226,36 @@
         "codeExamples": 0,
         "complexity": "beginner",
         "readingTime": "6 min",
-        "contentLength": 8285,
+        "contentLength": 8028,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "custom roles # custom project roles\n\nfeature availability\n\ncustom roles are available on self-hosted enterprise and cloud enterprise plans. refer to n8n's [pricing page](https://n8n.io/pricing/) for plan details.\n\n**available from:** n8n version 1.122.0 (released november 24, 2025)\n\nsecret vault scopes are available from n8n version `2.13.0`\n\ninstance roles vs project roles\n\nn8n has two types of roles: * **instance roles** ([account types](../../account-types/)): owner, admin, and member roles that span the entire n8n instance and all projects * **project roles**: roles that apply within a specific project (admin, editor, viewer, and custom roles)\n\ncustom roles are project-level roles. they define permissions within individual projects, not across the entire instance.\n\ncustom project roles allow you to create roles with specific permissions tailored to your team's needs. unlike the built-in project roles (admin, editor, viewer), custom roles let you define granular access to workflows, credentials, and other project resources.\n\n## create a custom role\n\ninstance owners and instance admins can create custom roles.\n\nto create a custom role:\n\n1. go to **settings** > **project roles**.\n1. select **create role**.\n1. enter a role name and optional description.\n1. select the permissions (scopes) for this role:\n   - **workflow permissions**: create, read, update, publish, delete, list, execute, move, or share workflows\n   - **credential permissions**: create, read, update, delete, list, move, or share credentials\n   - **project permissions**: list, read, update, or delete projects\n   - **folder permissions**: create, read, update, delete, list, or move folders\n   - **data table permissions**: create, read, update, delete, list project tables, read/write rows\n   - **project variable permissions**: create, read, update, delete, or list project variables\n   - **secret vault permissions**: create, view, update, delete, and sync (reload) vaults of a project\n   - **secrets permission**: use secrets in credentials\n   - **source control**: push to source control\n1. select **create role**.\n\n## assign a custom role to users\n\nproject admins can assign custom roles to project members. custom roles apply only within the specific project where they're assigned. a user can have different roles in different projects.\n\nto assign a custom role:\n\n1. select the project.\n1. select **project settings**.\n1. under **project members**, browse or search for users.\n1. select the user and choose the custom role from the dropdown.\n1. select **save**.\n\nproject-level permissions\n\ncustom role permissions only apply within the project where the role is assigned. to grant the same permissions across multiple projects, assign the custom role in each project individually.\n\n## edit a custom role\n\nto modify an existing custom role:\n\n1. go to **settings** > **project roles**.\n1. find the custom role you want to edit.\n1. select the **three-dot menu** > **edit**.\n1. update the role name, description, or permissions.\n1. select **save changes**.\n\nediting affects all assigned users\n\nchanges to a custom role immediately affect all users assigned to that role in any project. if the role is used across multiple projects, the permission changes apply everywhere the role is assigned.\n\n## duplicate a custom role\n\nto create a new role based on an existing one:\n\n1. go to **settings** > **project roles**.\n1. find the role you want to duplicate.\n1. select the **three-dot menu** > **duplicate**.\n1. modify the role name and permissions as needed.\n1. select **create role**.\n\n## delete a custom role\n\nto delete a custom role:\n\n1. go to **settings** > **project roles**.\n1. find the role you want to delete.\n1. select the **three-dot menu** > **delete**.\n1. confirm the deletion.\n\nreassign users before deletion\n\nif users are assigned to this role, you must first reassign them to a different role before deleting it.\n\n## permission scopes reference\n\ncustom roles use permission scopes to define what users can do within a project. here are the available scopes by resource:\n\n### workflow scopes\n\n- `workflow:create` - create new workflows\n- `workflow:read` - view workflow details\n- `workflow:update` - edit workflows\n- `workflow:publish` - publish workflows\n- `workflow:unpublish` - unpublish workflows\n- `workflow:delete` - delete workflows\n- `workflow:list` - view workflows in project\n- `workflow:execute-chat` - execute workflows via chat interface\n- `workflow:move` - move workflows between projects\n- `workflow:share` - share workflows with other users\n- `workflow:updateredactionsetting` - manage the data redaction policy for workflows\n\n### execution scopes\n\n- `execution:reveal` - reveal redacted execution data (refer to [execution data redaction](../../../workflows/executions/execution-data-redaction/))\n\n### credential scopes\n\n- `credential:create` - create new credentials\n- `credential:read` - view credential details\n- `credential:update` - edit credentials\n- `credential:delete` - delete credentials\n- `credential:list` - view credentials in project\n- `credential:move` - move credentials between projects\n- `credential:share` - share credentials with other users\n\n### project scopes\n\n- `project:list` - view available projects\n- `project:read` - view project details\n- `project:update` - edit project settings (admin only)\n- `project:delete` - delete projects (admin only)\n\n### folder scopes\n\n- `folder:create` - create new folders\n- `folder:read` - view folder contents\n- `folder:update` - rename folders\n- `folder:delete` - delete folders\n- `folder:list` - view folders in project\n- `folder:move` - move folders\n\n### data table scopes\n\n- `datatable:create` - create new data tables\n- `datatable:read` - view data table schema\n- `datatable:update` - modify data table schema\n- `datatable:delete` - delete data tables\n- `datatable:listproject` - view data tables in project\n- `datatable:readrow` - read rows from data tables\n- `datatable:writerow` - insert or update rows in data tables\n\n### project variable scopes\n\n- `projectvariable:list` - view project variables\n- `projectvariable:read` - view variable values\n- `projectvariable:create` - create new variables\n- `projectvariable:update` - edit variable values\n- `projectvariable:delete` - delete variables\n\n### secret vault scopes\n\n- `secretsvaults:view` - view secret vaults in a project\n- `secretsvaults:create` - create new secret vaults within project\n- `secretsvaults:edit` - edit secret vault configuration\n- `secretsvaults:delete` - delete secret vaults of a project\n- `secretsvaults:sync` - reload a vault's secrets\n- `secrets:list` - use secrets in credentials\n\n### source control scopes\n\n- `sourcecontrol:push` - push changes to source control\n\n## common custom role examples\n\nthese are example custom project roles you can create for common use cases. remember that these roles apply within individual projects, not across your entire n8n instance.\n\n### workflow developer\n\na role for users who work only with workflows: * `workflow:create`, `workflow:read`, `workflow:update`, `workflow:delete`, `workflow:list` * `credential:read`, `credential:list` (view credentials but not modify) * `project:list`, `project:read`\n\n### credential manager\n\na role for users who manage credentials: * `credential:create`, `credential:read`, `credential:update`, `credential:delete`, `credential:list`, `credential:share` * `workflow:read`, `workflow:list` (view workflows to understand credential usage) * `project:list`, `project:read`\n\n### secrets user\n\na role for users who need to use external secrets in credentials but not manage vaults: * `secrets:list` (use secrets in credentials expressions) * `credential:create`, `credential:read`, `credential:update`, `credential:list` (manage credentials with secrets) * `workflow:read`, `workflow:list` * `project:list`, `project:read`\n\n### workflow publisher\n\na role for users who can publish workflows without full edit access: * `workflow:read`, `workflow:list`, `workflow:publish`, `workflow:unpublish` * `credential:read`, `credential:list` * `project:list`, `project:read`\n\ncombining scopes\n\nyou can combine any scopes to create roles that match your specific needs. consider the principle of least privilege: grant only the permissions users need to perform their tasks.\n custom project roles",
+        "fullText": "custom roles # custom project roles\n\nfeature availability\n\ncustom roles are available on self-hosted enterprise and cloud enterprise plans. refer to n8n's [pricing page](https://n8n.io/pricing/) for plan details.\n\n**available from:** n8n version 1.122.0 (released november 24, 2025)\n\nsecret vault scopes are available from n8n version `2.13.0`\n\ninstance roles vs project roles\n\nn8n has two types of roles: * **instance roles** ([account types](../../account-types/)): owner, admin, and member roles that span the entire n8n instance and all projects * **project roles**: roles that apply within a specific project (admin, editor, viewer, and custom roles)\n\ncustom roles are project-level roles. they define permissions within individual projects, not across the entire instance.\n\ncustom project roles allow you to create roles with specific permissions tailored to your team's needs. unlike the built-in project roles (admin, editor, viewer), custom roles let you define granular access to workflows, credentials, and other project resources.\n\n## create a custom role\n\ninstance owners and instance admins can create custom roles.\n\nto create a custom role:\n\n1. go to **settings** > **project roles**.\n1. select **create role**.\n1. enter a role name and optional description.\n1. select the permissions (scopes) for this role:\n   - **workflow permissions**: create, read, update, publish, delete, list, execute, move, or share workflows\n   - **credential permissions**: create, read, update, delete, list, move, or share credentials\n   - **project permissions**: list, read, update, or delete projects\n   - **folder permissions**: create, read, update, delete, list, or move folders\n   - **data table permissions**: create, read, update, delete, list project tables, read/write rows\n   - **project variable permissions**: create, read, update, delete, or list project variables\n   - **secret vault permissions**: create, view, update, delete, and sync (reload) vaults of a project\n   - **secrets permission**: use secrets in credentials\n   - **source control**: push to source control\n1. select **create role**.\n\n## assign a custom role to users\n\nproject admins can assign custom roles to project members. custom roles apply only within the specific project where they're assigned. a user can have different roles in different projects.\n\nto assign a custom role:\n\n1. select the project.\n1. select **project settings**.\n1. under **project members**, browse or search for users.\n1. select the user and choose the custom role from the dropdown.\n1. select **save**.\n\nproject-level permissions\n\ncustom role permissions only apply within the project where the role is assigned. to grant the same permissions across multiple projects, assign the custom role in each project individually.\n\n## edit a custom role\n\nto modify an existing custom role:\n\n1. go to **settings** > **project roles**.\n1. find the custom role you want to edit.\n1. select the **three-dot menu** > **edit**.\n1. update the role name, description, or permissions.\n1. select **save changes**.\n\nediting affects all assigned users\n\nchanges to a custom role immediately affect all users assigned to that role in any project. if the role is used across multiple projects, the permission changes apply everywhere the role is assigned.\n\n## duplicate a custom role\n\nto create a new role based on an existing one:\n\n1. go to **settings** > **project roles**.\n1. find the role you want to duplicate.\n1. select the **three-dot menu** > **duplicate**.\n1. modify the role name and permissions as needed.\n1. select **create role**.\n\n## delete a custom role\n\nto delete a custom role:\n\n1. go to **settings** > **project roles**.\n1. find the role you want to delete.\n1. select the **three-dot menu** > **delete**.\n1. confirm the deletion.\n\nreassign users before deletion\n\nif users are assigned to this role, you must first reassign them to a different role before deleting it.\n\n## permission scopes reference\n\ncustom roles use permission scopes to define what users can do within a project. here are the available scopes by resource:\n\n### workflow scopes\n\n- `workflow:create` - create new workflows\n- `workflow:read` - view workflow details\n- `workflow:update` - edit workflows\n- `workflow:publish` - publish workflows\n- `workflow:unpublish` - unpublish workflows\n- `workflow:delete` - delete workflows\n- `workflow:list` - view workflows in project\n- `workflow:execute-chat` - execute workflows via chat interface\n- `workflow:move` - move workflows between projects\n- `workflow:share` - share workflows with other users\n\n### credential scopes\n\n- `credential:create` - create new credentials\n- `credential:read` - view credential details\n- `credential:update` - edit credentials\n- `credential:delete` - delete credentials\n- `credential:list` - view credentials in project\n- `credential:move` - move credentials between projects\n- `credential:share` - share credentials with other users\n\n### project scopes\n\n- `project:list` - view available projects\n- `project:read` - view project details\n- `project:update` - edit project settings (admin only)\n- `project:delete` - delete projects (admin only)\n\n### folder scopes\n\n- `folder:create` - create new folders\n- `folder:read` - view folder contents\n- `folder:update` - rename folders\n- `folder:delete` - delete folders\n- `folder:list` - view folders in project\n- `folder:move` - move folders\n\n### data table scopes\n\n- `datatable:create` - create new data tables\n- `datatable:read` - view data table schema\n- `datatable:update` - modify data table schema\n- `datatable:delete` - delete data tables\n- `datatable:listproject` - view data tables in project\n- `datatable:readrow` - read rows from data tables\n- `datatable:writerow` - insert or update rows in data tables\n\n### project variable scopes\n\n- `projectvariable:list` - view project variables\n- `projectvariable:read` - view variable values\n- `projectvariable:create` - create new variables\n- `projectvariable:update` - edit variable values\n- `projectvariable:delete` - delete variables\n\n### secret vault scopes\n\n- `secretsvaults:view` - view secret vaults in a project\n- `secretsvaults:create` - create new secret vaults within project\n- `secretsvaults:edit` - edit secret vault configuration\n- `secretsvaults:delete` - delete secret vaults of a project\n- `secretsvaults:sync` - reload a vault's secrets\n- `secrets:list` - use secrets in credentials\n\n### source control scopes\n\n- `sourcecontrol:push` - push changes to source control\n\n## common custom role examples\n\nthese are example custom project roles you can create for common use cases. remember that these roles apply within individual projects, not across your entire n8n instance.\n\n### workflow developer\n\na role for users who work only with workflows: * `workflow:create`, `workflow:read`, `workflow:update`, `workflow:delete`, `workflow:list` * `credential:read`, `credential:list` (view credentials but not modify) * `project:list`, `project:read`\n\n### credential manager\n\na role for users who manage credentials: * `credential:create`, `credential:read`, `credential:update`, `credential:delete`, `credential:list`, `credential:share` * `workflow:read`, `workflow:list` (view workflows to understand credential usage) * `project:list`, `project:read`\n\n### secrets user\n\na role for users who need to use external secrets in credentials but not manage vaults: * `secrets:list` (use secrets in credentials expressions) * `credential:create`, `credential:read`, `credential:update`, `credential:list` (manage credentials with secrets) * `workflow:read`, `workflow:list` * `project:list`, `project:read`\n\n### workflow publisher\n\na role for users who can publish workflows without full edit access: * `workflow:read`, `workflow:list`, `workflow:publish`, `workflow:unpublish` * `credential:read`, `credential:list` * `project:list`, `project:read`\n\ncombining scopes\n\nyou can combine any scopes to create roles that match your specific needs. consider the principle of least privilege: grant only the permissions users need to perform their tasks.\n custom project roles",
         "importantTerms": [
           "project",
           "role",
           "create",
           "roles",
-          "workflow",
           "custom",
+          "workflow",
           "delete",
           "read",
           "credential",
           "list",
           "update",
           "view",
-          "scopes",
           "permissions",
-          "workflows",
+          "scopes",
           "credentials",
+          "workflows",
           "users",
-          "data",
           "select",
           "projects",
           "secrets",
           "edit",
           "move",
           "folder",
+          "data",
           "secret",
           "instance",
           "within",
@@ -90277,14 +90274,14 @@
           "with",
           "publish",
           "vaults",
-          "execution",
           "projectvariable",
           "secretsvaults",
           "details",
           "from",
           "specific",
           "across",
-          "table"
+          "table",
+          "variable"
         ]
       }
     },
@@ -91203,7 +91200,7 @@
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Workflow settings\n\nYou can customize workflow behavior for individual workflows using workflow settings.\n\n## Access workflow settings\n\nTo open the settings:\n\n1. Open your workflow.\n1. Select the **three dots icon** in the upper-right corner.\n1. Select **Settings**. n8n opens the **Workflow settings** modal.\n\n## Available settings\n\nThe following settings are available:\n\n### Execution order\n\nChoose the execution order for multi-branch workflows:\n\n**v1 (recommended)** executes each branch in turn, completing one branch before starting another. n8n orders the branches based on their position on the [canvas](../../glossary/#canvas-n8n), from topmost to bottommost. If two branches are at the same height, the leftmost branch executes first.\n\n**v0 (legacy)** executes the first node of each branch, then the second node of each branch, and so on.\n\n### Error Workflow (to notify when this one errors)\n\nSelect a workflow to trigger if the current workflow fails. See [error workflows](../../flow-logic/error-handling/) for more details.\n\n### This workflow can be called by\n\nChoose which other workflows can call this workflow.\n\n### Timezone\n\nSets the timezone for this workflow. The timezone setting is important for the Schedule Trigger node.\n\nYou can set your n8n instance's timezone to configure the default timezone workflows use:\n\n- [Set a n8n Cloud instance timezone](../../manage-cloud/set-cloud-timezone/)\n- [Configure the timezone for self-hosted instances](../../hosting/configuration/environment-variables/timezone-localization/)\n\nIf you don't configure the workflow or instance timezone, n8n defaults to the EDT (New York) timezone.\n\n### Save failed production executions\n\nWhether n8n should save failed executions for active workflows.\n\n### Save successful production executions\n\nWhether n8n should save successful executions for active workflows.\n\n### Save manual executions\n\nWhether n8n should save executions for workflows started by the user in the editor.\n\n### Save execution progress\n\nWhether n8n should save execution data for each node.\n\nIf set to **Save**, the workflow resumes from where it stopped in case of an error. This may increase latency.\n\n### Timeout Workflow\n\nWhether n8n should cancel the current workflow execution after a certain amount of time elapses.\n\nWhen enabled, the **Timeout After** option appears. Here, you can set the time (in hours, minutes, and seconds) after which the workflow should timeout. For n8n Cloud users, n8n enforces a maximum available timeout for each plan.\n\n### Redact production execution data\n\nControls whether execution data from production (non-manually triggered) executions is redacted. When set to **Redact**, the input and output data of each node is hidden and replaced with a redacted indicator.\n\n### Redact manual execution data\n\nControls whether execution data from manually triggered executions is redacted. When set to **Redact**, the input and output data of each node is hidden and replaced with a redacted indicator.\n\nRefer to [Execution data redaction](../executions/execution-data-redaction/) for details on redaction policies, revealing data, and permission requirements.\n\n### Estimated time saved\n\nAn estimate of the number of minutes each of execution of this workflow saves you.\n\nSetting this lets n8n calculate the amount of time saved for [insights](../../insights/).\n",
+        "markdown": "# Workflow settings\n\nYou can customize workflow behavior for individual workflows using workflow settings.\n\n## Access workflow settings\n\nTo open the settings:\n\n1. Open your workflow.\n1. Select the **three dots icon** in the upper-right corner.\n1. Select **Settings**. n8n opens the **Workflow settings** modal.\n\n## Available settings\n\nThe following settings are available:\n\n### Execution order\n\nChoose the execution order for multi-branch workflows:\n\n**v1 (recommended)** executes each branch in turn, completing one branch before starting another. n8n orders the branches based on their position on the [canvas](../../glossary/#canvas-n8n), from topmost to bottommost. If two branches are at the same height, the leftmost branch executes first.\n\n**v0 (legacy)** executes the first node of each branch, then the second node of each branch, and so on.\n\n### Error Workflow (to notify when this one errors)\n\nSelect a workflow to trigger if the current workflow fails. See [error workflows](../../flow-logic/error-handling/) for more details.\n\n### This workflow can be called by\n\nChoose which other workflows can call this workflow.\n\n### Timezone\n\nSets the timezone for this workflow. The timezone setting is important for the Schedule Trigger node.\n\nYou can set your n8n instance's timezone to configure the default timezone workflows use:\n\n- [Set a n8n Cloud instance timezone](../../manage-cloud/set-cloud-timezone/)\n- [Configure the timezone for self-hosted instances](../../hosting/configuration/environment-variables/timezone-localization/)\n\nIf you don't configure the workflow or instance timezone, n8n defaults to the EDT (New York) timezone.\n\n### Save failed production executions\n\nWhether n8n should save failed executions for active workflows.\n\n### Save successful production executions\n\nWhether n8n should save successful executions for active workflows.\n\n### Save manual executions\n\nWhether n8n should save executions for workflows started by the user in the editor.\n\n### Save execution progress\n\nWhether n8n should save execution data for each node.\n\nIf set to **Save**, the workflow resumes from where it stopped in case of an error. This may increase latency.\n\n### Timeout Workflow\n\nWhether n8n should cancel the current workflow execution after a certain amount of time elapses.\n\nWhen enabled, the **Timeout After** option appears. Here, you can set the time (in hours, minutes, and seconds) after which the workflow should timeout. For n8n Cloud users, n8n enforces a maximum available timeout for each plan.\n\n### Estimated time saved\n\nAn estimate of the number of minutes each of execution of this workflow saves you.\n\nSetting this lets n8n calculate the amount of time saved for [insights](../../insights/).\n",
         "excerpt": "# Workflow settings  You can customize workflow behavior for individual workflows using workflow settings.  ## Access workflow settings  To open the settings:  1. Open your workflow. 1. Select the **three dots icon** in the upper-right corner. 1. Select **Settings**. n8n opens the **Workflow settings** modal.  ## Available settings  The following settings are available:  ### Execution order  Choose the execution order for multi-branch workflows:  **v1 (recommended)** executes each branch in turn...",
         "sections": [
           {
@@ -91236,8 +91233,6 @@
           "manual",
           "progress",
           "timeout",
-          "redact",
-          "data",
           "estimated",
           "time",
           "saved"
@@ -91246,43 +91241,36 @@
         "operations": [],
         "codeExamples": 0,
         "complexity": "beginner",
-        "readingTime": "3 min",
-        "contentLength": 3359,
+        "readingTime": "2 min",
+        "contentLength": 2724,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "settings # workflow settings\n\nyou can customize workflow behavior for individual workflows using workflow settings.\n\n## access workflow settings\n\nto open the settings:\n\n1. open your workflow.\n1. select the **three dots icon** in the upper-right corner.\n1. select **settings**. n8n opens the **workflow settings** modal.\n\n## available settings\n\nthe following settings are available:\n\n### execution order\n\nchoose the execution order for multi-branch workflows:\n\n**v1 (recommended)** executes each branch in turn, completing one branch before starting another. n8n orders the branches based on their position on the [canvas](../../glossary/#canvas-n8n), from topmost to bottommost. if two branches are at the same height, the leftmost branch executes first.\n\n**v0 (legacy)** executes the first node of each branch, then the second node of each branch, and so on.\n\n### error workflow (to notify when this one errors)\n\nselect a workflow to trigger if the current workflow fails. see [error workflows](../../flow-logic/error-handling/) for more details.\n\n### this workflow can be called by\n\nchoose which other workflows can call this workflow.\n\n### timezone\n\nsets the timezone for this workflow. the timezone setting is important for the schedule trigger node.\n\nyou can set your n8n instance's timezone to configure the default timezone workflows use:\n\n- [set a n8n cloud instance timezone](../../manage-cloud/set-cloud-timezone/)\n- [configure the timezone for self-hosted instances](../../hosting/configuration/environment-variables/timezone-localization/)\n\nif you don't configure the workflow or instance timezone, n8n defaults to the edt (new york) timezone.\n\n### save failed production executions\n\nwhether n8n should save failed executions for active workflows.\n\n### save successful production executions\n\nwhether n8n should save successful executions for active workflows.\n\n### save manual executions\n\nwhether n8n should save executions for workflows started by the user in the editor.\n\n### save execution progress\n\nwhether n8n should save execution data for each node.\n\nif set to **save**, the workflow resumes from where it stopped in case of an error. this may increase latency.\n\n### timeout workflow\n\nwhether n8n should cancel the current workflow execution after a certain amount of time elapses.\n\nwhen enabled, the **timeout after** option appears. here, you can set the time (in hours, minutes, and seconds) after which the workflow should timeout. for n8n cloud users, n8n enforces a maximum available timeout for each plan.\n\n### redact production execution data\n\ncontrols whether execution data from production (non-manually triggered) executions is redacted. when set to **redact**, the input and output data of each node is hidden and replaced with a redacted indicator.\n\n### redact manual execution data\n\ncontrols whether execution data from manually triggered executions is redacted. when set to **redact**, the input and output data of each node is hidden and replaced with a redacted indicator.\n\nrefer to [execution data redaction](../executions/execution-data-redaction/) for details on redaction policies, revealing data, and permission requirements.\n\n### estimated time saved\n\nan estimate of the number of minutes each of execution of this workflow saves you.\n\nsetting this lets n8n calculate the amount of time saved for [insights](../../insights/).\n workflow settings",
+        "fullText": "settings # workflow settings\n\nyou can customize workflow behavior for individual workflows using workflow settings.\n\n## access workflow settings\n\nto open the settings:\n\n1. open your workflow.\n1. select the **three dots icon** in the upper-right corner.\n1. select **settings**. n8n opens the **workflow settings** modal.\n\n## available settings\n\nthe following settings are available:\n\n### execution order\n\nchoose the execution order for multi-branch workflows:\n\n**v1 (recommended)** executes each branch in turn, completing one branch before starting another. n8n orders the branches based on their position on the [canvas](../../glossary/#canvas-n8n), from topmost to bottommost. if two branches are at the same height, the leftmost branch executes first.\n\n**v0 (legacy)** executes the first node of each branch, then the second node of each branch, and so on.\n\n### error workflow (to notify when this one errors)\n\nselect a workflow to trigger if the current workflow fails. see [error workflows](../../flow-logic/error-handling/) for more details.\n\n### this workflow can be called by\n\nchoose which other workflows can call this workflow.\n\n### timezone\n\nsets the timezone for this workflow. the timezone setting is important for the schedule trigger node.\n\nyou can set your n8n instance's timezone to configure the default timezone workflows use:\n\n- [set a n8n cloud instance timezone](../../manage-cloud/set-cloud-timezone/)\n- [configure the timezone for self-hosted instances](../../hosting/configuration/environment-variables/timezone-localization/)\n\nif you don't configure the workflow or instance timezone, n8n defaults to the edt (new york) timezone.\n\n### save failed production executions\n\nwhether n8n should save failed executions for active workflows.\n\n### save successful production executions\n\nwhether n8n should save successful executions for active workflows.\n\n### save manual executions\n\nwhether n8n should save executions for workflows started by the user in the editor.\n\n### save execution progress\n\nwhether n8n should save execution data for each node.\n\nif set to **save**, the workflow resumes from where it stopped in case of an error. this may increase latency.\n\n### timeout workflow\n\nwhether n8n should cancel the current workflow execution after a certain amount of time elapses.\n\nwhen enabled, the **timeout after** option appears. here, you can set the time (in hours, minutes, and seconds) after which the workflow should timeout. for n8n cloud users, n8n enforces a maximum available timeout for each plan.\n\n### estimated time saved\n\nan estimate of the number of minutes each of execution of this workflow saves you.\n\nsetting this lets n8n calculate the amount of time saved for [insights](../../insights/).\n workflow settings",
         "importantTerms": [
           "workflow",
-          "execution",
           "timezone",
           "settings",
-          "data",
           "save",
-          "executions",
           "workflows",
-          "each",
           "this",
-          "whether",
+          "execution",
           "branch",
-          "node",
+          "each",
+          "executions",
           "should",
-          "from",
+          "whether",
+          "node",
           "error",
-          "when",
           "cloud",
-          "production",
           "timeout",
           "time",
-          "redact",
-          "redacted",
           "select",
           "available",
           "executes",
           "instance",
           "configure",
-          "after",
-          "redaction"
+          "after"
         ]
       }
     },
@@ -91962,7 +91950,7 @@
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Executions\n\nAn execution is a single run of a workflow.\n\n## Execution modes\n\nThere are two execution modes:\n\n- Manual: run workflows manually when testing. Select **Execute Workflow** to start a manual execution. You can do manual executions of active workflows, but n8n recommends keeping your workflow set to **Inactive** while developing and testing.\n- Production: a production workflow is one that runs automatically. To enable this, set the workflow to **Active**.\n\n## How executions count towards quotas:\n\n[Paid plans](https://n8n.io/pricing/), whether cloud or self-hosted, have an execution limit quota. Only production executions count towards this quota. These are executions started automatically by triggers, schedules, or polling. Manual executions aren't counted. This distinction applies regardless of the instance environment, such as development or production.\n\n## Execution lists\n\nn8n provides two execution lists:\n\n- [Workflow-level executions](single-workflow-executions/): this execution list shows the executions for a single workflow.\n- [All executions](all-executions/): this list shows all executions for all your workflows.\n\nn8n supports [adding custom data to executions](custom-executions-data/).\n\n## Execution data redaction\n\nYou can redact execution data to protect sensitive information. Redaction hides the input and output data of workflow executions while preserving execution metadata like status, timing, and node names. Refer to [Execution data redaction](execution-data-redaction/) for details.\n",
+        "markdown": "# Executions\n\nAn execution is a single run of a workflow.\n\n## Execution modes\n\nThere are two execution modes:\n\n- Manual: run workflows manually when testing. Select **Execute Workflow** to start a manual execution. You can do manual executions of active workflows, but n8n recommends keeping your workflow set to **Inactive** while developing and testing.\n- Production: a production workflow is one that runs automatically. To enable this, set the workflow to **Active**.\n\n## How executions count towards quotas:\n\n[Paid plans](https://n8n.io/pricing/), whether cloud or self-hosted, have an execution limit quota. Only production executions count towards this quota. These are executions started automatically by triggers, schedules, or polling. Manual executions aren't counted. This distinction applies regardless of the instance environment, such as development or production.\n\n## Execution lists\n\nn8n provides two execution lists:\n\n- [Workflow-level executions](single-workflow-executions/): this execution list shows the executions for a single workflow.\n- [All executions](all-executions/): this list shows all executions for all your workflows.\n\nn8n supports [adding custom data to executions](custom-executions-data/).\n",
         "excerpt": "# Executions  An execution is a single run of a workflow.  ## Execution modes  There are two execution modes:  - Manual: run workflows manually when testing. Select **Execute Workflow** to start a manual execution. You can do manual executions of active workflows, but n8n recommends keeping your workflow set to **Inactive** while developing and testing. - Production: a production workflow is one that runs automatically. To enable this, set the workflow to **Active**.  ## How executions count tow...",
         "sections": [
           {
@@ -91980,31 +91968,25 @@
           "count",
           "towards",
           "quotas:",
-          "lists",
-          "data",
-          "redaction"
+          "lists"
         ],
         "useCases": [],
-        "operations": [
-          "execution data red"
-        ],
+        "operations": [],
         "codeExamples": 0,
         "complexity": "beginner",
-        "readingTime": "2 min",
-        "contentLength": 1535,
+        "readingTime": "1 min",
+        "contentLength": 1227,
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "executions # executions\n\nan execution is a single run of a workflow.\n\n## execution modes\n\nthere are two execution modes:\n\n- manual: run workflows manually when testing. select **execute workflow** to start a manual execution. you can do manual executions of active workflows, but n8n recommends keeping your workflow set to **inactive** while developing and testing.\n- production: a production workflow is one that runs automatically. to enable this, set the workflow to **active**.\n\n## how executions count towards quotas:\n\n[paid plans](https://n8n.io/pricing/), whether cloud or self-hosted, have an execution limit quota. only production executions count towards this quota. these are executions started automatically by triggers, schedules, or polling. manual executions aren't counted. this distinction applies regardless of the instance environment, such as development or production.\n\n## execution lists\n\nn8n provides two execution lists:\n\n- [workflow-level executions](single-workflow-executions/): this execution list shows the executions for a single workflow.\n- [all executions](all-executions/): this list shows all executions for all your workflows.\n\nn8n supports [adding custom data to executions](custom-executions-data/).\n\n## execution data redaction\n\nyou can redact execution data to protect sensitive information. redaction hides the input and output data of workflow executions while preserving execution metadata like status, timing, and node names. refer to [execution data redaction](execution-data-redaction/) for details.\n executions",
+        "fullText": "executions # executions\n\nan execution is a single run of a workflow.\n\n## execution modes\n\nthere are two execution modes:\n\n- manual: run workflows manually when testing. select **execute workflow** to start a manual execution. you can do manual executions of active workflows, but n8n recommends keeping your workflow set to **inactive** while developing and testing.\n- production: a production workflow is one that runs automatically. to enable this, set the workflow to **active**.\n\n## how executions count towards quotas:\n\n[paid plans](https://n8n.io/pricing/), whether cloud or self-hosted, have an execution limit quota. only production executions count towards this quota. these are executions started automatically by triggers, schedules, or polling. manual executions aren't counted. this distinction applies regardless of the instance environment, such as development or production.\n\n## execution lists\n\nn8n provides two execution lists:\n\n- [workflow-level executions](single-workflow-executions/): this execution list shows the executions for a single workflow.\n- [all executions](all-executions/): this list shows all executions for all your workflows.\n\nn8n supports [adding custom data to executions](custom-executions-data/).\n executions",
         "importantTerms": [
           "executions",
           "execution",
           "workflow",
-          "data",
           "this",
           "manual",
           "production",
-          "redaction",
           "single",
           "workflows"
         ]
@@ -92286,128 +92268,6 @@
     },
     {
       "id": "page-1261",
-      "title": "Redact execution data",
-      "url": "https://docs.n8n.io/workflows/executions/execution-data-redaction/index.md",
-      "urlPath": "workflows/executions/execution-data-redaction/index.md",
-      "category": "workflows",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Execution data redaction\n\nExecution data redaction lets you hide the input and output data of workflow executions. This helps protect sensitive information like personal data, authentication tokens, and financial records from being visible to users who can view the workflow but don't need to see the underlying data.\n\nWhen redaction is enabled, execution metadata (status, timing, node names) remains visible, but the actual data payload processed by each node is replaced with a redacted indicator.\n\n## Why use execution data redaction\n\nWorkflows often process data that the workflow builder or viewers should not have access to outside of n8n. Common scenarios include:\n\n- **Dynamic credentials**: End users authenticate through workflows, and their data flows through execution logs that the builder can freely view.\n- **PII and compliance**: Workflows handling customer personal data (emails, addresses, financial records) need to comply with GDPR, SOC 2, or internal security standards.\n- **Cross-department workflows**: A workflow built by one team processes sensitive data from another team that the builder would not normally have access to.\n- **Least privilege principle**: Limiting data visibility to only those who need it, rather than everyone with workflow view access.\n\nPreviously, the only option was to disable execution history entirely at the workflow level, which removed all visibility into workflow success or failure status. Execution data redaction preserves execution monitoring while hiding the sensitive data payload.\n\n## Configure redaction settings\n\nRedaction is configured per workflow in the workflow settings. You need the **Manage data redaction** (`workflow:updateRedactionSetting`) scope to change these settings.\n\nTo configure redaction:\n\n1. Open your workflow.\n1. Select the **three dots icon** in the upper-right corner.\n1. Select **Settings**.\n1. Find the **Redact production execution data** and **Redact manual execution data** settings.\n1. For each setting, choose either **Default - Do not redact** or **Redact**.\n1. Select **Save**.\n\n### Redaction settings explained\n\nThere are two independent toggles that control redaction:\n\n| Setting                              | What it controls                                                                                                                                                                                        |\n| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **Redact production execution data** | Controls whether data from production (non-manually triggered) executions is redacted. Production executions are those triggered by webhooks, schedules, or other triggers when the workflow is active. |\n| **Redact manual execution data**     | Controls whether data from manually triggered executions is redacted. Manual executions are those started by selecting **Execute Workflow** in the editor.                                              |\n\nThese two toggles combine into a single `redactionPolicy` stored on the workflow:\n\n| Production    | Manual        | Resulting policy                                       |\n| ------------- | ------------- | ------------------------------------------------------ |\n| Do not redact | Do not redact | `none` - No redaction applied to any executions        |\n| Redact        | Do not redact | `non-manual` - Only production executions are redacted |\n| Do not redact | Redact        | `manual-only` - Only manual executions are redacted    |\n| Redact        | Redact        | `all` - All executions are redacted                    |\n\n### Dynamic credentials\n\nWorkflows that use dynamic credentials always have their production execution data redacted, regardless of the redaction setting. This is because dynamic credential executions process data on behalf of end users, and the workflow builder should not be able to view that data.\n\nWhen a workflow uses dynamic credentials, the **Redact production execution data** setting is locked to **Redact** and cannot be changed.\n\n## What redacted data looks like\n\nWhen an execution is redacted:\n\n- All input and output data for each node is replaced with an empty object.\n- Binary data (files, images) is removed.\n- Error messages are redacted, preserving only the error type and HTTP status code (for API errors) to aid in troubleshooting.\n- The execution viewer displays a **\"Data redacted\"** indicator with a shredder icon instead of the usual data tables.\n- Execution metadata remains visible: node names, execution status (success/failure), timing information, and the workflow structure.\n\nError information\n\nWhen execution data is redacted, error details are also redacted to prevent sensitive information from leaking through error messages. Only the error type (for example, `NodeApiError`) and HTTP status code are preserved. This provides enough information to identify the category of failure without exposing data.\n\n## Reveal redacted data\n\nUsers with the **Reveal execution data** (`execution:reveal`) scope can temporarily view redacted execution data for a specific execution. Instance owners and admins have this scope by default.\n\nTo reveal data:\n\n1. Open the execution in the execution viewer.\n1. Select the **Reveal data** button displayed in the redacted data area.\n1. Review the confirmation dialog. It explains that:\n   - The action will be logged in the audit trail.\n   - You should only reveal data if you have a legitimate reason.\n   - Unnecessary access may violate your organization's policy.\n1. Select **Reveal data** to confirm.\n\nThe execution data becomes visible for that execution in the current session.\n\nDynamic credential executions can't be revealed\n\nExecutions that used dynamic credentials can't be revealed, even by users with the `execution:reveal` scope. This is a security measure to protect end-user data that flows through workflows using dynamic credential resolution.\n\n### Audit logging\n\nAll reveal actions are tracked through [log streaming](../../../log-streaming/). Two audit events are available:\n\n| Event                             | Description                                                                                                                                                                |\n| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `execution.data.revealed`         | Emitted when a user successfully reveals redacted execution data. Includes the user, execution ID, workflow ID, timestamp, IP address, and the redaction policy in effect. |\n| `execution.data.revealed_failure` | Emitted when a reveal attempt is denied (for example, due to insufficient permissions). Includes the same fields plus the rejection reason.                                |\n\nThese events integrate with your existing log streaming destinations (syslog, webhooks, Sentry) and can be used for compliance reporting and access auditing.\n\nFail-closed behavior\n\nIf the audit system is unavailable when a reveal is attempted, the reveal is denied and a `503 Service Unavailable` error is returned. This fail-closed behavior ensures that all data access is auditable.\n\n## Permission scopes\n\nExecution data redaction introduces two permission scopes that can be assigned through [custom project roles](../../../user-management/rbac/custom-roles/):\n\n| Scope                             | Purpose                                                                                                                          |\n| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |\n| `workflow:updateRedactionSetting` | Allows modifying the redaction policy in workflow settings. Displayed as **Manage data redaction** in the role configuration UI. |\n| `execution:reveal`                | Allows revealing redacted execution data. Instance owners and admins have this scope by default.                                 |\n\nApply the principle of least privilege when assigning these scopes:\n\n- Grant `workflow:updateRedactionSetting` to project admins or security leads who define data access policies.\n- Grant `execution:reveal` sparingly, typically to a small set of trusted users who may need to troubleshoot production issues involving sensitive data.\n\n## Best practices\n\n### Choosing the right redaction policy\n\n| Scenario                                                                                   | Recommended setting                              |\n| ------------------------------------------------------------------------------------------ | ------------------------------------------------ |\n| Workflows processing PII, financial data, or authentication tokens in production           | Redact production execution data                 |\n| Workflows where even test data is sensitive (for example, using copies of production data) | Redact both production and manual execution data |\n| Workflows processing non-sensitive data, or during initial development                     | No redaction                                     |\n| Workflows using dynamic credentials                                                        | Production data is always redacted automatically |\n\n### General recommendations\n\n- **Start with production redaction**: For most workflows handling sensitive data, redacting production executions while keeping manual executions visible provides a good balance between security and debuggability.\n- **Redact manual data when needed**: If your test environment uses real or production-like data, enable manual execution redaction as well.\n- **Use log streaming**: Enable [log streaming](../../../log-streaming/) to capture reveal audit events. This provides an audit trail for compliance and allows you to monitor who is accessing sensitive execution data.\n- **Limit reveal access**: Only grant the `execution:reveal` scope to users who have a legitimate need to view sensitive data in production executions.\n- **Review redaction settings during workflow reviews**: Include redaction policy as part of your workflow review or approval process, especially for workflows that handle cross-department or customer-facing data.\n\n## Security considerations\n\n- Redaction is applied at the API level. Redacted data is not sent to the browser.\n- Nodes can declare specific output fields as sensitive (using `sensitiveOutputFields` in the node type definition). These fields are always redacted and cannot be revealed, even by users with the `execution:reveal` scope.\n- The fail-closed audit design ensures that if logging infrastructure is down, data cannot be silently revealed without a record.\n- Redaction settings are stored as part of the workflow configuration and can be managed through [source control](../../../source-control-environments/).\n",
-        "excerpt": "# Execution data redaction  Execution data redaction lets you hide the input and output data of workflow executions. This helps protect sensitive information like personal data, authentication tokens, and financial records from being visible to users who can view the workflow but don't need to see the underlying data.  When redaction is enabled, execution metadata (status, timing, node names) remains visible, but the actual data payload processed by each node is replaced with a redacted indicato...",
-        "sections": [
-          {
-            "title": "Execution data redaction",
-            "level": 1,
-            "content": "Execution data redaction lets you hide the input and output data of workflow executions. This helps protect sensitive information like personal data, authentication tokens, and financial records from being visible to users who can view the workflow but don't need to see the underlying data.\n\nWhen redaction is enabled, execution metadata (status, timing, node names) remains visible, but the actual data payload processed by each node is replaced with a redacted indicator."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "redact",
-          "execution",
-          "data",
-          "redaction",
-          "configure",
-          "settings",
-          "explained",
-          "dynamic",
-          "credentials",
-          "what",
-          "redacted",
-          "looks",
-          "like",
-          "reveal",
-          "audit",
-          "logging",
-          "permission",
-          "scopes",
-          "best",
-          "practices",
-          "choosing",
-          "right",
-          "policy",
-          "general",
-          "recommendations",
-          "security",
-          "considerations"
-        ],
-        "useCases": [],
-        "operations": [
-          "1. open your workflow.",
-          "setting",
-          "what it controls",
-          "why use execution data red",
-          "configure red settings",
-          "red settings explained",
-          "choosing the right red policy"
-        ],
-        "codeExamples": 0,
-        "complexity": "intermediate",
-        "readingTime": "7 min",
-        "contentLength": 11181,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "redact execution data # execution data redaction\n\nexecution data redaction lets you hide the input and output data of workflow executions. this helps protect sensitive information like personal data, authentication tokens, and financial records from being visible to users who can view the workflow but don't need to see the underlying data.\n\nwhen redaction is enabled, execution metadata (status, timing, node names) remains visible, but the actual data payload processed by each node is replaced with a redacted indicator.\n\n## why use execution data redaction\n\nworkflows often process data that the workflow builder or viewers should not have access to outside of n8n. common scenarios include:\n\n- **dynamic credentials**: end users authenticate through workflows, and their data flows through execution logs that the builder can freely view.\n- **pii and compliance**: workflows handling customer personal data (emails, addresses, financial records) need to comply with gdpr, soc 2, or internal security standards.\n- **cross-department workflows**: a workflow built by one team processes sensitive data from another team that the builder would not normally have access to.\n- **least privilege principle**: limiting data visibility to only those who need it, rather than everyone with workflow view access.\n\npreviously, the only option was to disable execution history entirely at the workflow level, which removed all visibility into workflow success or failure status. execution data redaction preserves execution monitoring while hiding the sensitive data payload.\n\n## configure redaction settings\n\nredaction is configured per workflow in the workflow settings. you need the **manage data redaction** (`workflow:updateredactionsetting`) scope to change these settings.\n\nto configure redaction:\n\n1. open your workflow.\n1. select the **three dots icon** in the upper-right corner.\n1. select **settings**.\n1. find the **redact production execution data** and **redact manual execution data** settings.\n1. for each setting, choose either **default - do not redact** or **redact**.\n1. select **save**.\n\n### redaction settings explained\n\nthere are two independent toggles that control redaction:\n\n| setting                              | what it controls                                                                                                                                                                                        |\n| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **redact production execution data** | controls whether data from production (non-manually triggered) executions is redacted. production executions are those triggered by webhooks, schedules, or other triggers when the workflow is active. |\n| **redact manual execution data**     | controls whether data from manually triggered executions is redacted. manual executions are those started by selecting **execute workflow** in the editor.                                              |\n\nthese two toggles combine into a single `redactionpolicy` stored on the workflow:\n\n| production    | manual        | resulting policy                                       |\n| ------------- | ------------- | ------------------------------------------------------ |\n| do not redact | do not redact | `none` - no redaction applied to any executions        |\n| redact        | do not redact | `non-manual` - only production executions are redacted |\n| do not redact | redact        | `manual-only` - only manual executions are redacted    |\n| redact        | redact        | `all` - all executions are redacted                    |\n\n### dynamic credentials\n\nworkflows that use dynamic credentials always have their production execution data redacted, regardless of the redaction setting. this is because dynamic credential executions process data on behalf of end users, and the workflow builder should not be able to view that data.\n\nwhen a workflow uses dynamic credentials, the **redact production execution data** setting is locked to **redact** and cannot be changed.\n\n## what redacted data looks like\n\nwhen an execution is redacted:\n\n- all input and output data for each node is replaced with an empty object.\n- binary data (files, images) is removed.\n- error messages are redacted, preserving only the error type and http status code (for api errors) to aid in troubleshooting.\n- the execution viewer displays a **\"data redacted\"** indicator with a shredder icon instead of the usual data tables.\n- execution metadata remains visible: node names, execution status (success/failure), timing information, and the workflow structure.\n\nerror information\n\nwhen execution data is redacted, error details are also redacted to prevent sensitive information from leaking through error messages. only the error type (for example, `nodeapierror`) and http status code are preserved. this provides enough information to identify the category of failure without exposing data.\n\n## reveal redacted data\n\nusers with the **reveal execution data** (`execution:reveal`) scope can temporarily view redacted execution data for a specific execution. instance owners and admins have this scope by default.\n\nto reveal data:\n\n1. open the execution in the execution viewer.\n1. select the **reveal data** button displayed in the redacted data area.\n1. review the confirmation dialog. it explains that:\n   - the action will be logged in the audit trail.\n   - you should only reveal data if you have a legitimate reason.\n   - unnecessary access may violate your organization's policy.\n1. select **reveal data** to confirm.\n\nthe execution data becomes visible for that execution in the current session.\n\ndynamic credential executions can't be revealed\n\nexecutions that used dynamic credentials can't be revealed, even by users with the `execution:reveal` scope. this is a security measure to protect end-user data that flows through workflows using dynamic credential resolution.\n\n### audit logging\n\nall reveal actions are tracked through [log streaming](../../../log-streaming/). two audit events are available:\n\n| event                             | description                                                                                                                                                                |\n| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `execution.data.revealed`         | emitted when a user successfully reveals redacted execution data. includes the user, execution id, workflow id, timestamp, ip address, and the redaction policy in effect. |\n| `execution.data.revealed_failure` | emitted when a reveal attempt is denied (for example, due to insufficient permissions). includes the same fields plus the rejection reason.                                |\n\nthese events integrate with your existing log streaming destinations (syslog, webhooks, sentry) and can be used for compliance reporting and access auditing.\n\nfail-closed behavior\n\nif the audit system is unavailable when a reveal is attempted, the reveal is denied and a `503 service unavailable` error is returned. this fail-closed behavior ensures that all data access is auditable.\n\n## permission scopes\n\nexecution data redaction introduces two permission scopes that can be assigned through [custom project roles](../../../user-management/rbac/custom-roles/):\n\n| scope                             | purpose                                                                                                                          |\n| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |\n| `workflow:updateredactionsetting` | allows modifying the redaction policy in workflow settings. displayed as **manage data redaction** in the role configuration ui. |\n| `execution:reveal`                | allows revealing redacted execution data. instance owners and admins have this scope by default.                                 |\n\napply the principle of least privilege when assigning these scopes:\n\n- grant `workflow:updateredactionsetting` to project admins or security leads who define data access policies.\n- grant `execution:reveal` sparingly, typically to a small set of trusted users who may need to troubleshoot production issues involving sensitive data.\n\n## best practices\n\n### choosing the right redaction policy\n\n| scenario                                                                                   | recommended setting                              |\n| ------------------------------------------------------------------------------------------ | ------------------------------------------------ |\n| workflows processing pii, financial data, or authentication tokens in production           | redact production execution data                 |\n| workflows where even test data is sensitive (for example, using copies of production data) | redact both production and manual execution data |\n| workflows processing non-sensitive data, or during initial development                     | no redaction                                     |\n| workflows using dynamic credentials                                                        | production data is always redacted automatically |\n\n### general recommendations\n\n- **start with production redaction**: for most workflows handling sensitive data, redacting production executions while keeping manual executions visible provides a good balance between security and debuggability.\n- **redact manual data when needed**: if your test environment uses real or production-like data, enable manual execution redaction as well.\n",
-        "importantTerms": [
-          "data",
-          "execution",
-          "redaction",
-          "workflow",
-          "redacted",
-          "redact",
-          "production",
-          "reveal",
-          "executions",
-          "that",
-          "workflows",
-          "sensitive",
-          "manual",
-          "when",
-          "with",
-          "dynamic",
-          "only",
-          "settings",
-          "this",
-          "users",
-          "access",
-          "scope",
-          "have",
-          "through",
-          "error",
-          "audit",
-          "view",
-          "need",
-          "credentials",
-          "policy",
-          "streaming",
-          "information",
-          "from",
-          "visible",
-          "status",
-          "node",
-          "security",
-          "these",
-          "your",
-          "select",
-          "setting",
-          "revealed",
-          "builder",
-          "user",
-          "using",
-          "output",
-          "like",
-          "financial",
-          "each",
-          "process"
-        ]
-      }
-    },
-    {
-      "id": "page-1262",
       "title": "Manual, partial, and production executions",
       "url": "https://docs.n8n.io/workflows/executions/manual-partial-and-production-executions/index.md",
       "urlPath": "workflows/executions/manual-partial-and-production-executions/index.md",
@@ -92490,7 +92350,7 @@
       }
     },
     {
-      "id": "page-1263",
+      "id": "page-1262",
       "title": "Workflow-level executions",
       "url": "https://docs.n8n.io/workflows/executions/single-workflow-executions/index.md",
       "urlPath": "workflows/executions/single-workflow-executions/index.md",
@@ -93003,7 +92863,7 @@
         "page-0501",
         "page-0504",
         "page-0505",
-        "page-0511",
+        "page-0513",
         "page-0514",
         "page-0515",
         "page-0516",
@@ -93335,11 +93195,9 @@
         "page-1192",
         "page-1204",
         "page-1205",
-        "page-1231",
         "page-1245",
         "page-1256",
-        "page-1258",
-        "page-1261"
+        "page-1258"
       ],
       "order": [
         "page-0002",
@@ -93352,8 +93210,8 @@
       ],
       "mysql": [
         "page-0002",
+        "page-0513",
         "page-0514",
-        "page-0515",
         "page-0892"
       ],
       "mariadb": [
@@ -93378,8 +93236,8 @@
         "page-1257",
         "page-1258",
         "page-1259",
-        "page-1262",
-        "page-1263"
+        "page-1261",
+        "page-1262"
       ],
       "process": [
         "page-0002",
@@ -93454,7 +93312,7 @@
         "page-0203",
         "page-0207",
         "page-0213",
-        "page-0515",
+        "page-0514",
         "page-0522",
         "page-0632",
         "page-0636",
@@ -93531,7 +93389,7 @@
         "page-0136",
         "page-0139",
         "page-0141",
-        "page-0147",
+        "page-0146",
         "page-0148",
         "page-0151",
         "page-0153",
@@ -93574,7 +93432,7 @@
         "page-1252",
         "page-1254",
         "page-1257",
-        "page-1263"
+        "page-1262"
       ],
       "failures": [
         "page-0002"
@@ -93822,7 +93680,7 @@
         "page-0135",
         "page-0141",
         "page-0144",
-        "page-0147",
+        "page-0146",
         "page-0153",
         "page-0155",
         "page-0174",
@@ -93869,13 +93727,10 @@
         "page-1216",
         "page-1219",
         "page-1231",
-        "page-1245",
-        "page-1256",
         "page-1257",
         "page-1258",
         "page-1259",
-        "page-1260",
-        "page-1261"
+        "page-1260"
       ],
       "retention": [
         "page-0002",
@@ -93999,7 +93854,7 @@
         "page-0504",
         "page-0505",
         "page-0510",
-        "page-0511",
+        "page-0513",
         "page-0514",
         "page-0515",
         "page-0516",
@@ -94115,7 +93970,7 @@
         "page-0208",
         "page-0332",
         "page-0491",
-        "page-0515",
+        "page-0514",
         "page-0522",
         "page-0632",
         "page-0636",
@@ -94179,7 +94034,7 @@
       ],
       "waiting": [
         "page-0003",
-        "page-0146",
+        "page-0147",
         "page-0168",
         "page-0318",
         "page-0378",
@@ -94231,7 +94086,7 @@
         "page-0139",
         "page-0142",
         "page-0145",
-        "page-0147",
+        "page-0146",
         "page-0151",
         "page-0153",
         "page-0195",
@@ -94252,7 +94107,7 @@
         "page-1244",
         "page-1246",
         "page-1257",
-        "page-1263"
+        "page-1262"
       ],
       "retired": [
         "page-0003"
@@ -94287,8 +94142,7 @@
         "page-1200",
         "page-1204",
         "page-1205",
-        "page-1234",
-        "page-1261"
+        "page-1234"
       ],
       "block": [
         "page-0003",
@@ -94444,8 +94298,7 @@
         "page-0164",
         "page-0874",
         "page-1245",
-        "page-1254",
-        "page-1261"
+        "page-1254"
       ],
       "file": [
         "page-0003",
@@ -95337,8 +95190,8 @@
         "page-0368",
         "page-0369",
         "page-0370",
+        "page-0371",
         "page-0372",
-        "page-0373",
         "page-0374",
         "page-0375",
         "page-0376",
@@ -95494,7 +95347,7 @@
         "page-0021",
         "page-0042",
         "page-0083",
-        "page-0515",
+        "page-0514",
         "page-0522",
         "page-0548",
         "page-0549",
@@ -95590,7 +95443,7 @@
         "page-1192",
         "page-1204",
         "page-1245",
-        "page-1262"
+        "page-1261"
       ],
       "mount": [
         "page-0005"
@@ -95617,7 +95470,7 @@
         "page-0664",
         "page-0706",
         "page-1205",
-        "page-1263"
+        "page-1262"
       ],
       "\"secret/\"": [
         "page-0005"
@@ -95977,8 +95830,7 @@
         "page-1205",
         "page-1219",
         "page-1232",
-        "page-1246",
-        "page-1261"
+        "page-1246"
       ],
       "using": [
         "page-0005",
@@ -96010,7 +95862,7 @@
         "page-0231",
         "page-0332",
         "page-0491",
-        "page-0515",
+        "page-0514",
         "page-0521",
         "page-0522",
         "page-0531",
@@ -96461,7 +96313,7 @@
         "page-1229",
         "page-1235",
         "page-1239",
-        "page-1262"
+        "page-1261"
       ],
       "don't": [
         "page-0005",
@@ -96487,7 +96339,7 @@
         "page-1144",
         "page-1207",
         "page-1245",
-        "page-1262"
+        "page-1261"
       ],
       "glossary": [
         "page-0006"
@@ -96962,8 +96814,7 @@
         "page-0007",
         "page-0567",
         "page-0619",
-        "page-1169",
-        "page-1261"
+        "page-1169"
       ],
       "configure": [
         "page-0007",
@@ -97000,8 +96851,7 @@
         "page-1111",
         "page-1207",
         "page-1208",
-        "page-1247",
-        "page-1261"
+        "page-1247"
       ],
       "metrics": [
         "page-0007",
@@ -97134,7 +96984,7 @@
         "page-0008",
         "page-0013",
         "page-0098",
-        "page-0513",
+        "page-0512",
         "page-0711",
         "page-1205"
       ],
@@ -97292,7 +97142,7 @@
       ],
       "updated": [
         "page-0009",
-        "page-0511"
+        "page-0515"
       ],
       "license": [
         "page-0010",
@@ -97359,7 +97209,7 @@
         "page-0199",
         "page-0207",
         "page-0218",
-        "page-0515",
+        "page-0514",
         "page-0700",
         "page-0736",
         "page-0843",
@@ -97421,7 +97271,7 @@
         "page-1089",
         "page-1090",
         "page-1093",
-        "page-1095",
+        "page-1094",
         "page-1097",
         "page-1102",
         "page-1105",
@@ -97595,8 +97445,8 @@
         "page-0503",
         "page-0507",
         "page-0509",
-        "page-0513",
-        "page-0515",
+        "page-0512",
+        "page-0514",
         "page-0518",
         "page-0519",
         "page-0532",
@@ -97748,7 +97598,7 @@
         "page-0209",
         "page-0214",
         "page-0218",
-        "page-0511",
+        "page-0515",
         "page-0664",
         "page-0736",
         "page-0857",
@@ -97873,7 +97723,7 @@
       "separate": [
         "page-0013",
         "page-0155",
-        "page-0515",
+        "page-0514",
         "page-0522",
         "page-0632",
         "page-0636"
@@ -97881,8 +97731,7 @@
       "permission": [
         "page-0013",
         "page-0208",
-        "page-1231",
-        "page-1261"
+        "page-1231"
       ],
       "scope": [
         "page-0013"
@@ -98111,8 +97960,8 @@
         "page-0368",
         "page-0369",
         "page-0370",
+        "page-0371",
         "page-0372",
-        "page-0373",
         "page-0374",
         "page-0375",
         "page-0376",
@@ -98187,8 +98036,7 @@
         "page-1203",
         "page-1210",
         "page-1216",
-        "page-1235",
-        "page-1261"
+        "page-1235"
       ],
       "chat": [
         "page-0013",
@@ -98257,8 +98105,7 @@
         "page-0151",
         "page-0224",
         "page-0675",
-        "page-1204",
-        "page-1261"
+        "page-1204"
       ],
       "observability": [
         "page-0013",
@@ -98419,8 +98266,8 @@
         "page-0368",
         "page-0369",
         "page-0370",
+        "page-0371",
         "page-0372",
-        "page-0373",
         "page-0374",
         "page-0375",
         "page-0376",
@@ -98623,7 +98470,7 @@
         "page-0132",
         "page-0136",
         "page-0141",
-        "page-0147",
+        "page-0146",
         "page-0166",
         "page-0200",
         "page-0201",
@@ -98643,8 +98490,8 @@
         "page-0507",
         "page-0508",
         "page-0509",
+        "page-0511",
         "page-0512",
-        "page-0513",
         "page-0517",
         "page-0532",
         "page-0535",
@@ -98678,8 +98525,7 @@
         "page-0468"
       ],
       "policy": [
-        "page-0015",
-        "page-1261"
+        "page-0015"
       ],
       "against": [
         "page-0015"
@@ -98772,7 +98618,7 @@
         "page-0018",
         "page-0028",
         "page-0132",
-        "page-0147",
+        "page-0146",
         "page-0649",
         "page-0656",
         "page-0657",
@@ -98894,7 +98740,7 @@
         "page-0495",
         "page-0501",
         "page-0510",
-        "page-0514",
+        "page-0513",
         "page-0516",
         "page-0518",
         "page-0519",
@@ -99336,7 +99182,7 @@
         "page-1089",
         "page-1090",
         "page-1092",
-        "page-1095",
+        "page-1093",
         "page-1097",
         "page-1100",
         "page-1102",
@@ -99433,7 +99279,7 @@
         "page-0495",
         "page-0501",
         "page-0510",
-        "page-0514",
+        "page-0513",
         "page-0516",
         "page-0518",
         "page-0519",
@@ -99875,7 +99721,7 @@
         "page-1089",
         "page-1090",
         "page-1092",
-        "page-1095",
+        "page-1093",
         "page-1097",
         "page-1100",
         "page-1102",
@@ -100181,7 +100027,7 @@
         "page-0501",
         "page-0504",
         "page-0510",
-        "page-0514",
+        "page-0513",
         "page-0516",
         "page-0519",
         "page-0521",
@@ -100351,15 +100197,14 @@
         "page-0702",
         "page-1205",
         "page-1255",
-        "page-1263"
+        "page-1262"
       ],
       "considerations": [
         "page-0018",
         "page-0020",
         "page-0099",
         "page-0137",
-        "page-0546",
-        "page-1261"
+        "page-0546"
       ],
       "enabling": [
         "page-0018",
@@ -100976,7 +100821,7 @@
         "page-0501",
         "page-0504",
         "page-0510",
-        "page-0514",
+        "page-0513",
         "page-0516",
         "page-0519",
         "page-0521",
@@ -101186,7 +101031,7 @@
         "page-0510",
         "page-0511",
         "page-0512",
-        "page-0513",
+        "page-0515",
         "page-0577",
         "page-0578",
         "page-0579",
@@ -101442,8 +101287,7 @@
         "page-1166",
         "page-1171",
         "page-1199",
-        "page-1222",
-        "page-1261"
+        "page-1222"
       ],
       "practices": [
         "page-0021",
@@ -101451,8 +101295,7 @@
         "page-0736",
         "page-1171",
         "page-1199",
-        "page-1222",
-        "page-1261"
+        "page-1222"
       ],
       "chaining": [
         "page-0021"
@@ -101620,8 +101463,7 @@
       "right": [
         "page-0023",
         "page-0070",
-        "page-0085",
-        "page-1261"
+        "page-0085"
       ],
       "model?": [
         "page-0023"
@@ -101696,7 +101538,7 @@
         "page-1214",
         "page-1243",
         "page-1246",
-        "page-1263"
+        "page-1262"
       ],
       "results": [
         "page-0025",
@@ -101757,7 +101599,7 @@
         "page-0504",
         "page-0505",
         "page-0510",
-        "page-0511",
+        "page-0513",
         "page-0514",
         "page-0515",
         "page-0516",
@@ -101860,7 +101702,7 @@
       "same": [
         "page-0027",
         "page-0059",
-        "page-0515",
+        "page-0514",
         "page-0632",
         "page-0636",
         "page-1205"
@@ -101884,7 +101726,7 @@
         "page-0029",
         "page-0046",
         "page-0136",
-        "page-0147",
+        "page-0146",
         "page-0630",
         "page-0656",
         "page-0657",
@@ -101915,14 +101757,14 @@
         "page-0510",
         "page-0511",
         "page-0512",
-        "page-0513",
+        "page-0515",
         "page-1141",
         "page-1142",
         "page-1204"
       ],
       "sheet": [
         "page-0030",
-        "page-0513"
+        "page-0512"
       ],
       "fallback": [
         "page-0031"
@@ -102003,8 +101845,8 @@
       "document": [
         "page-0037",
         "page-0041",
+        "page-0511",
         "page-0512",
-        "page-0513",
         "page-0528",
         "page-0573"
       ],
@@ -102030,7 +101872,7 @@
         "page-0385",
         "page-0476",
         "page-0496",
-        "page-0514",
+        "page-0513",
         "page-0518",
         "page-0519",
         "page-0520",
@@ -102328,8 +102170,7 @@
         "page-0972",
         "page-1027",
         "page-1105",
-        "page-1231",
-        "page-1261"
+        "page-1231"
       ],
       "delete": [
         "page-0046",
@@ -102346,8 +102187,8 @@
         "page-0507",
         "page-0508",
         "page-0509",
+        "page-0511",
         "page-0512",
-        "page-0513",
         "page-0518",
         "page-0519",
         "page-0528",
@@ -102619,8 +102460,8 @@
         "page-0368",
         "page-0369",
         "page-0370",
+        "page-0371",
         "page-0372",
-        "page-0373",
         "page-0374",
         "page-0375",
         "page-0376",
@@ -103543,7 +103384,7 @@
         "page-0638",
         "page-1028",
         "page-1215",
-        "page-1263"
+        "page-1262"
       ],
       "object": [
         "page-0060",
@@ -103699,7 +103540,7 @@
       ],
       "returned": [
         "page-0066",
-        "page-0515"
+        "page-0514"
       ],
       "last": [
         "page-0066"
@@ -103758,7 +103599,7 @@
         "page-0139",
         "page-0153",
         "page-0352",
-        "page-0514",
+        "page-0513",
         "page-0519",
         "page-0524",
         "page-0557",
@@ -104091,7 +103932,7 @@
         "page-0168",
         "page-1245",
         "page-1257",
-        "page-1263"
+        "page-1262"
       ],
       "catching": [
         "page-0089"
@@ -104450,7 +104291,7 @@
         "page-1205",
         "page-1249",
         "page-1257",
-        "page-1263"
+        "page-1262"
       ],
       "visually": [
         "page-0096"
@@ -104459,7 +104300,7 @@
         "page-0096",
         "page-0112",
         "page-0113",
-        "page-0511",
+        "page-0515",
         "page-0660",
         "page-0667",
         "page-0692",
@@ -104624,7 +104465,7 @@
       ],
       "can't": [
         "page-0100",
-        "page-0515",
+        "page-0514",
         "page-0522",
         "page-0569",
         "page-0632",
@@ -105535,7 +105376,7 @@
         "page-0550",
         "page-0734",
         "page-0857",
-        "page-0967",
+        "page-0966",
         "page-0974",
         "page-1192",
         "page-1204",
@@ -105714,12 +105555,12 @@
         "page-0145"
       ],
       "passes": [
-        "page-0147",
+        "page-0146",
         "page-0656",
         "page-0657"
       ],
       "conversion": [
-        "page-0147",
+        "page-0146",
         "page-0684",
         "page-1248"
       ],
@@ -105798,7 +105639,7 @@
         "page-0151",
         "page-0208",
         "page-0218",
-        "page-0515",
+        "page-0514",
         "page-0522",
         "page-0624",
         "page-0632",
@@ -105829,7 +105670,7 @@
       ],
       "clear": [
         "page-0151",
-        "page-0513",
+        "page-0512",
         "page-0551",
         "page-0554",
         "page-0558",
@@ -106071,7 +105912,7 @@
         "page-0196",
         "page-0202",
         "page-0207",
-        "page-0515",
+        "page-0514",
         "page-0632",
         "page-0636"
       ],
@@ -106190,7 +106031,7 @@
       ],
       "microsoft": [
         "page-0166",
-        "page-0373",
+        "page-0372",
         "page-0374",
         "page-0375",
         "page-0376",
@@ -106337,7 +106178,7 @@
         "page-0208",
         "page-0221",
         "page-0230",
-        "page-0515",
+        "page-0514",
         "page-0522",
         "page-0632",
         "page-0636",
@@ -106564,8 +106405,8 @@
         "page-0507",
         "page-0508",
         "page-0509",
+        "page-0511",
         "page-0512",
-        "page-0513",
         "page-0518",
         "page-0519",
         "page-0532",
@@ -106874,7 +106715,7 @@
       "local": [
         "page-0203",
         "page-0208",
-        "page-0515",
+        "page-0514",
         "page-0522",
         "page-0632",
         "page-0636",
@@ -107167,7 +107008,7 @@
         "page-0900",
         "page-0960",
         "page-0961",
-        "page-0965",
+        "page-0967",
         "page-1011",
         "page-1031",
         "page-1035"
@@ -107375,7 +107216,7 @@
       ],
       "after": [
         "page-0208",
-        "page-0511",
+        "page-0515",
         "page-0694",
         "page-1196"
       ],
@@ -107383,8 +107224,7 @@
         "page-0208"
       ],
       "logging": [
-        "page-0209",
-        "page-1261"
+        "page-0209"
       ],
       "'debug'": [
         "page-0209"
@@ -107542,8 +107382,7 @@
         "page-0218"
       ],
       "recommendations": [
-        "page-0218",
-        "page-1261"
+        "page-0218"
       ],
       "leader": [
         "page-0218"
@@ -107955,9 +107794,9 @@
         "page-0508",
         "page-0509",
         "page-0510",
+        "page-0511",
         "page-0512",
         "page-0513",
-        "page-0514",
         "page-0516",
         "page-0518",
         "page-0519",
@@ -108053,7 +107892,7 @@
         "page-0233",
         "page-0710",
         "page-1257",
-        "page-1263"
+        "page-1262"
       ],
       "fail": [
         "page-0233",
@@ -108175,8 +108014,8 @@
         "page-0368",
         "page-0369",
         "page-0370",
+        "page-0371",
         "page-0372",
-        "page-0373",
         "page-0374",
         "page-0375",
         "page-0376",
@@ -108297,7 +108136,7 @@
         "page-0449",
         "page-0666",
         "page-0814",
-        "page-0967"
+        "page-0966"
       ],
       "interacting": [
         "page-0240"
@@ -108862,19 +108701,19 @@
         "page-0370",
         "page-0871"
       ],
-      "messagebird": [
-        "page-0371",
-        "page-0872"
-      ],
       "metabase": [
-        "page-0372",
+        "page-0371",
         "page-0873",
         "page-1204"
       ],
       "dynamics": [
-        "page-0373",
+        "page-0372",
         "page-0874"
       ],
+      "messagebird": [
+        "page-0373",
+        "page-0872"
+      ],
       "entra": [
         "page-0374",
         "page-0739",
@@ -109015,7 +108854,7 @@
       "onfleet": [
         "page-0403",
         "page-0904",
-        "page-1093"
+        "page-1094"
       ],
       "openthesaurus": [
         "page-0404"
@@ -109039,7 +108878,7 @@
       "paypal": [
         "page-0409",
         "page-0913",
-        "page-1094"
+        "page-1095"
       ],
       "peekalink": [
         "page-0410",
@@ -109203,11 +109042,11 @@
       ],
       "stackby": [
         "page-0448",
-        "page-0966"
+        "page-0965"
       ],
       "storyblok": [
         "page-0449",
-        "page-0967"
+        "page-0966"
       ],
       "strapi": [
         "page-0450",
@@ -109421,7 +109260,7 @@
       ],
       "column": [
         "page-0491",
-        "page-0511",
+        "page-0515",
         "page-0553"
       ],
       "forbidden": [
@@ -109597,70 +109436,70 @@
       "drives": [
         "page-0509"
       ],
+      "spreadsheet": [
+        "page-0511"
+      ],
       "append": [
-        "page-0511",
-        "page-0513",
+        "page-0512",
+        "page-0515",
         "page-0674",
         "page-0683"
       ],
-      "names": [
-        "page-0511",
-        "page-0553",
-        "page-1149",
-        "page-1161"
-      ],
-      "were": [
-        "page-0511"
-      ],
-      "node's": [
-        "page-0511",
-        "page-1184"
-      ],
-      "spreadsheet": [
-        "page-0512"
-      ],
       "rows": [
-        "page-0513",
-        "page-0515",
+        "page-0512",
+        "page-0514",
         "page-0522",
         "page-0566"
       ],
       "columns": [
-        "page-0513",
+        "page-0512",
         "page-0520",
         "page-1142"
       ],
       "row(s)": [
-        "page-0513"
+        "page-0512"
       ],
       "composite": [
-        "page-0515",
+        "page-0514",
         "page-0651"
       ],
       "containers": [
-        "page-0515",
+        "page-0514",
         "page-0522",
         "page-0632",
         "page-0636"
       ],
       "decimal": [
-        "page-0515"
+        "page-0514"
       ],
       "numbers": [
-        "page-0515",
+        "page-0514",
         "page-0674",
         "page-1142"
       ],
       "strings": [
-        "page-0515",
+        "page-0514",
         "page-0520",
         "page-1204"
       ],
+      "names": [
+        "page-0515",
+        "page-0553",
+        "page-1149",
+        "page-1161"
+      ],
+      "were": [
+        "page-0515"
+      ],
+      "node's": [
+        "page-0515",
+        "page-1184"
+      ],
       "notion": [
         "page-0516",
         "page-0517",
         "page-0898",
-        "page-1095"
+        "page-1093"
       ],
       "property": [
         "page-0517",
@@ -111307,7 +111146,7 @@
       "private": [
         "page-0797",
         "page-0845",
-        "page-0965",
+        "page-0967",
         "page-1008",
         "page-1179"
       ],
@@ -111950,8 +111789,7 @@
       ],
       "general": [
         "page-1170",
-        "page-1205",
-        "page-1261"
+        "page-1205"
       ],
       "philosophy": [
         "page-1170"
@@ -112310,7 +112148,7 @@
       ],
       "partial": [
         "page-1205",
-        "page-1262"
+        "page-1261"
       ],
       "breadcrumb": [
         "page-1205"
@@ -112592,10 +112430,6 @@
       "called": [
         "page-1245"
       ],
-      "redact": [
-        "page-1245",
-        "page-1261"
-      ],
       "estimated": [
         "page-1245"
       ],
@@ -112626,10 +112460,6 @@
       "quotas:": [
         "page-1256"
       ],
-      "redaction": [
-        "page-1256",
-        "page-1261"
-      ],
       "past": [
         "page-1259"
       ],
@@ -112642,29 +112472,11 @@
       "marks": [
         "page-1260"
       ],
-      "explained": [
-        "page-1261"
-      ],
-      "redacted": [
-        "page-1261"
-      ],
-      "looks": [
-        "page-1261"
-      ],
-      "like": [
-        "page-1261"
-      ],
-      "reveal": [
-        "page-1261"
-      ],
-      "choosing": [
-        "page-1261"
-      ],
       "manual,": [
-        "page-1262"
+        "page-1261"
       ],
       "partial,": [
-        "page-1262"
+        "page-1261"
       ]
     },
     "byCategory": {
@@ -113954,8 +113766,7 @@
         "page-1259",
         "page-1260",
         "page-1261",
-        "page-1262",
-        "page-1263"
+        "page-1262"
       ]
     },
     "byNodeName": {
@@ -114367,13 +114178,13 @@
       "medium": [
         "page-0370"
       ],
-      "messagebird": [
+      "metabase": [
         "page-0371"
       ],
-      "metabase": [
+      "microsoftdynamicscrm": [
         "page-0372"
       ],
-      "microsoftdynamicscrm": [
+      "messagebird": [
         "page-0373"
       ],
       "microsoftentra": [
@@ -114751,11 +114562,11 @@
         "page-0510",
         "page-0511",
         "page-0512",
-        "page-0513"
+        "page-0515"
       ],
       "mysql": [
-        "page-0514",
-        "page-0515"
+        "page-0513",
+        "page-0514"
       ],
       "notion": [
         "page-0516",
@@ -115142,13 +114953,13 @@
       "netlifytrigger": [
         "page-1092"
       ],
-      "onfleettrigger": [
+      "notiontrigger": [
         "page-1093"
       ],
-      "paypaltrigger": [
+      "onfleettrigger": [
         "page-1094"
       ],
-      "notiontrigger": [
+      "paypaltrigger": [
         "page-1095"
       ],
       "pipedrivetrigger": [