> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/amqp-consumer/options-amqp-consumer/fields-tab-amqp-consumer.md).

# Fields tab

![Fields tab in AMQP Consumer](https://3411831820-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAYwCj9fPr1B2pjC11IOQ%2Fuploads%2Fgit-blob-c317399b4e5622663fe19373652e77c56b3b81ea%2FPDITransStep_AMQPConsumer_FieldsTab.png?alt=media)

Use this tab to define the fields in the record format.

| Option          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Input name**  | <p>The input name is specified by the AMQP Consumer step. The following input names are assigned by default:</p><ul><li><em>message</em>: The individual message contained in a record.</li><li><em>queue name</em>: The queue to which records are published and received.</li><li><em>routing key</em>: The routing key associated with the dependent pattern type.</li><li><em>exchange name</em>: The exchange name from which messages are received.</li></ul> |
| **Output name** | Specify a substitute output name to use a field name that is different from the **Input name**. The data type of the output name must match the **Type** of the **Input name**.                                                                                                                                                                                                                                                                                     |
| **Type**        | The type field defines the data format for streaming records. Options include **String** or **Binary**. The default value is String.                                                                                                                                                                                                                                                                                                                                |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/amqp-consumer/options-amqp-consumer/fields-tab-amqp-consumer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.