---
title: "Use a loop in the bulk trigger step"
slug: "use-a-loop-in-the-bulk-trigger-step"
updated: 2026-06-01T16:17:58Z
published: 2026-06-01T16:17:58Z
canonical: "help.quickbase.com/use-a-loop-in-the-bulk-trigger-step"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.quickbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use a loop in the bulk trigger step

The output of the bulk trigger step is an array of data. To process the data, use a loop to iterate through each record in the array and perform an appropriate action. The loop is automatically attached to the bulk trigger step when you select it for the first time.

In this example, we use the bulk trigger to transfer records from one table to another:

![Bulk trigger pipeline example](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/38700692819092.png)

We create the pipeline using these steps:

1. An **On New Bulk Event** step that receives a large amount of changes at once.
2. A **Bulk Record Upsert** step that specifies the table where we would like to transfer the records to.
3. A **Loop**, which processes each record that is outputted from the **On New Bulk Event** step. For example, if 1,000 records are sent to the pipeline, any action inside the loop will run 1,000 times.
4. Inside the loop, we can perform any modifications to the records that we would like. In this example, we use an **Add a Bulk Upsert Row** step to prepare the record to be uploaded to the other table.
5. Outside of the loop, we use the **Commit Upsert** step to start the bulk import into the other table.

> [!NOTE]
> Note
> 
> The loop for the **On New Bulk Event** bulk trigger processes records in sequence. This means that the order of the records that you received with the trigger are kept as is and are transferred to other tables without any shuffling.
