You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/integrations/builtin/core-nodes/n8n-nodes-base.splitinbatches.md
+20-5
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,16 @@ The Loop Over Items node helps you loop through data.
12
12
13
13
The node saves the original incoming data, and with each iteration, returns a predefined amount of data through the **loop** output.
14
14
15
-
When the node execution completes, it combines all the data and returns it through the **done** output.
15
+
When the node execution completes, it combines all of the processed data and returns it through the **done** output.
16
+
17
+
## When to use the Loop Over Items node
18
+
19
+
n8n automatically processes incoming items. Depending on what you're trying to achieve, you often don't need the Loop Over Items node in your workflow. You can learn more about how n8n processes multiple items on the [looping in n8n](/flow-logic/looping.md) page.
20
+
21
+
In particular, these two sections are of particular interest to the Loop Over Items node:
22
+
23
+
*[Loop until all items are processed](/flow-logic/looping.md#loop-until-all-items-are-processed): describes how the Loop Over Items node differs from normal item processing and when you might want to incorporate this node.
24
+
*[Node exceptions](/flow-logic/looping.md#node-exceptions): outlines specific cases and nodes where you may need to use the Loop Over Items node to manually build looping logic.
16
25
17
26
## Node parameters
18
27
@@ -24,12 +33,16 @@ Enter the number of items to return with each call.
24
33
25
34
### Reset
26
35
27
-
If turned on, the node will reset with the current input-data newly initialized with each loop.
36
+
If turned on, the node will reset with the current input-data newly initialized with each loop. Use this when you want the Loop Over Items node to treat incoming data as a new set of data instead of a continuation of previous items.
28
37
29
-
/// note | Check if you need this node
30
-
n8n automatically processes incoming items. You may not need the Loop Over Items node in your workflow. To learn more about how n8n handles multiple items, refer to the documentation on [Looping in n8n](/flow-logic/looping.md).
38
+
For example, you can use the Loop Over Items node with the reset option and an [If node](/integrations/builtin/core-nodes/n8n-nodes-base.if.md) to query a paginated service when you don't know how many pages you need in advance. The loop queries pages one at a time, performs any processing, and increments the page number. The loop reset ensures the loop recognizes each iteration as a new set of data. The If node evaluates an exit condition to decide whether to perform another iteration or not.
39
+
40
+
/// warning | Include a valid termination condition
41
+
For workflows like the example described above, it's critical to include a valid termination condition for the loop. If your termination condition never matches, your workflow execution will get stuck in an infinite loop.
31
42
///
32
43
44
+
When enabled, you can adjust the reset conditions by switching the parameter representation from **Fixed** to **Expression**. The results of your expression evaluation determine when the node will reset item processing.
45
+
33
46
## Templates and examples
34
47
35
48
<!-- see https://www.notion.so/n8n/Pull-in-templates-for-the-integrations-pages-37c716837b804d30a33b47475f6e3780 -->
@@ -43,7 +56,9 @@ The example walks through building the workflow, but assumes you are already fam
43
56
44
57
The final workflow looks like this:
45
58
46
-
Copy file name to clipboardExpand all lines: docs/integrations/builtin/trigger-nodes/n8n-nodes-base.airtabletrigger.md
+58-3
Original file line number
Diff line number
Diff line change
@@ -10,11 +10,66 @@ priority: medium
10
10
11
11
[Airtable](https://airtable.com/){:target=_blank .external-link} is a spreadsheet-database hybrid, with the features of a database but applied to a spreadsheet. The fields in an Airtable table are similar to cells in a spreadsheet, but have types such as 'checkbox', 'phone number', and 'drop-down list', and can reference file attachments like images.
12
12
13
+
On this page, you'll find a list of events the Airtable Trigger node can respond to and links to more resources.
14
+
13
15
/// note | Credentials
14
16
You can find authentication information for this node [here](/integrations/builtin/credentials/airtable.md).
15
17
///
16
18
17
-
/// note | Examples and templates
18
-
For usage examples and templates to help you get started, refer to n8n's [Airtable Trigger integrations](https://n8n.io/integrations/airtable-trigger/){:target=_blank .external-link} page.
19
-
///
19
+
## Events
20
+
21
+
***New Airtable event**
22
+
23
+
## Related resources
24
+
25
+
n8n provides an app node for Airtable. You can find the node docs [here](/integrations/builtin/app-nodes/n8n-nodes-base.airtable/index.md).
26
+
27
+
View [example workflows and related content](https://n8n.io/integrations/airtable-trigger/) on n8n's website.
28
+
29
+
Refer to [Airtable's documentation](https://airtable.com/developers/web/api/introduction) for details about their API.
30
+
31
+
## Node parameters
32
+
33
+
Use these parameters to configure your node.
34
+
35
+
### Poll Times
36
+
37
+
n8n's Airtable node uses polling for check for updates on configured Airtable resources. The **Poll Times** parameter configures the querying frequency:
38
+
39
+
* Every Minute
40
+
* Every Hour
41
+
* Every Day
42
+
* Every Week
43
+
* Every Month
44
+
* Every X: Check for updates every given number of minutes or hours.
45
+
* Custom: Customize the polling interval by providing a [cron expression](https://en.wikipedia.org/wiki/Cron).
46
+
47
+
Use the **Add Poll Time** button to add more polling intervals.
48
+
49
+
### Base
50
+
51
+
The [Airtable base](https://support.airtable.com/docs/airtable-bases-overview) you want to check for updates on. You can provide your base's URL or [base ID](https://support.airtable.com/docs/finding-airtable-ids#finding-base-table-and-view-ids-from-urls).
52
+
53
+
### Table
54
+
55
+
The [Airtable table](https://support.airtable.com/docs/tables-overview) within the Airtable base that you want to check for updates on. You can provide the table's URL or [table ID](https://support.airtable.com/docs/finding-airtable-ids#finding-base-table-and-view-ids-from-urls).
56
+
57
+
### Trigger Field
58
+
59
+
A created or last modified field in your table. The Airtable Trigger node uses this to determine what updates occurred since the previous check.
60
+
61
+
### Download Attachments
62
+
63
+
Whether to download attachments from the table. When enabled, the **Download Fields** parameter defines the attachment fields.
64
+
65
+
### Download Fields
66
+
67
+
When you enable the **Download Attachments** toggle, this field defines which table fields to download. Field names are case sensitive. Use a comma to separate multiple field names.
68
+
69
+
### Additional Fields
70
+
71
+
Use the **Add Field** button to add the following parameters:
20
72
73
+
***Fields**: A comma-separated list of fields to include in the output. If you don't specify anything here, the output will contain only the **Trigger Field**.
74
+
***Formula**: An [Airtable formula](https://support.airtable.com/docs/formula-field-reference) to further filter the results. You can use this to add further constraints to the events that trigger the workflow. Note that formula values aren't taken into account for manual executions, only for production polling.
75
+
***View ID**: The name or ID of a table view. When defined, only returns records available in the given view.
0 commit comments