Integrations Usage Stats

Get a summary of how an organization's integrations (ActivePieces) flows consume tasks over a period.

Before You Begin

Prerequisites

  • A role with usage stats access (Admin / Super Admin) on the Organization.
  • Organization UUID.

Step 1. Find the Organization UUID

Find the organization UUID. You can retrieve it using this query:

{
  organization(id: "<ORGANIZATION_ID>") {
    uuid
  }
}

The organization ID can be found on the home page url: https://app.pipefy.com/organizations/<ORGANIZATION_ID>

Step 2. Execute the query

query integrationsUsageStats($organizationUuid: ID!, $period: PeriodFilter!) {
  integrationsUsageStats(organizationUuid: $organizationUuid, period: $period) {
    tasksConsumed {
      usage
      limit
    }
    activeFlows
    filterDate {
      from
      to
    }
    history {
      nodes {
        date
        usage
        limit
      }
    }
  }
}

Variables:

{
  "organizationUuid": "<ORGANIZATION_UUID>",
  "period": "current_month"
}

Input Explanation:

  • organizationUuid: The UUID of the organization you want the usage summary for.
  • period: The time window to aggregate. One of current_month, last_month, or last_3_months.

Sample Response:

{
  "data": {
    "integrationsUsageStats": {
      "tasksConsumed": {
        "usage": 1280,
        "limit": null
      },
      "activeFlows": 7,
      "filterDate": {
        "from": "2026-06-01T00:00:00Z",
        "to": "2026-06-30T23:59:59Z"
      },
      "history": {
        "nodes": [
          { "date": "2026-06-01", "usage": 120, "limit": null },
          { "date": "2026-06-02", "usage": 64, "limit": null }
        ]
      }
    }
  }
}

The response gives the total tasksConsumed.usage for the period, the number of activeFlows (distinct flows that ran), the resolved filterDate boundaries, and a history time series of tasks consumed per bucket.


Key Notes

  • History granularity follows the period: daily buckets (date as yyyy-MM-dd) for current_month and last_month, monthly buckets (date as yyyy-MM) for last_3_months.
  • limit (on both tasksConsumed and each history node) is the tasks allowance for the organization. It returns null while no allowance is mapped for the organization.
  • For the per-flow breakdown of this usage, see Integrations usage details query.