@n8n-as-code/skills 2.1.1-next.3 → 2.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/assets/n8n-credentials-ontology.json +1 -1
- package/dist/assets/n8n-docs-complete.json +30 -20
- package/dist/assets/n8n-knowledge-index.json +46 -26
- package/dist/assets/n8n-nodes-index.json +5 -5
- package/dist/assets/n8n-nodes-technical.json +5 -5
- package/dist/assets/workflows-index.json +1 -1
- package/package.json +1 -1
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
{
|
|
2
|
-
"generatedAt": "2026-05-
|
|
2
|
+
"generatedAt": "2026-05-11T18:54:52.573Z",
|
|
3
3
|
"version": "1.0.0",
|
|
4
4
|
"sourceUrl": "https://docs.n8n.io/llms.txt",
|
|
5
5
|
"totalPages": 1279,
|
|
@@ -2211,7 +2211,7 @@
|
|
|
2211
2211
|
"nodeName": null,
|
|
2212
2212
|
"nodeType": null,
|
|
2213
2213
|
"content": {
|
|
2214
|
-
"markdown": "# Insights\n\nInsights gives instance owners and admins visibility into how workflows perform over time. This feature consists of three parts:\n\n- [**Insights summary banner**](#insights-summary-banner): Shows key metrics about your instance from the last 7 days at the top of the **Overview** space.\n- [**Insights dashboard**](#insights-dashboard): A more detailed visual breakdown with per-workflow metrics and historical comparisons.\n- [**Time saved (Workflow ROI)**](#setting-the-time-saved-by-a-workflow): For each workflow, you can choose to set a fixed amount of time saved per workflow, or dynamically calculate time saved based on the execution path taken on a specific workflow.\n\nFeature availability\n\nThe insights summary banner displays activity from the last 7 days for all plans. The insights dashboard is only available on Pro, Business, and Enterprise plans.\n\n## Insights summary banner\n\nn8n collects several metrics for both the insights summary banner and dashboard. They include:\n\n- Total production executions (not including sub-workflow executions or manual executions)\n- Total failed production executions\n- Production execution failure rate\n- Time saved (when set on at least one or more active workflows)\n- Run time average (including wait time from any wait nodes)\n\n## Insights dashboard\n\nAccess the **Insights** section from the side navigation. Each metric from the summary banner is also clickable, taking you to the corresponding chart.\n\nThe insights dashboard also has a table showing individual insights from each workflow including total production executions, failed production executions, failure rate, time saved, and run time average.\n\n## Insights time periods\n\nBy default, the insights summary banner and dashboard show a rolling 7 day window with a comparison to the previous period to identify increases or decreases for each metric. On the dashboard, paid plans also display data for other date ranges:\n\n- Pro: 7 and 14 days\n- Business: 24 hours, 7 days, 14 days, 30 days.\n- Enterprise: 24 hours, 7 days, 14 days, 30 days, 90 days, 6 months, 1 year\n\n## Setting the time saved by a workflow\n\nFor each workflow, you can track how much time it saves you. This setting helps you calculate how much time automating a process saves over time vs the manual effort to complete the same task or process.\n\nOnce configured, n8n calculates the amount of time the workflow saves you based on the number of production executions and displays it on the summary banner and insights dashboard.\n\nYou can choose between two methods for calculating time saved:\n\n### Fixed time saved\n\nWith fixed time saved, you set a single time value that applies to every production execution of the workflow, regardless of which path the execution takes.\n\nTo configure fixed time saved:\n\n1. Navigate to the workflow\n1. Select the three dots menu in the top right and select **Settings**\n1. In the **Estimated time saved** dropdown, select **Fixed**\n1. Enter the number of minutes of work each execution saves\n1. Save your settings\n\n### Dynamic time saved\n\nDynamic time saved calculates time savings based on the actual execution path taken, accounting for workflows where different execution paths save different amounts of time.\n\nTo configure dynamic time saved:\n\n1. Navigate to the workflow\n1. Select the three dots menu in the top right and select **Settings**\n1. In the **Estimated time saved** dropdown, select **Dynamic**\n1. Save your settings\n1. Add **Time Saved** nodes to your workflow at the points where time is saved\n1. For each Time Saved node, configure:\n - **Time saved**: The amount of time saved (in minutes)\n - **Calculation mode**: Choose whether to calculate the time saved once for all items in an execution, or per item which will multiply minutes saved by the total number of input items\n\nWhen you use dynamic time saved, n8n adds up the time from all Time Saved nodes that execute during a workflow run to calculate the total time saved for that execution.\n\nSubworkflow support\n\nTime saved tracking currently only works on parent workflows. Time saved from subworkflows isn't currently supported, with plans to support this in a future release.\n\n## Disable or configure insights metrics collection\n\nIf you self-host n8n, you can disable or configure insights and metrics collection using [environment variables](../hosting/configuration/environment-variables/insights/).\n\n## Insights FAQs\n\n### Which executions do n8n use to calculate the values in the insights banner and dashboard?\n\nn8n insights only collects data from production executions (for example, those from active workflows triggered on a schedule or a webhook) from the main (parent) workflow. This means that it doesn't count manual (test) executions or executions from sub-workflows or error workflows.\n\n### Does n8n use historic execution data when upgrading to a version with insights?\n\nn8n only starts collecting data for insights once you update to the first supported version (1.89.0). This means it only reports on executions from that point forward and you won't see execution data in insights from prior periods.\n",
|
|
2214
|
+
"markdown": "# Insights\n\nInsights gives instance owners and admins visibility into how workflows perform over time. This feature consists of three parts:\n\n- [**Insights summary banner**](#insights-summary-banner): Shows key metrics about your instance from the last 7 days at the top of the **Overview** space.\n- [**Insights dashboard**](#insights-dashboard): A more detailed visual breakdown with per-workflow metrics and historical comparisons.\n- [**Time saved (Workflow ROI)**](#setting-the-time-saved-by-a-workflow): For each workflow, you can choose to set a fixed amount of time saved per workflow, or dynamically calculate time saved based on the execution path taken on a specific workflow.\n\nFeature availability\n\nThe insights summary banner displays activity from the last 7 days for all plans. The insights dashboard is only available on Pro, Business, and Enterprise plans.\n\n## Insights summary banner\n\nn8n collects several metrics for both the insights summary banner and dashboard. They include:\n\n- Total production executions (not including sub-workflow executions or manual executions)\n- Total failed production executions\n- Production execution failure rate\n- Time saved (when set on at least one or more active workflows)\n- Run time average (including wait time from any wait nodes)\n\n## Insights dashboard\n\nAccess the **Insights** section from the side navigation. Each metric from the summary banner is also clickable, taking you to the corresponding chart.\n\nThe insights dashboard also has a table showing individual insights from each workflow including total production executions, failed production executions, failure rate, time saved, and run time average.\n\n## Insights time periods\n\nBy default, the insights summary banner and dashboard show a rolling 7 day window with a comparison to the previous period to identify increases or decreases for each metric. On the dashboard, paid plans also display data for other date ranges:\n\n- Pro: 7 and 14 days\n- Business: 24 hours, 7 days, 14 days, 30 days.\n- Enterprise: 24 hours, 7 days, 14 days, 30 days, 90 days, 6 months, 1 year\n\n## Setting the time saved by a workflow\n\nFor each workflow, you can track how much time it saves you. This setting helps you calculate how much time automating a process saves over time vs the manual effort to complete the same task or process.\n\nOnce configured, n8n calculates the amount of time the workflow saves you based on the number of production executions and displays it on the summary banner and insights dashboard.\n\nYou can choose between two methods for calculating time saved:\n\n### Fixed time saved\n\nWith fixed time saved, you set a single time value that applies to every production execution of the workflow, regardless of which path the execution takes.\n\nTo configure fixed time saved:\n\n1. Navigate to the workflow\n1. Select the three dots menu in the top right and select **Settings**\n1. In the **Estimated time saved** dropdown, select **Fixed**\n1. Enter the number of minutes of work each execution saves\n1. Save your settings\n\n### Dynamic time saved\n\nDynamic time saved calculates time savings based on the actual execution path taken, accounting for workflows where different execution paths save different amounts of time.\n\nTo configure dynamic time saved:\n\n1. Navigate to the workflow\n1. Select the three dots menu in the top right and select **Settings**\n1. In the **Estimated time saved** dropdown, select **Dynamic**\n1. Save your settings\n1. Add **Time Saved** nodes to your workflow at the points where time is saved\n1. For each Time Saved node, configure:\n - **Time saved**: The amount of time saved (in minutes)\n - **Calculation mode**: Choose whether to calculate the time saved once for all items in an execution, or per item which will multiply minutes saved by the total number of input items\n\nWhen you use dynamic time saved, n8n adds up the time from all Time Saved nodes that execute during a workflow run to calculate the total time saved for that execution.\n\nSubworkflow support\n\nTime saved tracking currently only works on parent workflows. Time saved from subworkflows isn't currently supported, with plans to support this in a future release.\n\n## Disable or configure insights metrics collection\n\nIf you self-host n8n, you can disable or configure insights and metrics collection using [environment variables](../hosting/configuration/environment-variables/insights/).\n\nBy default, n8n keeps compacted insights data for 365 days (`N8N_INSIGHTS_MAX_AGE_DAYS`). n8n caps retention at 730 days (two years); use a lower number for a shorter window. To turn off insights collection entirely, set `N8N_DISABLED_MODULES=insights` (refer to the [environment variables page](../hosting/configuration/environment-variables/insights/)).\n\nSelf-host upgrade\n\nIn older versions, pruning could follow license-driven defaults (commonly 180 days). `N8N_INSIGHTS_MAX_AGE_DAYS` now controls pruning (default 365). Set `N8N_INSIGHTS_MAX_AGE_DAYS=180` if you want a retention window like that previous default.\n\nn8n stores recent insights at one-hour granularity, then compacts older data into day-level and week-level summaries. Use [Insights environment variables](../hosting/configuration/environment-variables/insights/) to control how long n8n waits before each compaction step.\n\nRaising those thresholds above the defaults keeps finer detail longer. That adds more rows to `insights_by_period` and uses more database space than extending `N8N_INSIGHTS_MAX_AGE_DAYS` alone. Increase `N8N_INSIGHTS_MAX_AGE_DAYS` first if you only need a longer retention window.\n\n## Insights FAQs\n\n### Which executions do n8n use to calculate the values in the insights banner and dashboard?\n\nn8n insights only collects data from production executions (for example, those from active workflows triggered on a schedule or a webhook) from the main (parent) workflow. This means that it doesn't count manual (test) executions or executions from sub-workflows or error workflows.\n\n### Does n8n use historic execution data when upgrading to a version with insights?\n\nn8n only starts collecting data for insights once you update to the first supported version (1.89.0). This means it only reports on executions from that point forward and you won't see execution data in insights from prior periods.\n",
|
|
2215
2215
|
"excerpt": "# Insights Insights gives instance owners and admins visibility into how workflows perform over time. This feature consists of three parts: - [**Insights summary banner**](#insights-summary-banner): Shows key metrics about your instance from the last 7 days at the top of the **Overview** space. - [**Insights dashboard**](#insights-dashboard): A more detailed visual breakdown with per-workflow metrics and historical comparisons. - [**Time saved (Workflow ROI)**](#setting-the-time-saved-by-a-wor...",
|
|
2216
2216
|
"sections": [
|
|
2217
2217
|
{
|
|
@@ -2258,42 +2258,48 @@
|
|
|
2258
2258
|
"operations": [],
|
|
2259
2259
|
"codeExamples": 0,
|
|
2260
2260
|
"complexity": "beginner",
|
|
2261
|
-
"readingTime": "
|
|
2262
|
-
"contentLength":
|
|
2261
|
+
"readingTime": "5 min",
|
|
2262
|
+
"contentLength": 6293,
|
|
2263
2263
|
"relatedPages": []
|
|
2264
2264
|
},
|
|
2265
2265
|
"searchIndex": {
|
|
2266
|
-
"fullText": "insights # insights\n\ninsights gives instance owners and admins visibility into how workflows perform over time. this feature consists of three parts:\n\n- [**insights summary banner**](#insights-summary-banner): shows key metrics about your instance from the last 7 days at the top of the **overview** space.\n- [**insights dashboard**](#insights-dashboard): a more detailed visual breakdown with per-workflow metrics and historical comparisons.\n- [**time saved (workflow roi)**](#setting-the-time-saved-by-a-workflow): for each workflow, you can choose to set a fixed amount of time saved per workflow, or dynamically calculate time saved based on the execution path taken on a specific workflow.\n\nfeature availability\n\nthe insights summary banner displays activity from the last 7 days for all plans. the insights dashboard is only available on pro, business, and enterprise plans.\n\n## insights summary banner\n\nn8n collects several metrics for both the insights summary banner and dashboard. they include:\n\n- total production executions (not including sub-workflow executions or manual executions)\n- total failed production executions\n- production execution failure rate\n- time saved (when set on at least one or more active workflows)\n- run time average (including wait time from any wait nodes)\n\n## insights dashboard\n\naccess the **insights** section from the side navigation. each metric from the summary banner is also clickable, taking you to the corresponding chart.\n\nthe insights dashboard also has a table showing individual insights from each workflow including total production executions, failed production executions, failure rate, time saved, and run time average.\n\n## insights time periods\n\nby default, the insights summary banner and dashboard show a rolling 7 day window with a comparison to the previous period to identify increases or decreases for each metric. on the dashboard, paid plans also display data for other date ranges:\n\n- pro: 7 and 14 days\n- business: 24 hours, 7 days, 14 days, 30 days.\n- enterprise: 24 hours, 7 days, 14 days, 30 days, 90 days, 6 months, 1 year\n\n## setting the time saved by a workflow\n\nfor each workflow, you can track how much time it saves you. this setting helps you calculate how much time automating a process saves over time vs the manual effort to complete the same task or process.\n\nonce configured, n8n calculates the amount of time the workflow saves you based on the number of production executions and displays it on the summary banner and insights dashboard.\n\nyou can choose between two methods for calculating time saved:\n\n### fixed time saved\n\nwith fixed time saved, you set a single time value that applies to every production execution of the workflow, regardless of which path the execution takes.\n\nto configure fixed time saved:\n\n1. navigate to the workflow\n1. select the three dots menu in the top right and select **settings**\n1. in the **estimated time saved** dropdown, select **fixed**\n1. enter the number of minutes of work each execution saves\n1. save your settings\n\n### dynamic time saved\n\ndynamic time saved calculates time savings based on the actual execution path taken, accounting for workflows where different execution paths save different amounts of time.\n\nto configure dynamic time saved:\n\n1. navigate to the workflow\n1. select the three dots menu in the top right and select **settings**\n1. in the **estimated time saved** dropdown, select **dynamic**\n1. save your settings\n1. add **time saved** nodes to your workflow at the points where time is saved\n1. for each time saved node, configure:\n - **time saved**: the amount of time saved (in minutes)\n - **calculation mode**: choose whether to calculate the time saved once for all items in an execution, or per item which will multiply minutes saved by the total number of input items\n\nwhen you use dynamic time saved, n8n adds up the time from all time saved nodes that execute during a workflow run to calculate the total time saved for that execution.\n\nsubworkflow support\n\ntime saved tracking currently only works on parent workflows. time saved from subworkflows isn't currently supported, with plans to support this in a future release.\n\n## disable or configure insights metrics collection\n\nif you self-host n8n, you can disable or configure insights and metrics collection using [environment variables](../hosting/configuration/environment-variables/insights/).\n\n## insights faqs\n\n### which executions do n8n use to calculate the values in the insights banner and dashboard?\n\nn8n insights only collects data from production executions (for example, those from active workflows triggered on a schedule or a webhook) from the main (parent) workflow. this means that it doesn't count manual (test) executions or executions from sub-workflows or error workflows.\n\n### does n8n use historic execution data when upgrading to a version with insights?\n\nn8n only starts collecting data for insights once you update to the first supported version (1.89.0). this means it only reports on executions from that point forward and you won't see execution data in insights from prior periods.\n insights",
|
|
2266
|
+
"fullText": "insights # insights\n\ninsights gives instance owners and admins visibility into how workflows perform over time. this feature consists of three parts:\n\n- [**insights summary banner**](#insights-summary-banner): shows key metrics about your instance from the last 7 days at the top of the **overview** space.\n- [**insights dashboard**](#insights-dashboard): a more detailed visual breakdown with per-workflow metrics and historical comparisons.\n- [**time saved (workflow roi)**](#setting-the-time-saved-by-a-workflow): for each workflow, you can choose to set a fixed amount of time saved per workflow, or dynamically calculate time saved based on the execution path taken on a specific workflow.\n\nfeature availability\n\nthe insights summary banner displays activity from the last 7 days for all plans. the insights dashboard is only available on pro, business, and enterprise plans.\n\n## insights summary banner\n\nn8n collects several metrics for both the insights summary banner and dashboard. they include:\n\n- total production executions (not including sub-workflow executions or manual executions)\n- total failed production executions\n- production execution failure rate\n- time saved (when set on at least one or more active workflows)\n- run time average (including wait time from any wait nodes)\n\n## insights dashboard\n\naccess the **insights** section from the side navigation. each metric from the summary banner is also clickable, taking you to the corresponding chart.\n\nthe insights dashboard also has a table showing individual insights from each workflow including total production executions, failed production executions, failure rate, time saved, and run time average.\n\n## insights time periods\n\nby default, the insights summary banner and dashboard show a rolling 7 day window with a comparison to the previous period to identify increases or decreases for each metric. on the dashboard, paid plans also display data for other date ranges:\n\n- pro: 7 and 14 days\n- business: 24 hours, 7 days, 14 days, 30 days.\n- enterprise: 24 hours, 7 days, 14 days, 30 days, 90 days, 6 months, 1 year\n\n## setting the time saved by a workflow\n\nfor each workflow, you can track how much time it saves you. this setting helps you calculate how much time automating a process saves over time vs the manual effort to complete the same task or process.\n\nonce configured, n8n calculates the amount of time the workflow saves you based on the number of production executions and displays it on the summary banner and insights dashboard.\n\nyou can choose between two methods for calculating time saved:\n\n### fixed time saved\n\nwith fixed time saved, you set a single time value that applies to every production execution of the workflow, regardless of which path the execution takes.\n\nto configure fixed time saved:\n\n1. navigate to the workflow\n1. select the three dots menu in the top right and select **settings**\n1. in the **estimated time saved** dropdown, select **fixed**\n1. enter the number of minutes of work each execution saves\n1. save your settings\n\n### dynamic time saved\n\ndynamic time saved calculates time savings based on the actual execution path taken, accounting for workflows where different execution paths save different amounts of time.\n\nto configure dynamic time saved:\n\n1. navigate to the workflow\n1. select the three dots menu in the top right and select **settings**\n1. in the **estimated time saved** dropdown, select **dynamic**\n1. save your settings\n1. add **time saved** nodes to your workflow at the points where time is saved\n1. for each time saved node, configure:\n - **time saved**: the amount of time saved (in minutes)\n - **calculation mode**: choose whether to calculate the time saved once for all items in an execution, or per item which will multiply minutes saved by the total number of input items\n\nwhen you use dynamic time saved, n8n adds up the time from all time saved nodes that execute during a workflow run to calculate the total time saved for that execution.\n\nsubworkflow support\n\ntime saved tracking currently only works on parent workflows. time saved from subworkflows isn't currently supported, with plans to support this in a future release.\n\n## disable or configure insights metrics collection\n\nif you self-host n8n, you can disable or configure insights and metrics collection using [environment variables](../hosting/configuration/environment-variables/insights/).\n\nby default, n8n keeps compacted insights data for 365 days (`n8n_insights_max_age_days`). n8n caps retention at 730 days (two years); use a lower number for a shorter window. to turn off insights collection entirely, set `n8n_disabled_modules=insights` (refer to the [environment variables page](../hosting/configuration/environment-variables/insights/)).\n\nself-host upgrade\n\nin older versions, pruning could follow license-driven defaults (commonly 180 days). `n8n_insights_max_age_days` now controls pruning (default 365). set `n8n_insights_max_age_days=180` if you want a retention window like that previous default.\n\nn8n stores recent insights at one-hour granularity, then compacts older data into day-level and week-level summaries. use [insights environment variables](../hosting/configuration/environment-variables/insights/) to control how long n8n waits before each compaction step.\n\nraising those thresholds above the defaults keeps finer detail longer. that adds more rows to `insights_by_period` and uses more database space than extending `n8n_insights_max_age_days` alone. increase `n8n_insights_max_age_days` first if you only need a longer retention window.\n\n## insights faqs\n\n### which executions do n8n use to calculate the values in the insights banner and dashboard?\n\nn8n insights only collects data from production executions (for example, those from active workflows triggered on a schedule or a webhook) from the main (parent) workflow. this means that it doesn't count manual (test) executions or executions from sub-workflows or error workflows.\n\n### does n8n use historic execution data when upgrading to a version with insights?\n\nn8n only starts collecting data for insights once you update to the first supported version (1.89.0). this means it only reports on executions from that point forward and you won't see execution data in insights from prior periods.\n insights",
|
|
2267
2267
|
"importantTerms": [
|
|
2268
2268
|
"time",
|
|
2269
2269
|
"insights",
|
|
2270
2270
|
"saved",
|
|
2271
2271
|
"workflow",
|
|
2272
2272
|
"from",
|
|
2273
|
+
"days",
|
|
2273
2274
|
"executions",
|
|
2274
2275
|
"execution",
|
|
2275
|
-
"days",
|
|
2276
2276
|
"dashboard",
|
|
2277
2277
|
"banner",
|
|
2278
2278
|
"summary",
|
|
2279
|
+
"each",
|
|
2279
2280
|
"production",
|
|
2280
2281
|
"workflows",
|
|
2281
|
-
"
|
|
2282
|
+
"data",
|
|
2283
|
+
"that",
|
|
2284
|
+
"only",
|
|
2282
2285
|
"select",
|
|
2286
|
+
"environment",
|
|
2287
|
+
"variables",
|
|
2283
2288
|
"this",
|
|
2284
2289
|
"metrics",
|
|
2285
2290
|
"with",
|
|
2286
2291
|
"fixed",
|
|
2287
2292
|
"calculate",
|
|
2288
|
-
"only",
|
|
2289
2293
|
"total",
|
|
2290
|
-
"data",
|
|
2291
|
-
"that",
|
|
2292
2294
|
"configure",
|
|
2293
2295
|
"dynamic",
|
|
2294
2296
|
"your",
|
|
2297
|
+
"more",
|
|
2295
2298
|
"plans",
|
|
2299
|
+
"default",
|
|
2300
|
+
"window",
|
|
2296
2301
|
"saves",
|
|
2302
|
+
"number",
|
|
2297
2303
|
"settings",
|
|
2298
2304
|
"three",
|
|
2299
2305
|
"setting",
|
|
@@ -2307,10 +2313,8 @@
|
|
|
2307
2313
|
"nodes",
|
|
2308
2314
|
"also",
|
|
2309
2315
|
"once",
|
|
2310
|
-
"number",
|
|
2311
2316
|
"which",
|
|
2312
|
-
"minutes"
|
|
2313
|
-
"save"
|
|
2317
|
+
"minutes"
|
|
2314
2318
|
]
|
|
2315
2319
|
}
|
|
2316
2320
|
},
|
|
@@ -15702,13 +15706,13 @@
|
|
|
15702
15706
|
"nodeName": null,
|
|
15703
15707
|
"nodeType": null,
|
|
15704
15708
|
"content": {
|
|
15705
|
-
"markdown": "# Insights environment variables\n\nFile-based configuration\n\nYou can add `_FILE` to individual variables to provide their configuration in a separate file. Refer to [Keeping sensitive data in separate files](../../configuration-methods/#keeping-sensitive-data-in-separate-files) for more details.\n\nInsights gives instance owners and admins visibility into how workflows perform over time. Refer to [Insights](../../../../insights/) for details.\n\n| Variable | Type | Default | Description
|
|
15706
|
-
"excerpt": "# Insights environment variables File-based configuration You can add `_FILE` to individual variables to provide their configuration in a separate file. Refer to [Keeping sensitive data in separate files](../../configuration-methods/#keeping-sensitive-data-in-separate-files) for more details. Insights gives instance owners and admins visibility into how workflows perform over time. Refer to [Insights](../../../../insights/) for details.
|
|
15709
|
+
"markdown": "# Insights environment variables\n\nFile-based configuration\n\nYou can add `_FILE` to individual variables to provide their configuration in a separate file. Refer to [Keeping sensitive data in separate files](../../configuration-methods/#keeping-sensitive-data-in-separate-files) for more details.\n\nInsights gives instance owners and admins visibility into how workflows perform over time. Refer to [Insights](../../../../insights/) for details.\n\nStorage and compaction thresholds\n\n`N8N_INSIGHTS_COMPACTION_HOURLY_TO_DAILY_THRESHOLD_DAYS` and `N8N_INSIGHTS_COMPACTION_DAILY_TO_WEEKLY_THRESHOLD_DAYS` set how many days n8n keeps high-resolution insights (metrics stored in one-hour buckets) before each compaction step (from the hour bucket to the day bucket, then from the day bucket to the week bucket). You configure those day counts on your instance.\n\nRaising the values delays compaction. That adds more rows to `insights_by_period` and increases database usage. For how this relates to retention, see [Insights](../../../../insights/#disable-or-configure-insights-metrics-collection).\n\n| Variable | Type | Default | Description |\n| -------------------------------------------------------- | ------ | ------- | ----------------------------------------------------------------------------------------------------------- |\n| `N8N_DISABLED_MODULES` | String | - | Set to `insights` to disable the feature and metrics collection for an instance. |\n| `N8N_INSIGHTS_COMPACTION_BATCH_SIZE` | Number | 500 | The number of raw insights data to compact in a single batch. |\n| `N8N_INSIGHTS_COMPACTION_DAILY_TO_WEEKLY_THRESHOLD_DAYS` | Number | 180 | Age in days after which n8n compacts daily insights rows to weekly. |\n| `N8N_INSIGHTS_COMPACTION_HOURLY_TO_DAILY_THRESHOLD_DAYS` | Number | 90 | Age in days after which n8n compacts hourly insights rows to daily. |\n| `N8N_INSIGHTS_COMPACTION_INTERVAL_MINUTES` | Number | 60 | Interval (in minutes) at which compaction should run. |\n| `N8N_INSIGHTS_FLUSH_BATCH_SIZE` | Number | 1000 | The maximum number of insights data to keep in the buffer before flushing. |\n| `N8N_INSIGHTS_FLUSH_INTERVAL_SECONDS` | Number | 30 | The interval (in seconds) at which n8n flushes insights data to the database. |\n| `N8N_INSIGHTS_MAX_AGE_DAYS` | Number | 365 | Number of days n8n keeps compacted insights data before pruning. The maximum value is 730 (two years). |\n| `N8N_INSIGHTS_PRUNE_CHECK_INTERVAL_HOURS` | Number | 24 | How often (in hours) the instance checks for insights data older than the effective max age and deletes it. |\n",
|
|
15710
|
+
"excerpt": "# Insights environment variables File-based configuration You can add `_FILE` to individual variables to provide their configuration in a separate file. Refer to [Keeping sensitive data in separate files](../../configuration-methods/#keeping-sensitive-data-in-separate-files) for more details. Insights gives instance owners and admins visibility into how workflows perform over time. Refer to [Insights](../../../../insights/) for details. Storage and compaction thresholds `N8N_INSIGHTS_COMPAC...",
|
|
15707
15711
|
"sections": [
|
|
15708
15712
|
{
|
|
15709
15713
|
"title": "Insights environment variables",
|
|
15710
15714
|
"level": 1,
|
|
15711
|
-
"content": "File-based configuration\n\nYou can add `_FILE` to individual variables to provide their configuration in a separate file. Refer to [Keeping sensitive data in separate files](../../configuration-methods/#keeping-sensitive-data-in-separate-files) for more details.\n\nInsights gives instance owners and admins visibility into how workflows perform over time. Refer to [Insights](../../../../insights/) for details.\n\
|
|
15715
|
+
"content": "File-based configuration\n\nYou can add `_FILE` to individual variables to provide their configuration in a separate file. Refer to [Keeping sensitive data in separate files](../../configuration-methods/#keeping-sensitive-data-in-separate-files) for more details.\n\nInsights gives instance owners and admins visibility into how workflows perform over time. Refer to [Insights](../../../../insights/) for details.\n\nStorage and compaction thresholds\n\n`N8N_INSIGHTS_COMPACTION_HOURLY_TO_DAILY_THRESHOLD_DAYS` and `N8N_INSIGHTS_COMPACTION_DAILY_TO_WEEKLY_THRESHOLD_DAYS` set how many days n8n keeps high-resolution insights (metrics stored in one-hour buckets) before each compaction step (from the hour bucket to the day bucket, then from the day bucket to the week bucket). You configure those day counts on your instance.\n\nRaising the values delays compaction. That adds more rows to `insights_by_period` and increases database usage. For how this relates to retention, see [Insights](../../../../insight"
|
|
15712
15716
|
}
|
|
15713
15717
|
]
|
|
15714
15718
|
},
|
|
@@ -15723,20 +15727,26 @@
|
|
|
15723
15727
|
"codeExamples": 0,
|
|
15724
15728
|
"complexity": "beginner",
|
|
15725
15729
|
"readingTime": "2 min",
|
|
15726
|
-
"contentLength":
|
|
15730
|
+
"contentLength": 3179,
|
|
15727
15731
|
"relatedPages": []
|
|
15728
15732
|
},
|
|
15729
15733
|
"searchIndex": {
|
|
15730
|
-
"fullText": "insights # insights environment variables\n\nfile-based configuration\n\nyou can add `_file` to individual variables to provide their configuration in a separate file. refer to [keeping sensitive data in separate files](../../configuration-methods/#keeping-sensitive-data-in-separate-files) for more details.\n\ninsights gives instance owners and admins visibility into how workflows perform over time. refer to [insights](../../../../insights/) for details.\n\n| variable | type | default | description
|
|
15734
|
+
"fullText": "insights # insights environment variables\n\nfile-based configuration\n\nyou can add `_file` to individual variables to provide their configuration in a separate file. refer to [keeping sensitive data in separate files](../../configuration-methods/#keeping-sensitive-data-in-separate-files) for more details.\n\ninsights gives instance owners and admins visibility into how workflows perform over time. refer to [insights](../../../../insights/) for details.\n\nstorage and compaction thresholds\n\n`n8n_insights_compaction_hourly_to_daily_threshold_days` and `n8n_insights_compaction_daily_to_weekly_threshold_days` set how many days n8n keeps high-resolution insights (metrics stored in one-hour buckets) before each compaction step (from the hour bucket to the day bucket, then from the day bucket to the week bucket). you configure those day counts on your instance.\n\nraising the values delays compaction. that adds more rows to `insights_by_period` and increases database usage. for how this relates to retention, see [insights](../../../../insights/#disable-or-configure-insights-metrics-collection).\n\n| variable | type | default | description |\n| -------------------------------------------------------- | ------ | ------- | ----------------------------------------------------------------------------------------------------------- |\n| `n8n_disabled_modules` | string | - | set to `insights` to disable the feature and metrics collection for an instance. |\n| `n8n_insights_compaction_batch_size` | number | 500 | the number of raw insights data to compact in a single batch. |\n| `n8n_insights_compaction_daily_to_weekly_threshold_days` | number | 180 | age in days after which n8n compacts daily insights rows to weekly. |\n| `n8n_insights_compaction_hourly_to_daily_threshold_days` | number | 90 | age in days after which n8n compacts hourly insights rows to daily. |\n| `n8n_insights_compaction_interval_minutes` | number | 60 | interval (in minutes) at which compaction should run. |\n| `n8n_insights_flush_batch_size` | number | 1000 | the maximum number of insights data to keep in the buffer before flushing. |\n| `n8n_insights_flush_interval_seconds` | number | 30 | the interval (in seconds) at which n8n flushes insights data to the database. |\n| `n8n_insights_max_age_days` | number | 365 | number of days n8n keeps compacted insights data before pruning. the maximum value is 730 (two years). |\n| `n8n_insights_prune_check_interval_hours` | number | 24 | how often (in hours) the instance checks for insights data older than the effective max age and deletes it. |\n insights environment variables",
|
|
15731
15735
|
"importantTerms": [
|
|
15732
15736
|
"insights",
|
|
15733
15737
|
"number",
|
|
15734
15738
|
"data",
|
|
15739
|
+
"instance",
|
|
15740
|
+
"compaction",
|
|
15741
|
+
"days",
|
|
15742
|
+
"bucket",
|
|
15743
|
+
"which",
|
|
15735
15744
|
"variables",
|
|
15736
15745
|
"configuration",
|
|
15737
15746
|
"separate",
|
|
15738
|
-
"
|
|
15739
|
-
"
|
|
15747
|
+
"metrics",
|
|
15748
|
+
"before",
|
|
15749
|
+
"rows"
|
|
15740
15750
|
]
|
|
15741
15751
|
}
|
|
15742
15752
|
},
|