> 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/10.2-data-integration/pdi-transformation-steps-reference-overview/amqp-consumer/options-amqp-consumer/use-an-existing-amqp-message-queue/specify-headers.md).

# Specify Headers

When using **Headers** as the **Exchange type**, specify the *Name* and *Value* associated with the appropriate headers in the **Headers** table. Only string values are accepted.

![Headers table](/files/WnGTrHEj9DJFbQWxaVuu)

There are two options for specifying headers:

* **Match all headers**

  For a message to be delivered to the AMQP Consumer step's queue, the producer message must contain all the header key/value pairs in the AMQP Consumer step.

  Be aware that the producer may have more headers than specified in the AMQP Consumer step. Producer headers must match all the specified consumer headers; however, not all the specified consumer headers must match all producer headers.
* **Match any header**

  For a message to be delivered to the AMQP Consumer step's queue, at least one header key/value pair must match on both the AMQP Consumer step and the producer.

Once you specify the headers configuration for the AMQP Consumer step and run the transformation, this permanently binds the headers and the consumer configuration to the specified queue. Even if you subsequently remove the headers from this table, the binding will persist in the AMQP broker. For more information on how to verify the queue's bindings, see: [https://www.rabbitmq/rabbitmqctl.8.html#list\_bindings.](https://www.rabbitmq/rabbitmqctl.8.html#list_bindings)


---

# 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 dynamically by asking a question.

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

```
GET https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/amqp-consumer/options-amqp-consumer/use-an-existing-amqp-message-queue/specify-headers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.