# for_each

> For the complete documentation index, see [llms.txt](https://docs.redpanda.com/llms.txt). Component-specific: [cloud-data-platform-full.txt](https://docs.redpanda.com/cloud-data-platform-full.txt)

---
title: for_each
latest-operator-version: v26.1.4
latest-console-tag: v3.7.3
latest-connect-version: 4.93.0
latest-redpanda-tag: v26.1.9
docname: connect/components/processors/for_each
page-component-name: cloud-data-platform
page-version: master
page-component-version: master
page-component-title: Cloud
page-relative-src-path: connect/components/processors/for_each.adoc
page-edit-url: https://github.com/redpanda-data/cloud-docs/edit/main/modules/develop/pages/connect/components/processors/for_each.adoc
page-git-created-date: "2024-09-09"
page-git-modified-date: "2026-05-26"
---

<!-- Source: https://docs.redpanda.com/cloud-data-platform/develop/connect/components/processors/for_each.md -->

**Available in:** Cloud, [Self-Managed](https://docs.redpanda.com/connect/components/processors/for_each/%20%22View%20the%20Self-Managed%20version%20of%20this%20component%22)

A processor that applies a list of child processors to messages of a batch as though they were each a batch of one message.

```yml
# Config fields, showing default values
label: ""
for_each: []
```

This is useful for forcing batch wide processors such as [`dedupe`](https://docs.redpanda.com/cloud-data-platform/develop/connect/components/processors/dedupe/) or interpolations such as the `value` field of the `metadata` processor to execute on individual message parts of a batch instead.

Please note that most processors already process per message of a batch, and this processor is not needed in those cases.