activities
latest
false
- Release Notes
- Overview
- The nature of communications
- The anatomy of an extraction
- General fields
- Automation architecture
- Uploading data to Communications Mining
- Using the Dispatcher Framework
- Activities reference
- Get Stream results
- Get Attachment
- Create Communications Mining Validation Action
- Create Communications Mining Validation Artifacts
- Create Record
- Get Record
- Fetch Batch from Stream (Legacy)
- Advance Stream
- Reset Stream
- Retrieve Communications Mining Artifacts
- Predict Record(s)
- Wait For Communications Mining Validation Action
Communications Mining Activities
Last updated Mar 3, 2025
The nature of communications
When a business receives a communication, it typically requires action. These communications can take various forms, such as emails, help desk tickets or "contact us" form submissions. Regardless of the channel, the goal remains the same: identify the necessary actions to resolve all queries within the communication.
When automating communications with UiPath Communications Mining, our goal is to transform natural language communications
into a "to-do list" of requests. We refer to this to-do list as a list of extractions.
Note: When an email lands in your inbox, it's not always straightforward. People often include multiple requests, which is why
we create a "to-do list" for each communication instead of trying to pinpoint just one main topic or request.
