Looping

Looping is beneficial for processing multiple items or actions repeatedly. Appizap Workflow Builder automatically handles repetitive processing, eliminating the need to manually include loops in workflows. However, there are some nodes where this automatic handling does not apply.

• Appizap Workflow Builder nodes can take multiple items as input, process them, and produce results.

• Each item can be seen as a single data point or row in the output table of a node.

Nodes typically run once per item. For instance, to share customer names and notes from the Customer Datastore node in a Slack message, follow these steps:

1. Connect the Slack node to the Customer Datastore node.

2. Configure the parameters.

3. Execute the node.

You would receive five messages: one for each item.

Executing nodes once

In cases where you only want a node to handle certain items, such as sending a Slack message to just the first customer, you can use the Execute Once parameter in the node's Settings tab. This parameter is useful when you have multiple items in the incoming data and only want to process the first item.

Creating loops

Appizap Workflow Builder usually manages the iteration of incoming items. But sometimes you might need to create a loop to iterate through all items. Check Node exceptions for nodes that don't automatically iterate over all incoming items.

To make a loop in an Appizap Workflow Builder workflow, link one node's output to the previous node's input. Include an IF node to determine when to end the loop.

Refer sample here

The Loop Over Items node is used to loop through all items for processing. Set Batch Size to 1 to process each item individually.

You can group data and process it in batches to avoid API rate limits when handling large amounts of data or specific items.

The Loop Over Items node stops running when items are divided into batches and sent to the next node. Adding an IF node to stop the loop is not needed.

Node exceptions

• CrateDB executes once for insert and update.
• Code node in Run Once for All Items mode: processes all the items based on the entered code snippet.
• Execute Workflow node in Run Once for All Items mode.
• HTTP Request: you must handle pagination yourself. If your API call returns paginated results you must create a loop to fetch one page at a time.
• Microsoft SQL executes once for insert, update, and delete.
• MongoDB executes once for insert and update.
• QuestDB executes once for insert.
• Redis:

  • Info: this operation executes only once, regardless of the number of items in the incoming data.

• TimescaleDB executes once for insert and update.