Report sources
Use tasks, forms, workflows, integrations, notifications, agents, documents, retention, and custom data.
Feature guide
Measure business work, automation health, integration performance, agent activity, and team capacity.
Actions
Reporting and operations actions
Build saved reportPreview and publishInspect workflow runsInspect integration callsMonitor capacityComplete feature description
Reporting covers both business outcomes and platform operations. Saved reports can query tasks, forms, workflows, integrations, notifications, agents, documents, retention, and custom data, then apply fields, filters, groupings, aggregations, and visualizations.
Operational views go deeper than aggregate reports. Workflow runs expose node progress and errors, integration calls expose redacted requests and latency, agent runs expose traces and artifacts, and capacity views expose assignment and workload patterns.
Reports can be shared in the report hub or embedded into application pages alongside the actions that address the measured condition.
Use tasks, forms, workflows, integrations, notifications, agents, documents, retention, and custom data.
Configure reusable filters, fields, groupings, visualizations, and page embeddings.
Workflow runs and integration calls expose status, duration, outputs, failures, and attribution.
Analyze workload, assignments, priority, due dates, throughput, and team availability.
What designers and operators can do in this product area.
The main operations available in Reporting and operations.
Reporting and operations actions
Select a source, fields, filters, sorting, grouping, and display configuration.
Reporting and operations actions
Validate report output and make it available in the report hub or application pages.
Reporting and operations actions
Review node status, variables, outputs, errors, retries, and SLA state.
Reporting and operations actions
Review redacted requests, responses, status, latency, and caller context.
Reporting and operations actions
Compare active work and completion patterns across users and teams.
Patterns you can adapt to your own operating model.
Combine work backlog, SLA risk, failed runs, and integration errors.
Balance assignments before service levels are affected.