Skip to main content
Organization Analytics is an AI-powered analytics agent available to enterprise organizations. It lets you query your organization’s usage data — workflow runs, agent chats, credit consumption, and user activity — through a conversational interface, without writing SQL or building dashboards.

Overview

The Gumloop Analytics agent connects to your organization’s data in BigQuery and answers questions in natural language. Ask about credit usage trends, top workflows, active users, or any other organizational metric, and the agent returns results as tables, charts, or CSV exports.
Gumloop Analytics agent chat interface

Credit Tracking

Monitor credit consumption across users, workflows, and agents over any time period

Usage Insights

Understand which workflows and agents are most active and who is using them

User Activity

See which team members are running workflows, chatting with agents, and consuming credits

Visual Reports

Generate charts and download CSV exports for stakeholder reporting

How to Access

In Chat

Organization Analytics is available in the Gumloop Chat interface. When you start a new conversation, select the Gumloop Analytics agent to begin querying your organization’s data.

In Slack

You can also use the Gumloop Analytics agent directly in Slack:
1

Add the Gumloop bot to your channel

Invite the Gumloop bot to the Slack channel where you want to use analytics.
2

Enable the analytics agent

Type /gummie add analytics in the channel to activate the Gumloop Analytics agent.
Running /gummie add analytics in Slack
3

Ask your questions

Mention @Gumloop in the channel and ask your analytics questions. The Gumloop Analytics agent will respond with results directly in the thread.
Gumloop Analytics responding to a query in Slack

What You Can Ask

The analytics agent has access to the following data about your organization:
DataWhat It Covers
Workflow RunsRun history, credit costs, execution counts, completion timestamps
Agent ChatsChat sessions with agents, credit costs per chat, chat volume over time
AgentsAgent names, descriptions, models used, tools configured, creator info
WorkflowsWorkflow names, descriptions, creator info
UsersUser emails and activity across your organization

Example Questions

Credit usage:
How many credits has our organization used in the last 30 days?
Break it down by user.
Workflow activity:
What are our top 10 most-run workflows this month? Show credit cost for each.
Agent usage:
How many agent chats happened last week? Which agents are most popular?
Trend analysis:
Show me daily credit consumption for the past 3 months as a chart.
User activity:
Which users have been most active in the last 7 days?
Show their workflow runs and agent chats separately.

Data Access and Permissions

Organization Analytics enforces role-based access to ensure data security:
RoleData Scope
AdminFull access to all organization-wide data across all users
ManagerFull access to all organization-wide data across all users
MemberPersonal data only — can only see their own workflow runs, agent chats, and credit usage
Non-admin and non-manager users are automatically scoped to their own data. They cannot query or view other users’ activity, even if they explicitly ask for it.

Security

Organization Analytics is built with multiple layers of data protection:
  • Organization isolation: Every query is automatically scoped to your organization. The agent cannot access data from other organizations, even if prompted to do so.
  • Parameterized queries: All queries use parameterized SQL — user input is never interpolated into query strings, preventing SQL injection.
  • Schema validation: The agent can only query pre-defined tables and columns. It cannot run arbitrary SQL or access tables outside the analytics schema.
  • Role-based scoping: Non-admin users are automatically filtered to their own data at the query level, not just at the display level.
  • Prompt injection protection: The agent is designed to refuse attempts to bypass data access restrictions through prompt injection, role-play scenarios, or other techniques.

Credit Usage

Queries made through the analytics agent consume credits based on the amount of data scanned in BigQuery. The agent is optimized to minimize data scanning by:
  • Using aggregation queries instead of raw row dumps
  • Applying automatic partition filters (defaulting to the last 90 days for time-series tables)
  • Limiting result sets to only the data needed to answer your question
For time-range questions, the agent automatically applies efficient date filters. If you need data beyond the default 90-day window, specify the date range explicitly in your question.