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

# Execute entity transformers

> Executes one or more entity transformers in sequence.

export const FormField = ({property, label, required = false, diType, uiPatterns, children}) => {
  const patterns = Array.isArray(uiPatterns) ? uiPatterns : uiPatterns ? [uiPatterns] : [];
  return <div style={{
    margin: '1.5rem 0'
  }}>
      <div style={{
    display: 'flex',
    alignItems: 'baseline',
    flexWrap: 'wrap',
    gap: '0.5rem',
    marginBottom: '0.25rem'
  }}>
        <strong>{label}</strong>
        <span style={{
    fontSize: '0.7rem',
    fontWeight: 600,
    textTransform: 'uppercase',
    letterSpacing: '0.04em',
    color: required ? '#6241f5' : '#6b7280'
  }}>
          {required ? 'Required' : 'Optional'}
        </span>
      </div>

      <div>{children}</div>

      {diType || patterns.length > 0 ? <p style={{
    fontSize: '0.85rem',
    color: '#6b7280',
    marginBottom: 0
  }}>
          {diType ? <>
              See the <a href={`/references/${diType}`}>{diType}</a> reference.{' '}
            </> : null}
          {patterns.length > 0 ? <>
              Accepts a <a href={`/documentation/placeholders-and-patterns/patterns#${patterns[0]}`}>pattern</a>.
            </> : null}
        </p> : null}
    </div>;
};

Lets you use entity transformers in a place that normally only accepts a regular data transformer. Some features, such as an HTTP proxy step, only offer a single data transformer slot, while a few transformations are built to work on whole entities instead. This feature bridges that gap: you drop it into the data transformer slot, add the entity transformers you need inside it, and it runs them in order on the current item. When they finish, it hands the result back as a single entity so the rest of your flow continues normally. It expects exactly one entity to come back out; if a step removes the item or produces more than one, it stops with an error.

This documentation describes: [Schema](/schemas/transformer/list-transformer-wrapper)

## Fields

<FormField property="transformers" label="Entity transformers" diType="list-transformer">
  The entity transformers to run, in order. Each one receives the item as the step before it left it. These are entity transformers (the kind that work on whole entities), not the regular data transformers you pick elsewhere. See [Entity transformers](/references/list-transformer) for the options you can add here.
</FormField>

## Sample data

This feature is a wrapper: it does not change data on its own, it simply runs the entity transformers you put inside it. What the result looks like depends entirely on those inner transformers, so there is no before/after of its own to show. The configuration below shows the shape: the wrapper holds one entity transformer in its list.

```json Configuration theme={null}
{
  "prototype": "list-transformer-wrapper",
  "parameters": {
    "transformers": [
      {
        "prototype": "<entity-transformer>",
        "parameters": {}
      }
    ]
  }
}
```