> For the complete documentation index, see [llms.txt](https://docs.ecotone.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecotone.tech/messaging/messaging-concepts/inbound-outbound-channel-adapter.md). # Inbound/Outbound Channel Adapter Inbound and Outbound Channel Adapters for external system integration When you will go through the code base you will meet `Channel Adapters`.\ Channel adapter are responsible for connecting external message providers to internal messaging system.\ This may be for example `AmqpInboundChannelAdapter`, which connects to RabbitMQ Message Broker to receive and send message internally. ## Inbound Channel Adapter Inbound Channel Adapter is responsible for incoming traffic from external providers.\ It's role is to connect to external provider or to expose API that will be called by external provider. Whatever role is selected, internally it convert incoming message to Ecotone's message and calls message channel (can be done via [Gateway](/messaging/messaging-concepts/messaging-gateway.md) or directly [Message Channel](/messaging/messaging-concepts/message-channel.md)). ## Outbound Channel Adapter Outbound Channel Adapter is responsible for outgoing traffic to external providers. After message flow is done, we may send Message to external provider, this may be for example `AmqpOutboundChannelAdapter` which connects to RabbitMQ Message Broker and converts Ecotone's Message to RabbitMQ message and sends it to the broker.\ Outboud Channel Adapter is implemented by [Message Handler](/messaging/messaging-concepts/message-endpoint.md). --- # 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.ecotone.tech/messaging/messaging-concepts/inbound-outbound-channel-adapter.md?ask=&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.