# About the Communications Mining activity package

> UiPath.CommunicationsMining.Activities package reference for building automations on Communications Mining stream results, records, and predictions.

The Communications Mining activities package lets your automations consume the output of UiPath Communications Mining™. Communications Mining turns each communication it processes into a list of extractions, and this package gives your workflow access to that list, to the records behind it, and to any attachments.

The activities in the package cover the following areas:

* **Streams** - read communications from a Communications Mining stream and control the stream position.
* **Records** - create records in a dataset and retrieve them.
* **Attachments** - download an attachment, so that a downstream automation, such as a Document Understanding workflow, can process it.
* **Predictions** - retrieve predictions for the records you supply.
* **Data validation** - send stream results to a human for review, either as a `Document Validation` action in Action Center or through an Apps validation control, and read the reviewed data back into the automation.

For the reference page of each activity, refer to the **Activities reference** section. For the recommended way of combining these activities into a dispatcher and its downstream automations, see [Automation architecture](https://docs.uipath.com/activities/other/latest/communications-mining/automation-architecture) and [How the Dispatcher process works](https://docs.uipath.com/activities/other/latest/communications-mining/how-does-the-dispatcher-process-work).

## Robot log level

The Communications Mining activities write diagnostic details to the robot logs at **Verbose** level, so these details appear only when the robot runs with verbose logging enabled. For the full list of levels and where to configure them, refer to [Log levels](https://docs.uipath.com/robot/standalone/latest/admin-guide/logging-levels).

You can raise these logs to the **Information** level by setting the `UIPATH_DU_SET_LOGS_TO_INFO` environment variable on the robot host, which makes them visible without switching the robot to verbose logging. Because these logs can include file paths, project names, and user email addresses, the variable is an opt-in for each host. When the variable is not set, the **Verbose** default applies.

:::warning
The activity logs can contain personally identifiable information (PII), including file paths, project names, and user email addresses. Raising the log level to **Information** makes that information visible to anyone with access to the robot logs.
:::