> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/utils/test/callcount.md).

# Call Count

### Overview

The **Call Count Component** waits until a specified number of messages arrive and then sends a single output message containing all received data.

### Usage

This component is useful for batch processing, ensuring that multiple incoming messages are collected before proceeding to the next step in a workflow.

#### Input Ports

| Port | Description                                     |
| ---- | ----------------------------------------------- |
| `in` | Receives messages to be counted and aggregated. |

#### Output Ports

| Port  | Description                                             |
| ----- | ------------------------------------------------------- |
| `out` | Emits a single message containing all collected inputs. |

#### Properties

| Property    | Type     | Description                                                           |
| ----------- | -------- | --------------------------------------------------------------------- |
| `callCount` | `number` | The number of input messages to wait for before triggering an output. |

#### Processing Logic

1. **Receives Messages**: Collects incoming messages one by one.
2. **Tracks Count**: Keeps count of received messages.
3. **Sends Aggregated Output**: Once the expected number of messages arrive, it sends them all in a single output message.

### Notes

* **Batch Processing**: Ensures that multiple messages are processed together.
* **Message Aggregation**: The output message contains all collected input messages.
* **Useful for Testing**: Helps verify message flow and event timing in test scenarios.

This component is ideal for workflows requiring synchronization of multiple incoming messages before proceeding further.


---

# 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.appmixer.com/connector-configuration/utils/test/callcount.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.