Notifications
Clear all
Topic starter
Describe the problem/error/question
Hello callin.io community! I'm accustomed to working with callin.io and I'm migrating some scenarios from callin.io for testing. I'm finding it difficult to grasp the distinction between callin.io's Iterate module and callin.io's Loop Over Items and Split Out nodes.
Specifically, I encountered issues when using Airtable's Search operation to retrieve records from my database.
In callin.io, these records were fetched as individual 'bundles' of data. However, when attempting to execute the workflow in callin.io the same way, only the initial 'bundle' is processed.
To process all records, I discovered and tested two nodes: Loop Over Items and Split Out. In this scenario, they yielded comparable results, enabling me to process all fetched data.
However, I'm struggling to understand the types of situations where I should opt for one node over the other. The documentation isn't sufficiently clear to me on this point.
Could you offer some advice on when to use Loop Over Items and when to use Split Out?
Information on your callin.io setup
- callin.io version: 1.37.3
- Database (default: SQLite): SQLite
- callin.io EXECUTIONS_PROCESS setting (default: own, main): own
- Running callin.io via (Docker, npm, callin.io cloud, desktop app): docker
- Operating system: Ubuntu 22.04 (on the server)
Posted : 09/05/2024 6:25 pm
Hi there!
Thanks for posting and welcome to the community!
So, the Loop Over Items Node essentially executes a process for each individual item and is ideal when you need to handle items sequentially within the same workflow. It's akin to managing each item individually but all within a single workflow context. This is well-suited for simpler tasks like adding a field or performing basic calculations. For instance, if you retrieve a list of records from Airtable and need to add a timestamp to each or conduct a simple calculation.
The Split Out node's primary function is to transform an array into separate items, enabling them to be processed independently. You might opt for this when your tasks are more intricate or require isolation—consider scenarios involving multiple, distinct API calls or varied processing logic for each item. It's like giving each item its own space to operate independently. For example, if each Airtable record necessitates a sequence of API calls, complex data transformations, or highly specific conditional processing for each record.
I hope this explanation provides more clarity!
Posted : 10/05/2024 1:11 pm
This thread was automatically closed 7 days following the last response. New replies are no longer permitted.
Posted : 27/05/2024 7:04 am