# Internal Message Handler

You're building a workflow step that processes a message but shouldn't be invokable from the Command Bus — for example, a "validate eligibility" step inside an Orchestrator, or a stage in an `outputChannelName` chain. An **Internal Handler** connects any service in your Dependency Container to a named input channel so it can play the role of an [Endpoint](/messaging/messaging-concepts/message-endpoint.md), without exposing it as a Command Handler. If the service produces output, it can be connected to an output channel.

### How to register

```php
class Shop
{
    #[InternalHandler("buyProduct")] 
    public function buyProduct(int $productId) : void
    {
        echo "Product with id {$productId} was bought";
    }
}
```

### Possible options

* `endpointId` - Endpoint identifier
* `inputChannnelName` - Required option, defines to which channel endpoint should be connected
* `outputChannelName` - Channel where result of method invocation will be
* `requiredInterceptorNames` - List of [interceptor](/modelling/extending-messaging-middlewares/interceptors.md) names, which should intercept the endpoint


---

# Agent Instructions: 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:

```
GET https://docs.ecotone.tech/messaging/messaging-concepts/message-endpoint/service-activator.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.