Example workflow: report Excel-driven runs

This walkthrough builds a small but realistic process that you can drop into any project. It reads a list of records from an .xlsx workbook, classifies each row as success or failed based on a column the source system already provides, attaches the daily log file, and sends one consolidated report to RPA Watch.

ZIPRPA Watch Uipath Example.zip142 KB · ZIPDownload ↓

XLSXEnglish_Dummy_RPA_Data.xlsx10 KB · XLSXDownload ↓

By the end you'll see a single run appear on your dashboard with per-record details and downloadable attachments.

Before you start

Make sure you have:

- The RPAWatch.UiPath.Activities package installed https://www.nuget.org/packages/RPAWatch.UiPath.Activities

- A workbook with at least the columns used below — adapt the column names to match yours:

- A Flow ID (a GUID) copied from the Flows page in RPA Watch.

- A Robot ID (numeric) copied from the Robots page.

- An API Key generated under Account Settings → API Keys. It looks like rpakey_eda9e46a8fdc22d427426c89c534758b71a1a179.

The example uses C# expressions, which is the default for projects created in Studio 2026.

1. Declare the workflow variables

In the Variables panel, add:

You can also expose the API URL, API key, flow ID, and robot ID as Arguments in_RPAWatchApiUrl, in_RPAWatchApiKey, in_FlowId, in_RobotId) so the same workflow can be promoted from Dev to Prod without changes.

 2. Capture the start time

The very first activity should be an Assign that records the moment the workflow started — Send Report uses it to calculate duration_seconds.

- To → startedAt

- Value → DateTime.Now

3. Read the input workbook

Add an Excel → Read Range Workbook activity:

If you assign this later (e.g. after the Excel read), the reported duration will be artificially short.

4. Initialize the details table

Add a Create Details Table activity (under the RPA Watch category):

- Details Table → detailsTable

The output is an empty DataTable with the six columns RPA Watch expects: sequence_no, record_id, record_name, status, result, error_message. See [Create Details Table](create-details-table) for the full schema.

5. Loop over the rows and log each one

Add a For Each Row in Data Table activity:

- DataTable → excelDataTable

- CurrentRow → currentDataRow (default)

- In the Properties panel, set CurrentIndex → index

Inside the loop body, drop a single Add Detail Row with these C# expressions:

The ternary on Status is the key trick: it maps the source system's domain status to the two values RPA Watch understands success, failed). See [Add Detail Row](add-detail-row.md) for more patterns.

6. Send the consolidated report

After the loop, drop a Send Report activity:

Because detailsTable contains rows with both success and failed, the run will be reported as partial_success automatically — no override needed. If the file paths in File Paths exist, they're uploaded as attachments using the original filenames.

Log the outcome (optional but recommended)

Drop a Log Message after Send Report with Level = Info and Message = $"RPA Watch returned {respStatus}". If a run ever fails to publish, this is the first place you'll look.

What you should see in RPA Watch

Within a few seconds, navigate to Processes → <your flow> in RPA Watch:

- A new run appears with status Partial success

- The duration matches the time between startedAt and the Send Report call

- The Details tab lists all three records, with row 2 highlighted as failed and the Error column populated

- The Attachments section shows Rapor_27-04-2026_16-02-03.xlsx for download

Common pitfalls