Overview
Company Overview is the governance hub that brings together everything IT admins need to track process health, automation performance, and API consumption across the entire Pipefy operation in one place. It exists to eliminate fragmented visibility across organizations and pipes, so governance decisions get made with full context instead of isolated snapshots. This evolution brings deeper data and direct action channels, reinforcing Company Overview as the definitive surface for teams managing the Pipefy ecosystem at scale.
What's new?
- Pipe level charts inside Automations: drill down from organization level health straight into a specific pipe to track volume and bottlenecks process by process. Available under Usage Stats, Automations section.
- Export report button for API calls: download API consumption reports in one click, ready for auditing or external analysis. Available under Usage Stats, API section.
- Native feedback button inside Usage Stats: a feedback channel is now built directly into the Usage Stats page, so you can send suggestions or report issues without leaving your workflow.
These additions join what is already available in Company Overview: feature discovery alerts across Usage Stats screens, Multi Org Metrics with Org Groups, AI Credits Management per organization, and detailed API visibility by operation, personal access token, and service account.
How does this help?
- You spot the exact bottleneck, not just the general symptom: instead of knowing only that one organization has slow automations, you see which specific pipe is holding up the flow.
- You audit API usage without depending on another team: exporting the API report in one click removes the need to request that data from someone else to close an audit.
- You shape the roadmap right from where you work: native feedback reaches the product team the moment an issue shows up, with no separate ticket required.
Use cases
1. IT admin pinpointing an approval bottleneck by business unit
A company with several business units, each running its own purchase approval pipes, notices that the South Unit organization has the lowest completed automation rate for the month. Using pipe level charts inside Automations, the IT admin finds the bottleneck concentrated in the Purchase Approval above $50k pipe, stuck at the legal validation phase, and routes it directly to the phase owner without opening the pipe manually or asking engineering to dig through logs.
2. Compliance team auditing API usage across organizations
A compliance team running the quarterly audit of API usage across the group's organizations opens Usage Stats, filters by organization, and uses the export button to download the API call report. The file is ready to feed the internal audit spreadsheet, cutting the wait for a request to another team.
3. Pipe Admin reporting an issue right from where it happens
A Pipe Admin notices a recurring glitch when switching between organizations inside Usage Stats. Instead of opening a separate support ticket, they use the native feedback button right on the screen where the issue happens, describing the behavior in the exact context it occurs in, and the product team receives the report already tied to that screen and organization.
4. Multi org manager prioritizing where to standardize a process
A manager overseeing multiple organizations uses pipe level charts to compare volume and bottlenecks across similar Vendor Onboarding pipes in three different organizations in the group, identifying which one needs priority intervention before rolling the model out to the rest.
Most relevant for
- IT Admins
- Multi Org Managers
- Compliance and Audit Teams
- Pipe Admins
