> For the complete documentation index, see [llms.txt](https://docs.brigge.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brigge.ai/documentation/brigge-for-transformers/pipelines/pipeline-nodes/set-meta-node.md).

# Set meta node

## Overview

Metadata is data that is stored *about* a payload, not the payload content itself. Metadata values can be defined in the *Set meta* node and applied to incoming payloads when they pass through. You can view metadata at the top of output payloads, for example:

<div align="left" data-with-frame="true"><figure><img src="https://2172380191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8IqdqwZowcxtFpZfLa6k%2Fuploads%2FcUTTw23UwrAtF2dXFTLv%2Fmetadata%20in%20payloads.svg?alt=media&amp;token=6a2d37c3-c0f7-4c46-a775-4efe62bd4d6b" alt=""><figcaption></figcaption></figure></div>

Typically, you would use this node to attach metadata that you need to use later in the pipeline.

## Configuring a set meta node

You can configure a *Set meta* node [manually](#adding-meta-items-manually) (inputting key names and values) and/or via a [schema](#adding-meta-items-from-a-schema) (if you want to resolve metadata values from incoming payloads). You can also [transform](#transforming-meta-items) metadata values for onward processing:

<div align="left" data-with-frame="true"><figure><img src="https://2172380191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8IqdqwZowcxtFpZfLa6k%2Fuploads%2F4m4Eeg2l3qxvHuPxpleI%2FSet%20meta%20options%202.svg?alt=media&amp;token=2cb2ffc7-ec22-4416-890f-ab82690d4ed3" alt=""><figcaption></figcaption></figure></div>

Metadata is defined in key/value pairs. You can add static metadata values, or include [payload/system variables](/documentation/brigge-for-transformers/pipelines/pipeline-variables.md) (resolving metadata values at runtime):

<div data-with-frame="true"><figure><img src="https://2172380191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8IqdqwZowcxtFpZfLa6k%2Fuploads%2FwDmJOGHQKW8YAxUiU4ER%2FSet%20metadata.svg?alt=media&amp;token=a4390a0c-82d4-46cb-96ba-7acef8e58f35" alt=""><figcaption></figcaption></figure></div>

### Adding meta items manually

If your metadata values are static text, or you know exactly what variable notation to enter, you can update key and value fields directly. For example:

<div data-with-frame="true"><figure><img src="https://2172380191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8IqdqwZowcxtFpZfLa6k%2Fuploads%2FEZYzkyKW4XyDAFGRIgU1%2Fset%20meta%20-%20manual%20.gif?alt=media&amp;token=9ddfc27b-f8d4-488b-95e6-ecc6997f067d" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
Enter variables using curly bracket syntax - for example: `{{payload.id}}`, `{{system.now}}`.
{% endhint %}

### Adding meta items from a schema

If you need to populate meta variable values from incoming payloads, it can be useful to navigate the payload schema and select required values, rather than adding payload paths manually. To do this:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td>Select the <a href="/documentation/brigge-for-transformers/schemas.md">schema</a> associated with incoming payloads (i.e. the payload structure that the <em>Set meta</em> node receives) and click the transformation button:</td><td><img src="https://2172380191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8IqdqwZowcxtFpZfLa6k%2Fuploads%2FEfMVVVBF5Sj3VUcWWOF6%2FSet%20meta%20options%20-%20use%20schema.svg?alt=media&amp;token=f53ba44c-df21-4365-a8ec-057acf60105e" alt=""></td></tr><tr><td>Enter a variable name (i.e. <code>key</code>), then use the <code>value</code> field to navigate the schema structure to select the required payload field:</td><td><img src="https://2172380191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8IqdqwZowcxtFpZfLa6k%2Fuploads%2FYDTrDxRVNdaSSUTqBX53%2FSet%20meta%20options%20-%20add%20payload%20field.svg?alt=media&amp;token=d026b46c-2bfc-4100-bd50-d5a18a9f91fa" alt=""></td></tr></tbody></table>

<details>

<summary><img src="https://2172380191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8IqdqwZowcxtFpZfLa6k%2Fuploads%2F7HM7sl8g8aAJS7kJ0UqA%2Ficon-park-outline--play-two.svg?alt=media&amp;token=af3a2963-fabf-4e70-a87c-1884308d2c27" alt="" data-size="line"> Show me</summary>

<figure><img src="https://2172380191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8IqdqwZowcxtFpZfLa6k%2Fuploads%2F1Fiqkpe59TuzCONgim73%2Fset%20meta%20-%20schema%20.gif?alt=media&amp;token=4718b9e6-bcd1-4184-8211-1e0cfb45b008" alt=""><figcaption></figcaption></figure>

</details>

### Transforming meta items

When you choose to resolve variable values from payload or system variables, resolved values will be exactly as received from payloads or exactly as generated by Brigge.&#x20;

If needed, you can apply [data transformations](/documentation/brigge-for-transformers/pipelines/data-transformations.md) to resolved values. For example, you might want to change a date format, change values to upper or lower case, etc. To do this, click the transformation button for the associated variable. For example:

<div align="left"><figure><img src="https://2172380191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8IqdqwZowcxtFpZfLa6k%2Fuploads%2Fk3QC3CFAdWMs4oT28A74%2Fset%20meta%20transform%20option.png?alt=media&amp;token=6f4111c4-313b-43f5-9724-5b8f2ab2b380" alt=""><figcaption></figcaption></figure></div>

From here, select and configure the required [data transformation](/documentation/brigge-for-transformers/pipelines/data-transformations.md).
