> 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.md). # Use an existing AMQP Message Queue To use an AMQP message queue that already exists on the broker, define the options in the **Setup** tab as follows: | Option | Description | | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Connection** | Specify the URI address of the AMQP broker to which this step connects to ingest messages into PDI. For more information see: | | **Queue name** |

Specify the name of an existing AMQP message queue name from which this step will ingest messages. The specified queue must conform to these parameters:- Durable

Note: If you specify the name of a queue which does not already exist, this step will create a new queue. The new queue will conform to the same parameters. See Create a new AMQP Message Queue.

| | **Exchange name** |

Specify an existing exchange name from which to bind the queue.

Leave the Exchange name blank to use the DEFAULT as the Exchange type (below) and set the Exchange type to DIRECT. The AMQP Producer step requires a matching blank entry in its Setup tab for the Exchange name.

| | **Exchange type** |

Specify the type pattern this exchange is using:

DIRECT routes messages to queues based on the message routing key.

FANOUT routes messages to all the queues that are bound to the fanout exchange and the routing key is ignored.

TOPIC routes messages to one or many queues based on a match between a message routing key and the pattern used to bind a queue to an exchange.

HEADERS routes messages using one or more key/value pairs that are more easily expressed as message headers than a routing key.

| | **Routing Keys** | Use the **Routing Keys** table to specify the routing keys that define the bindings between the exchange and the queue. See [Specify Routing Keys](/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/amqp-consumer/options-amqp-consumer/use-an-existing-amqp-message-queue/specify-routing-keys.md) for more information. | | **Headers** | Use the **Headers** table to specify the *Name* and *Value* associated with the appropriate headers. See [Specify Headers](/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) for more information. | --- # 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.md?ask=&goal= ``` `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.