# Batch triggers

**Batch triggers** let you trigger multiple runs for a single workflow at once. Unlike the [Looping over a list \*inside\* a workflow](/flow-control/iterators.md), Batch Triggers aren't restricted in terms of how many runs they can start.

## About batch triggers

You will find batch triggers inside the trigger menu for each app. Below the list of regular "event-based" triggers, you'll find a list of the supported batch triggers for that app.

Apps typically only have one batch trigger option available, but some have multiple types.

<figure><img src="/files/FRkWYK6nc4kIERCNODO1" alt="Google Sheets has one Batch Trigger: to start runs for every row in a spreadsheet that matches your filter"><figcaption><p>Google Sheets has one Batch Trigger: to start runs for every row in a spreadsheet that matches your filter</p></figcaption></figure>

<figure><img src="/files/4GjRqHaYD0yecrhqncrv" alt="Asana has multiple Batch Triggers"><figcaption><p>Asana has multiple Batch Triggers</p></figcaption></figure>

## Setting up a batch trigger

### 1. Configure it to start on demand or on a recurring schedule

When selecting a batch trigger, you'll first need to select whether you will want to

* Manually kick off the batch every time "on demand," or
* Start a batch of runs on a recurring schedule (e.g. every day/month/etc) ([more here](#id-3.-recurring-only-specify-the-schedule))

<div align="left"><figure><img src="/files/kzKUH6ifGWVMsOksN5tF" alt="" width="375"><figcaption></figcaption></figure></div>

### 2. Specify for which items it should start runs

First, select whether runs should be started for every item (e.g. every row in the selected spreadsheet), or only a subset. Typically you'll want to only run for a subset, and specify filters.

<div align="left"><figure><img src="/files/YAqRlsek93rQZRYeIyF2" alt="" width="375"><figcaption></figcaption></figure></div>

If you've selected to only trigger runs for a subset of items, you'll need to specify filters. The "Preview" area below it will show a preview of the items that match your filters and that it would trigger runs for.

<div align="left"><figure><img src="/files/GXkOkUr8lyC0Lg6T5liw" alt="" width="375"><figcaption></figcaption></figure></div>

### 3a. \[Recurring only] Specify the schedule

If you've selected a recurring batch trigger [above](#id-1.-configure-it-to-start-on-demand-or-on-a-recurring-schedule), specify the recurring schedule below the Preview section:

<div align="left"><figure><img src="/files/zaHAdoHX8j5G941BdTmY" alt="" width="375"><figcaption></figcaption></figure></div>

### 3b. Starting a batch on demand/manually

To start a batch manually, click 'Start batch' in the header of the trigger. Note: This button will only appear when you have a complete workflow set up (i.e. there are steps and no errors).

<div align="left"><figure><img src="/files/lNJGr17DjmUkzi74F9ao" alt="" width="375"><figcaption></figcaption></figure></div>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.relay.app/triggers/batch-triggers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
