Workflow run reports
Workflow run reports show what recorded workflow runs did: which items they identified, who they contacted, the channel used, and the recorded outcome. You can ask Harriet for a table and download the same report as a CSV.
Enable the skill
Workflow run reports is off by default. An admin must enable the skill for the appropriate groups under Skills, or assign it to an Endpoint AI profile or user for Desktop access. Enabling it does not give every employee access: the caller must also have permission to manage workflows, and the workflows feature must be enabled.
Before assigning it to a Desktop profile, install a Harriet Desktop release that supports interactive-only reporting. Older Desktop versions cannot prevent scheduled jobs from attempting to use the skill. Third-party MCP clients may not identify automated turns, so their automation restrictions cannot be guaranteed.
Choose a useful report
In a private chat, ask Harriet to describe a workflow's recent activity and suggest report options. Useful requests include “Show who received the 30-day survey in July”, “Which welcome messages failed last week?” and “List onboarding runs with the people they identified”. Choose the workflow, date range and timezone, then ask for the table and CSV.
Dates are inclusive. Harriet uses the workflow's schedule timezone unless you specify another, falling back to UTC. The usual window is 30 days, with a maximum of 366 days per request. Actions are reported on the date they happened, even if their run began earlier. Test runs are excluded unless you ask to include them.
Understand outcomes
Reports distinguish sent, failed, awaiting approval, approved, rejected, simulated, test redirected and no result logged. Approved means permission was recorded; it does not by itself prove a message was delivered. Bulk messages appear as a separate row for each recipient. Run links let you inspect the source activity.
Large reports are paged. If a result is marked incomplete, ask for the next page or narrow the window. Each CSV contains the rows returned on that page, using the same columns and access restrictions as the table.
Access and privacy
Reports include only your organisation's workflows that you can manage. Owners can inspect raw tool arguments, responses and message excerpts. Other workflow admins see message metadata such as recipient, channel, subject, status and time, with those payloads hidden from tables, CSVs and traces.
This skill is for interactive private chats. It is unavailable to workflow steps, automated cloud runs, public channels and widgets. It reports workflows run by the workflow editor; cloud-agent conversations use the separate, opt-in Session history setting.
Historical coverage
- Per-tool activity was not recorded before 12 November 2025.
- Records before 7 June 2026 use an older format that may provide fewer details.
- Before 21 September 2026, sends requiring approval may be reconstructed from confirmation and approval messages. July 2026 reports can therefore show an approval without proof of the final send.
Reports reflect the available logs and are not a guaranteed delivery ledger. See Scheduled runs for scheduling and Approvals and waiting steps for approval behavior.