# Automation architecture

> Communications Mining™ provides a list of extractions for you to automate, and the following diagram describes how you actually acquire this list of extractions.

Communications Mining™ provides a list of extractions for you to automate, and the following diagram describes how you actually acquire this list of extractions.

The Communications Mining™ Stream processes communications and sends them to the Dispatcher. From there, they are routed to UiPath® Orchestrator, which distributes them into several numbered queues, including a Human-in-the-loop (HITL) queue. Each numbered queue initiates an Automation Process, with the HITL queue generating an Automation Process logic specifically for HITL.

![automation architecture](https://dev-assets.cms.uipath.com/assets/images/activities/communications-mining-automation-architecture-472220-0f8eb1a7-813b7c34.webp)

Working from left to right, the data is first uploaded into Communications Mining, it then progresses through the platform and lands in something called a [Stream](https://docs.uipath.com/communications-mining/automation-cloud/latest/user-guide/create-a-stream). A robot then picks up the communication from this stream and dispatches it to an Orchestrator queue for processing. There are three main elements to understand within this architecture:

1. How are communications uploaded into the Communications Mining platform?
2. How does the Dispatcher process work?
3. How do the downstream automations access the needed information?