@n8n-as-code/skills 2.1.0 → 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 +193 -64
- package/dist/assets/n8n-knowledge-index.json +166 -60
- 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,11 +1,11 @@
|
|
|
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
|
-
"totalPages":
|
|
5
|
+
"totalPages": 1279,
|
|
6
6
|
"statistics": {
|
|
7
7
|
"byCategory": {
|
|
8
|
-
"other":
|
|
8
|
+
"other": 514,
|
|
9
9
|
"tutorials": 27,
|
|
10
10
|
"advanced-ai": 28,
|
|
11
11
|
"api": 6,
|
|
@@ -26,7 +26,7 @@
|
|
|
26
26
|
"categories": {
|
|
27
27
|
"other": {
|
|
28
28
|
"description": "General documentation and guides",
|
|
29
|
-
"totalPages":
|
|
29
|
+
"totalPages": 514,
|
|
30
30
|
"pages": [
|
|
31
31
|
"page-0001",
|
|
32
32
|
"page-0002",
|
|
@@ -49,6 +49,7 @@
|
|
|
49
49
|
"page-0237",
|
|
50
50
|
"page-0238",
|
|
51
51
|
"page-0239",
|
|
52
|
+
"page-0240",
|
|
52
53
|
"page-0654",
|
|
53
54
|
"page-0655",
|
|
54
55
|
"page-0656",
|
|
@@ -2210,7 +2211,7 @@
|
|
|
2210
2211
|
"nodeName": null,
|
|
2211
2212
|
"nodeType": null,
|
|
2212
2213
|
"content": {
|
|
2213
|
-
"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",
|
|
2214
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...",
|
|
2215
2216
|
"sections": [
|
|
2216
2217
|
{
|
|
@@ -2257,42 +2258,48 @@
|
|
|
2257
2258
|
"operations": [],
|
|
2258
2259
|
"codeExamples": 0,
|
|
2259
2260
|
"complexity": "beginner",
|
|
2260
|
-
"readingTime": "
|
|
2261
|
-
"contentLength":
|
|
2261
|
+
"readingTime": "5 min",
|
|
2262
|
+
"contentLength": 6293,
|
|
2262
2263
|
"relatedPages": []
|
|
2263
2264
|
},
|
|
2264
2265
|
"searchIndex": {
|
|
2265
|
-
"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",
|
|
2266
2267
|
"importantTerms": [
|
|
2267
2268
|
"time",
|
|
2268
2269
|
"insights",
|
|
2269
2270
|
"saved",
|
|
2270
2271
|
"workflow",
|
|
2271
2272
|
"from",
|
|
2273
|
+
"days",
|
|
2272
2274
|
"executions",
|
|
2273
2275
|
"execution",
|
|
2274
|
-
"days",
|
|
2275
2276
|
"dashboard",
|
|
2276
2277
|
"banner",
|
|
2277
2278
|
"summary",
|
|
2279
|
+
"each",
|
|
2278
2280
|
"production",
|
|
2279
2281
|
"workflows",
|
|
2280
|
-
"
|
|
2282
|
+
"data",
|
|
2283
|
+
"that",
|
|
2284
|
+
"only",
|
|
2281
2285
|
"select",
|
|
2286
|
+
"environment",
|
|
2287
|
+
"variables",
|
|
2282
2288
|
"this",
|
|
2283
2289
|
"metrics",
|
|
2284
2290
|
"with",
|
|
2285
2291
|
"fixed",
|
|
2286
2292
|
"calculate",
|
|
2287
|
-
"only",
|
|
2288
2293
|
"total",
|
|
2289
|
-
"data",
|
|
2290
|
-
"that",
|
|
2291
2294
|
"configure",
|
|
2292
2295
|
"dynamic",
|
|
2293
2296
|
"your",
|
|
2297
|
+
"more",
|
|
2294
2298
|
"plans",
|
|
2299
|
+
"default",
|
|
2300
|
+
"window",
|
|
2295
2301
|
"saves",
|
|
2302
|
+
"number",
|
|
2296
2303
|
"settings",
|
|
2297
2304
|
"three",
|
|
2298
2305
|
"setting",
|
|
@@ -2306,10 +2313,8 @@
|
|
|
2306
2313
|
"nodes",
|
|
2307
2314
|
"also",
|
|
2308
2315
|
"once",
|
|
2309
|
-
"number",
|
|
2310
2316
|
"which",
|
|
2311
|
-
"minutes"
|
|
2312
|
-
"save"
|
|
2317
|
+
"minutes"
|
|
2313
2318
|
]
|
|
2314
2319
|
}
|
|
2315
2320
|
},
|
|
@@ -15701,13 +15706,13 @@
|
|
|
15701
15706
|
"nodeName": null,
|
|
15702
15707
|
"nodeType": null,
|
|
15703
15708
|
"content": {
|
|
15704
|
-
"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
|
|
15705
|
-
"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...",
|
|
15706
15711
|
"sections": [
|
|
15707
15712
|
{
|
|
15708
15713
|
"title": "Insights environment variables",
|
|
15709
15714
|
"level": 1,
|
|
15710
|
-
"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"
|
|
15711
15716
|
}
|
|
15712
15717
|
]
|
|
15713
15718
|
},
|
|
@@ -15722,20 +15727,26 @@
|
|
|
15722
15727
|
"codeExamples": 0,
|
|
15723
15728
|
"complexity": "beginner",
|
|
15724
15729
|
"readingTime": "2 min",
|
|
15725
|
-
"contentLength":
|
|
15730
|
+
"contentLength": 3179,
|
|
15726
15731
|
"relatedPages": []
|
|
15727
15732
|
},
|
|
15728
15733
|
"searchIndex": {
|
|
15729
|
-
"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",
|
|
15730
15735
|
"importantTerms": [
|
|
15731
15736
|
"insights",
|
|
15732
15737
|
"number",
|
|
15733
15738
|
"data",
|
|
15739
|
+
"instance",
|
|
15740
|
+
"compaction",
|
|
15741
|
+
"days",
|
|
15742
|
+
"bucket",
|
|
15743
|
+
"which",
|
|
15734
15744
|
"variables",
|
|
15735
15745
|
"configuration",
|
|
15736
15746
|
"separate",
|
|
15737
|
-
"
|
|
15738
|
-
"
|
|
15747
|
+
"metrics",
|
|
15748
|
+
"before",
|
|
15749
|
+
"rows"
|
|
15739
15750
|
]
|
|
15740
15751
|
}
|
|
15741
15752
|
},
|
|
@@ -20762,13 +20773,13 @@
|
|
|
20762
20773
|
"nodeName": null,
|
|
20763
20774
|
"nodeType": null,
|
|
20764
20775
|
"content": {
|
|
20765
|
-
"markdown": "#
|
|
20766
|
-
"excerpt": "#
|
|
20776
|
+
"markdown": "# Built-in integrations\n\nThis section contains the [node](../../../glossary/#node-n8n) library: reference documentation for every built-in node in n8n, and their credentials.\n\n## Node operations: Triggers and Actions\n\nWhen you add a node to a workflow, n8n displays a list of available operations. An operation is something a node does, such as getting or sending data.\n\nThere are two types of operation:\n\n- Triggers start a workflow in response to specific events or conditions in your services. When you select a Trigger, n8n adds a trigger node to your workflow, with the Trigger operation you chose pre-selected. When you search for a node in n8n, Trigger operations have a bolt icon .\n- Actions are operations that represent specific tasks within a workflow, which you can use to manipulate data, perform operations on external systems, and trigger events in other systems as part of your workflows. When you select an Action, n8n adds a node to your workflow, with the Action operation you chose pre-selected.\n\n## Core nodes\n\nCore nodes can be actions or [triggers](../../../glossary/#trigger-node-n8n). Whereas most nodes connect to a specific external service, core nodes provide functionality such as logic, scheduling, or generic API calls.\n\n## Cluster nodes\n\n[Cluster nodes](../../../glossary/#cluster-node-n8n) are node groups that work together to provide functionality in an n8n workflow. Instead of using a single node, you use a [root node](../../../glossary/#root-node-n8n) and one or more [sub-nodes](../../../glossary/#sub-node-n8n) that extend the functionality of the node.\n\n## Credentials\n\nExternal services need a way to identify and authenticate users. This data can range from an API key over an email/password combination to a long multi-line private key. You can save these in n8n as [credentials](../../../glossary/#credential-n8n).\n\nNodes in n8n can then request that credential information. As another layer of security, only node types with specific access rights can access the credentials.\n\nTo make sure that the data is secure, it gets saved to the database encrypted. n8n uses a random personal encryption key, which it automatically generates on the first run of n8n and then saved under `~/.n8n/config`.\n\nTo learn more about creating, managing, and sharing credentials, refer to [Manage credentials](../../../credentials/).\n\n## Community nodes\n\nn8n supports custom nodes built by the community. Refer to [Community nodes](../../community-nodes/installation/) for guidance on installing and using these nodes.\n\nFor help building your own custom nodes, and publish them to [npm](https://www.npmjs.com/), refer to [Creating nodes](../../creating-nodes/overview/) for more information.\n",
|
|
20777
|
+
"excerpt": "# Built-in integrations This section contains the [node](../../../glossary/#node-n8n) library: reference documentation for every built-in node in n8n, and their credentials. ## Node operations: Triggers and Actions When you add a node to a workflow, n8n displays a list of available operations. An operation is something a node does, such as getting or sending data. There are two types of operation: - Triggers start a workflow in response to specific events or conditions in your services. Whe...",
|
|
20767
20778
|
"sections": [
|
|
20768
20779
|
{
|
|
20769
|
-
"title": "
|
|
20780
|
+
"title": "Built-in integrations",
|
|
20770
20781
|
"level": 1,
|
|
20771
|
-
"content": "[
|
|
20782
|
+
"content": "This section contains the [node](../../../glossary/#node-n8n) library: reference documentation for every built-in node in n8n, and their credentials."
|
|
20772
20783
|
}
|
|
20773
20784
|
]
|
|
20774
20785
|
},
|
|
@@ -20788,6 +20799,97 @@
|
|
|
20788
20799
|
"community"
|
|
20789
20800
|
],
|
|
20790
20801
|
"useCases": [],
|
|
20802
|
+
"operations": [
|
|
20803
|
+
"triggers",
|
|
20804
|
+
"actions",
|
|
20805
|
+
"n8n adds a trigger node to your workflow",
|
|
20806
|
+
"trigger operations have a bolt icon .",
|
|
20807
|
+
"node : triggers and"
|
|
20808
|
+
],
|
|
20809
|
+
"codeExamples": 0,
|
|
20810
|
+
"complexity": "beginner",
|
|
20811
|
+
"readingTime": "2 min",
|
|
20812
|
+
"contentLength": 2719,
|
|
20813
|
+
"relatedPages": []
|
|
20814
|
+
},
|
|
20815
|
+
"searchIndex": {
|
|
20816
|
+
"fullText": "node types # built-in integrations\n\nthis section contains the [node](../../../glossary/#node-n8n) library: reference documentation for every built-in node in n8n, and their credentials.\n\n## node operations: triggers and actions\n\nwhen you add a node to a workflow, n8n displays a list of available operations. an operation is something a node does, such as getting or sending data.\n\nthere are two types of operation:\n\n- triggers start a workflow in response to specific events or conditions in your services. when you select a trigger, n8n adds a trigger node to your workflow, with the trigger operation you chose pre-selected. when you search for a node in n8n, trigger operations have a bolt icon .\n- actions are operations that represent specific tasks within a workflow, which you can use to manipulate data, perform operations on external systems, and trigger events in other systems as part of your workflows. when you select an action, n8n adds a node to your workflow, with the action operation you chose pre-selected.\n\n## core nodes\n\ncore nodes can be actions or [triggers](../../../glossary/#trigger-node-n8n). whereas most nodes connect to a specific external service, core nodes provide functionality such as logic, scheduling, or generic api calls.\n\n## cluster nodes\n\n[cluster nodes](../../../glossary/#cluster-node-n8n) are node groups that work together to provide functionality in an n8n workflow. instead of using a single node, you use a [root node](../../../glossary/#root-node-n8n) and one or more [sub-nodes](../../../glossary/#sub-node-n8n) that extend the functionality of the node.\n\n## credentials\n\nexternal services need a way to identify and authenticate users. this data can range from an api key over an email/password combination to a long multi-line private key. you can save these in n8n as [credentials](../../../glossary/#credential-n8n).\n\nnodes in n8n can then request that credential information. as another layer of security, only node types with specific access rights can access the credentials.\n\nto make sure that the data is secure, it gets saved to the database encrypted. n8n uses a random personal encryption key, which it automatically generates on the first run of n8n and then saved under `~/.n8n/config`.\n\nto learn more about creating, managing, and sharing credentials, refer to [manage credentials](../../../credentials/).\n\n## community nodes\n\nn8n supports custom nodes built by the community. refer to [community nodes](../../community-nodes/installation/) for guidance on installing and using these nodes.\n\nfor help building your own custom nodes, and publish them to [npm](https://www.npmjs.com/), refer to [creating nodes](../../creating-nodes/overview/) for more information.\n built-in integrations",
|
|
20817
|
+
"importantTerms": [
|
|
20818
|
+
"node",
|
|
20819
|
+
"nodes",
|
|
20820
|
+
"credentials",
|
|
20821
|
+
"glossary",
|
|
20822
|
+
"workflow",
|
|
20823
|
+
"trigger",
|
|
20824
|
+
"operations",
|
|
20825
|
+
"your",
|
|
20826
|
+
"that",
|
|
20827
|
+
"built",
|
|
20828
|
+
"when",
|
|
20829
|
+
"operation",
|
|
20830
|
+
"data",
|
|
20831
|
+
"specific",
|
|
20832
|
+
"community",
|
|
20833
|
+
"types",
|
|
20834
|
+
"triggers",
|
|
20835
|
+
"actions",
|
|
20836
|
+
"with",
|
|
20837
|
+
"external",
|
|
20838
|
+
"core",
|
|
20839
|
+
"functionality",
|
|
20840
|
+
"cluster",
|
|
20841
|
+
"more",
|
|
20842
|
+
"creating",
|
|
20843
|
+
"refer"
|
|
20844
|
+
]
|
|
20845
|
+
}
|
|
20846
|
+
},
|
|
20847
|
+
{
|
|
20848
|
+
"id": "page-0240",
|
|
20849
|
+
"title": "Handle rate limits",
|
|
20850
|
+
"url": "https://docs.n8n.io/integrations/builtin/rate-limits/index.md",
|
|
20851
|
+
"urlPath": "integrations/builtin/rate-limits/index.md",
|
|
20852
|
+
"category": "other",
|
|
20853
|
+
"subcategory": null,
|
|
20854
|
+
"nodeName": null,
|
|
20855
|
+
"nodeType": null,
|
|
20856
|
+
"content": {
|
|
20857
|
+
"markdown": "# Handling API rate limits\n\n[API](../../../glossary/#api) rate limits are restrictions on request frequency. For example, an API may limit the number of requests you can make per minute, or per day.\n\nAPIs can also limits how much data you can send in one request, or how much data the API sends in a single response.\n\n## Identify rate limit issues\n\nWhen an n8n node hits a rate limit, it errors. n8n displays the error message in the node output panel. This includes the error message from the service.\n\nIf n8n received error 429 (too many requests) from the service, the error message is **The service is receiving too many requests from you**.\n\nTo check the rate limits for the service you're using, refer to the API documentation for the service.\n\n## Handle rate limits for integrations\n\nThere are two ways to handle rate limits in n8n's integrations: using the Retry On Fail setting, or using a combination of the [Loop Over Items](../core-nodes/n8n-nodes-base.splitinbatches/) and [Wait](../core-nodes/n8n-nodes-base.wait/) nodes:\n\n- Retry On Fail adds a pause between API request attempts.\n- With Loop Over Items and Wait you can break you request data into smaller chunks, as well as pausing between requests.\n\n### Enable Retry On Fail\n\nWhen you enable Retry On Fail, the node automatically tries the request again if it fails the first time.\n\n1. Open the node.\n1. Select **Settings**.\n1. Enable the **Retry On Fail** toggle.\n1. Configure the retry settings: if using this to work around rate limits, set **Wait Between Tries (ms)** to more than the rate limit. For example, if the API you're using allows one request per second, set **Wait Between Tries (ms)** to `1000` to allow a 1 second wait.\n\n### Use Loop Over Items and Wait\n\nUse the Loop Over Items node to batch the input items, and the Wait node to introduce a pause between each request.\n\n1. Add the Loop Over Items node before the node that calls the API. Refer to [Loop Over Items](../core-nodes/n8n-nodes-base.splitinbatches/) for information on how to configure the node.\n1. Add the Wait node after the node that calls the API, and connect it back to the Loop Over Items node. Refer to [Wait](../core-nodes/n8n-nodes-base.wait/) for information on how to configure the node.\n\nFor example, to handle rate limits when using OpenAI:\n\n## Handle rate limits in the HTTP Request node\n\nThe HTTP Request node has built-in settings for handling rate limits and large amounts of data.\n\n### Batch requests\n\nUse the Batching option to send more than one request, reducing the request size, and introducing a pause between requests. This is the equivalent of using Loop Over Items and Wait.\n\n1. In the HTTP Request node, select **Add Option** > **Batching**.\n1. Set **Items per Batch**: this is the number of input items to include in each request.\n1. Set **Batch Interval (ms)** to introduce a delay between requests. For example, if the API you're using allows one request per second, set **Wait Between Tries (ms)** to `1000` to allow a 1 second wait.\n\n### Paginate results\n\nAPIs paginate their results when they need to send more data than they can handle in a single response. For more information on pagination in the HTTP Request node, refer to [HTTP Request node | Pagination](../core-nodes/n8n-nodes-base.httprequest/#pagination).\n",
|
|
20858
|
+
"excerpt": "# Handling API rate limits [API](../../../glossary/#api) rate limits are restrictions on request frequency. For example, an API may limit the number of requests you can make per minute, or per day. APIs can also limits how much data you can send in one request, or how much data the API sends in a single response. ## Identify rate limit issues When an n8n node hits a rate limit, it errors. n8n displays the error message in the node output panel. This includes the error message from the servic...",
|
|
20859
|
+
"sections": [
|
|
20860
|
+
{
|
|
20861
|
+
"title": "Handling API rate limits",
|
|
20862
|
+
"level": 1,
|
|
20863
|
+
"content": "[API](../../../glossary/#api) rate limits are restrictions on request frequency. For example, an API may limit the number of requests you can make per minute, or per day.\n\nAPIs can also limits how much data you can send in one request, or how much data the API sends in a single response."
|
|
20864
|
+
}
|
|
20865
|
+
]
|
|
20866
|
+
},
|
|
20867
|
+
"metadata": {
|
|
20868
|
+
"keywords": [
|
|
20869
|
+
"handle",
|
|
20870
|
+
"rate",
|
|
20871
|
+
"limits",
|
|
20872
|
+
"handling",
|
|
20873
|
+
"identify",
|
|
20874
|
+
"limit",
|
|
20875
|
+
"issues",
|
|
20876
|
+
"integrations",
|
|
20877
|
+
"enable",
|
|
20878
|
+
"retry",
|
|
20879
|
+
"fail",
|
|
20880
|
+
"loop",
|
|
20881
|
+
"over",
|
|
20882
|
+
"items",
|
|
20883
|
+
"wait",
|
|
20884
|
+
"http",
|
|
20885
|
+
"request",
|
|
20886
|
+
"node",
|
|
20887
|
+
"batch",
|
|
20888
|
+
"requests",
|
|
20889
|
+
"paginate",
|
|
20890
|
+
"results"
|
|
20891
|
+
],
|
|
20892
|
+
"useCases": [],
|
|
20791
20893
|
"operations": [],
|
|
20792
20894
|
"codeExamples": 0,
|
|
20793
20895
|
"complexity": "beginner",
|
|
@@ -20796,12 +20898,12 @@
|
|
|
20796
20898
|
"relatedPages": []
|
|
20797
20899
|
},
|
|
20798
20900
|
"searchIndex": {
|
|
20799
|
-
"fullText": "
|
|
20901
|
+
"fullText": "handle rate limits # handling api rate limits\n\n[api](../../../glossary/#api) rate limits are restrictions on request frequency. for example, an api may limit the number of requests you can make per minute, or per day.\n\napis can also limits how much data you can send in one request, or how much data the api sends in a single response.\n\n## identify rate limit issues\n\nwhen an n8n node hits a rate limit, it errors. n8n displays the error message in the node output panel. this includes the error message from the service.\n\nif n8n received error 429 (too many requests) from the service, the error message is **the service is receiving too many requests from you**.\n\nto check the rate limits for the service you're using, refer to the api documentation for the service.\n\n## handle rate limits for integrations\n\nthere are two ways to handle rate limits in n8n's integrations: using the retry on fail setting, or using a combination of the [loop over items](../core-nodes/n8n-nodes-base.splitinbatches/) and [wait](../core-nodes/n8n-nodes-base.wait/) nodes:\n\n- retry on fail adds a pause between api request attempts.\n- with loop over items and wait you can break you request data into smaller chunks, as well as pausing between requests.\n\n### enable retry on fail\n\nwhen you enable retry on fail, the node automatically tries the request again if it fails the first time.\n\n1. open the node.\n1. select **settings**.\n1. enable the **retry on fail** toggle.\n1. configure the retry settings: if using this to work around rate limits, set **wait between tries (ms)** to more than the rate limit. for example, if the api you're using allows one request per second, set **wait between tries (ms)** to `1000` to allow a 1 second wait.\n\n### use loop over items and wait\n\nuse the loop over items node to batch the input items, and the wait node to introduce a pause between each request.\n\n1. add the loop over items node before the node that calls the api. refer to [loop over items](../core-nodes/n8n-nodes-base.splitinbatches/) for information on how to configure the node.\n1. add the wait node after the node that calls the api, and connect it back to the loop over items node. refer to [wait](../core-nodes/n8n-nodes-base.wait/) for information on how to configure the node.\n\nfor example, to handle rate limits when using openai:\n\n## handle rate limits in the http request node\n\nthe http request node has built-in settings for handling rate limits and large amounts of data.\n\n### batch requests\n\nuse the batching option to send more than one request, reducing the request size, and introducing a pause between requests. this is the equivalent of using loop over items and wait.\n\n1. in the http request node, select **add option** > **batching**.\n1. set **items per batch**: this is the number of input items to include in each request.\n1. set **batch interval (ms)** to introduce a delay between requests. for example, if the api you're using allows one request per second, set **wait between tries (ms)** to `1000` to allow a 1 second wait.\n\n### paginate results\n\napis paginate their results when they need to send more data than they can handle in a single response. for more information on pagination in the http request node, refer to [http request node | pagination](../core-nodes/n8n-nodes-base.httprequest/#pagination).\n handling api rate limits",
|
|
20800
20902
|
"importantTerms": [
|
|
20801
20903
|
"node",
|
|
20802
20904
|
"request",
|
|
20803
|
-
"wait",
|
|
20804
20905
|
"rate",
|
|
20906
|
+
"wait",
|
|
20805
20907
|
"limits",
|
|
20806
20908
|
"items",
|
|
20807
20909
|
"nodes",
|
|
@@ -20810,10 +20912,10 @@
|
|
|
20810
20912
|
"over",
|
|
20811
20913
|
"between",
|
|
20812
20914
|
"requests",
|
|
20915
|
+
"handle",
|
|
20813
20916
|
"retry",
|
|
20814
20917
|
"data",
|
|
20815
20918
|
"service",
|
|
20816
|
-
"handle",
|
|
20817
20919
|
"fail",
|
|
20818
20920
|
"core",
|
|
20819
20921
|
"base",
|
|
@@ -94290,6 +94392,7 @@
|
|
|
94290
94392
|
"page-0218",
|
|
94291
94393
|
"page-0230",
|
|
94292
94394
|
"page-0239",
|
|
94395
|
+
"page-0240",
|
|
94293
94396
|
"page-0242",
|
|
94294
94397
|
"page-0243",
|
|
94295
94398
|
"page-0244",
|
|
@@ -95480,6 +95583,7 @@
|
|
|
95480
95583
|
"page-0070",
|
|
95481
95584
|
"page-0079",
|
|
95482
95585
|
"page-0080",
|
|
95586
|
+
"page-0240",
|
|
95483
95587
|
"page-0506",
|
|
95484
95588
|
"page-0540",
|
|
95485
95589
|
"page-0544",
|
|
@@ -95565,6 +95669,7 @@
|
|
|
95565
95669
|
"page-0012",
|
|
95566
95670
|
"page-0026",
|
|
95567
95671
|
"page-0102",
|
|
95672
|
+
"page-0240",
|
|
95568
95673
|
"page-0355",
|
|
95569
95674
|
"page-0381",
|
|
95570
95675
|
"page-0501",
|
|
@@ -96101,6 +96206,7 @@
|
|
|
96101
96206
|
"page-0224",
|
|
96102
96207
|
"page-0226",
|
|
96103
96208
|
"page-0233",
|
|
96209
|
+
"page-0240",
|
|
96104
96210
|
"page-0577",
|
|
96105
96211
|
"page-0580",
|
|
96106
96212
|
"page-0883",
|
|
@@ -99982,6 +100088,7 @@
|
|
|
99982
100088
|
"page-0013",
|
|
99983
100089
|
"page-0020",
|
|
99984
100090
|
"page-0138",
|
|
100091
|
+
"page-0240",
|
|
99985
100092
|
"page-0699"
|
|
99986
100093
|
],
|
|
99987
100094
|
"calls": [
|
|
@@ -102372,6 +102479,7 @@
|
|
|
102372
102479
|
"page-0018",
|
|
102373
102480
|
"page-0066",
|
|
102374
102481
|
"page-0136",
|
|
102482
|
+
"page-0240",
|
|
102375
102483
|
"page-0687",
|
|
102376
102484
|
"page-1156",
|
|
102377
102485
|
"page-1179",
|
|
@@ -102881,6 +102989,7 @@
|
|
|
102881
102989
|
"results": [
|
|
102882
102990
|
"page-0024",
|
|
102883
102991
|
"page-0026",
|
|
102992
|
+
"page-0240",
|
|
102884
102993
|
"page-0558",
|
|
102885
102994
|
"page-0559",
|
|
102886
102995
|
"page-0560",
|
|
@@ -104538,6 +104647,7 @@
|
|
|
104538
104647
|
],
|
|
104539
104648
|
"limits": [
|
|
104540
104649
|
"page-0052",
|
|
104650
|
+
"page-0240",
|
|
104541
104651
|
"page-1006",
|
|
104542
104652
|
"page-1208",
|
|
104543
104653
|
"page-1211"
|
|
@@ -105429,6 +105539,7 @@
|
|
|
105429
105539
|
"page-0070",
|
|
105430
105540
|
"page-0079",
|
|
105431
105541
|
"page-0080",
|
|
105542
|
+
"page-0240",
|
|
105432
105543
|
"page-0635",
|
|
105433
105544
|
"page-0678",
|
|
105434
105545
|
"page-0707",
|
|
@@ -105443,6 +105554,7 @@
|
|
|
105443
105554
|
],
|
|
105444
105555
|
"requests": [
|
|
105445
105556
|
"page-0053",
|
|
105557
|
+
"page-0240",
|
|
105446
105558
|
"page-0422",
|
|
105447
105559
|
"page-0502",
|
|
105448
105560
|
"page-0544",
|
|
@@ -105527,6 +105639,7 @@
|
|
|
105527
105639
|
"page-0111",
|
|
105528
105640
|
"page-0112",
|
|
105529
105641
|
"page-0138",
|
|
105642
|
+
"page-0240",
|
|
105530
105643
|
"page-0683",
|
|
105531
105644
|
"page-0687",
|
|
105532
105645
|
"page-0699",
|
|
@@ -109613,6 +109726,7 @@
|
|
|
109613
109726
|
"integrations": [
|
|
109614
109727
|
"page-0236",
|
|
109615
109728
|
"page-0239",
|
|
109729
|
+
"page-0240",
|
|
109616
109730
|
"page-0891",
|
|
109617
109731
|
"page-0914"
|
|
109618
109732
|
],
|
|
@@ -109969,6 +110083,54 @@
|
|
|
109969
110083
|
"page-0239",
|
|
109970
110084
|
"page-1270"
|
|
109971
110085
|
],
|
|
110086
|
+
"handle": [
|
|
110087
|
+
"page-0240",
|
|
110088
|
+
"page-0527"
|
|
110089
|
+
],
|
|
110090
|
+
"rate": [
|
|
110091
|
+
"page-0240",
|
|
110092
|
+
"page-1006"
|
|
110093
|
+
],
|
|
110094
|
+
"identify": [
|
|
110095
|
+
"page-0240"
|
|
110096
|
+
],
|
|
110097
|
+
"limit": [
|
|
110098
|
+
"page-0240",
|
|
110099
|
+
"page-0568",
|
|
110100
|
+
"page-0576",
|
|
110101
|
+
"page-0640",
|
|
110102
|
+
"page-0683",
|
|
110103
|
+
"page-0707",
|
|
110104
|
+
"page-0813",
|
|
110105
|
+
"page-1221"
|
|
110106
|
+
],
|
|
110107
|
+
"retry": [
|
|
110108
|
+
"page-0240",
|
|
110109
|
+
"page-0723",
|
|
110110
|
+
"page-1273",
|
|
110111
|
+
"page-1279"
|
|
110112
|
+
],
|
|
110113
|
+
"fail": [
|
|
110114
|
+
"page-0240",
|
|
110115
|
+
"page-0723"
|
|
110116
|
+
],
|
|
110117
|
+
"over": [
|
|
110118
|
+
"page-0240",
|
|
110119
|
+
"page-0699"
|
|
110120
|
+
],
|
|
110121
|
+
"wait": [
|
|
110122
|
+
"page-0240",
|
|
110123
|
+
"page-0509",
|
|
110124
|
+
"page-0538",
|
|
110125
|
+
"page-0707"
|
|
110126
|
+
],
|
|
110127
|
+
"batch": [
|
|
110128
|
+
"page-0240",
|
|
110129
|
+
"page-0699"
|
|
110130
|
+
],
|
|
110131
|
+
"paginate": [
|
|
110132
|
+
"page-0240"
|
|
110133
|
+
],
|
|
109972
110134
|
"action": [
|
|
109973
110135
|
"page-0242",
|
|
109974
110136
|
"page-0538",
|
|
@@ -111446,11 +111608,6 @@
|
|
|
111446
111608
|
"page-0538",
|
|
111447
111609
|
"page-0696"
|
|
111448
111610
|
],
|
|
111449
|
-
"wait": [
|
|
111450
|
-
"page-0509",
|
|
111451
|
-
"page-0538",
|
|
111452
|
-
"page-0707"
|
|
111453
|
-
],
|
|
111454
111611
|
"thread": [
|
|
111455
111612
|
"page-0510"
|
|
111456
111613
|
],
|
|
@@ -111585,9 +111742,6 @@
|
|
|
111585
111742
|
"page-0527",
|
|
111586
111743
|
"page-1271"
|
|
111587
111744
|
],
|
|
111588
|
-
"handle": [
|
|
111589
|
-
"page-0527"
|
|
111590
|
-
],
|
|
111591
111745
|
"null": [
|
|
111592
111746
|
"page-0527"
|
|
111593
111747
|
],
|
|
@@ -112130,15 +112284,6 @@
|
|
|
112130
112284
|
"fusion": [
|
|
112131
112285
|
"page-0568"
|
|
112132
112286
|
],
|
|
112133
|
-
"limit": [
|
|
112134
|
-
"page-0568",
|
|
112135
|
-
"page-0576",
|
|
112136
|
-
"page-0640",
|
|
112137
|
-
"page-0683",
|
|
112138
|
-
"page-0707",
|
|
112139
|
-
"page-0813",
|
|
112140
|
-
"page-1221"
|
|
112141
|
-
],
|
|
112142
112287
|
"alpha": [
|
|
112143
112288
|
"page-0568",
|
|
112144
112289
|
"page-1221"
|
|
@@ -112838,18 +112983,12 @@
|
|
|
112838
112983
|
"arrays": [
|
|
112839
112984
|
"page-0697"
|
|
112840
112985
|
],
|
|
112841
|
-
"over": [
|
|
112842
|
-
"page-0699"
|
|
112843
|
-
],
|
|
112844
112986
|
"(split": [
|
|
112845
112987
|
"page-0699"
|
|
112846
112988
|
],
|
|
112847
112989
|
"batches)": [
|
|
112848
112990
|
"page-0699"
|
|
112849
112991
|
],
|
|
112850
|
-
"batch": [
|
|
112851
|
-
"page-0699"
|
|
112852
|
-
],
|
|
112853
112992
|
"reset": [
|
|
112854
112993
|
"page-0699"
|
|
112855
112994
|
],
|
|
@@ -113002,14 +113141,6 @@
|
|
|
113002
113141
|
"could": [
|
|
113003
113142
|
"page-0723"
|
|
113004
113143
|
],
|
|
113005
|
-
"retry": [
|
|
113006
|
-
"page-0723",
|
|
113007
|
-
"page-1273",
|
|
113008
|
-
"page-1279"
|
|
113009
|
-
],
|
|
113010
|
-
"fail": [
|
|
113011
|
-
"page-0723"
|
|
113012
|
-
],
|
|
113013
113144
|
"duplicates": [
|
|
113014
113145
|
"page-0724",
|
|
113015
113146
|
"page-0725",
|
|
@@ -113453,9 +113584,6 @@
|
|
|
113453
113584
|
"trellix": [
|
|
113454
113585
|
"page-1001"
|
|
113455
113586
|
],
|
|
113456
|
-
"rate": [
|
|
113457
|
-
"page-1006"
|
|
113458
|
-
],
|
|
113459
113587
|
"typeform": [
|
|
113460
113588
|
"page-1007",
|
|
113461
113589
|
"page-1131"
|
|
@@ -114590,6 +114718,7 @@
|
|
|
114590
114718
|
"page-0237",
|
|
114591
114719
|
"page-0238",
|
|
114592
114720
|
"page-0239",
|
|
114721
|
+
"page-0240",
|
|
114593
114722
|
"page-0654",
|
|
114594
114723
|
"page-0655",
|
|
114595
114724
|
"page-0656",
|