Skip to main content
Audit Logging provides comprehensive tracking and monitoring of user actions across your Gumloop organization. This feature enables administrators to maintain security, compliance, and operational oversight by recording detailed logs of all significant activities within the platform.

Overview

Audit logging automatically captures and stores detailed records of user activities, system events, and administrative actions within your organization.

Security Monitoring

Track unauthorized access attempts and suspicious activities

Compliance Requirements

Meet regulatory standards for data access and modification tracking

Operational Oversight

Monitor workflow executions and system usage patterns

Troubleshooting

Investigate issues by reviewing historical activity patterns
Audit Logging Overview

Filtering by Event Type

You can filter audit logs by event type to quickly find specific activities. Use the Event Type dropdown to select from available event types, or search for a specific type.
Audit log Event Type filter dropdown showing event types like user_sign_in, credential_retrieval, credential_insertion, and more

Tracked Events

The audit logging system captures a comprehensive range of activities across the platform including:
  • User Sign-ins: Records when users authenticate to the platform
  • Session Management: Tracks session creation and termination
  • Credential Creation (credential_insertion): New API keys, OAuth connections, and service integrations
  • Credential Modification (credential_modification): Updates to existing authentication credentials
  • Credential Deletion (credential_deletion): Removal of credentials from the system
  • Credential Retrieval (credential_retrieval): Access to stored credentials for agent and workflow execution
Credential events record which credential was touched and by whom. Secret values, OAuth codes, and tokens are never written to audit logs.
  • Team Creation: New team setup and configuration
  • Member Management: Adding or removing users from teams
  • Team Deletion: Permanent removal of teams
  • Team Renaming: Changes to team names and metadata
  • Member Addition/Removal: Changes to organization membership
  • Domain Configuration: Updates to organization domain settings
  • Metadata Updates: Changes to organization settings and configuration
Records which Slack workspaces are linked to your organization, and who linked them.
  • Workspace Registration (organization_slack_workspace_registration): A Slack workspace was associated with the organization
  • Workspace Removal (organization_slack_workspace_removal): The association was removed
Each entry includes organization_id, slack_workspace_id, slack_workspace_name, and the acting user.
Only the relationship and the acting user are recorded. OAuth codes, tokens, and state parameters are never logged.
  • Role Creation: New custom roles and access controls
  • Member Changes: Adding or removing users from a custom role
  • Role Deletion: Removal of custom roles
  • Workflow Execution: Workflow runs and automation triggers
  • Workflow Termination: Manual or automatic stopping of workflows
  • Workflow Completion: Successful workflow completions
  • Run Retrieval: Access to workflow execution results and logs
  • File Uploads (file_upload): Documents and data uploaded to the platform
  • File Downloads (file_download): Access to stored files and documents
  • File Deletion (file_deletion): Removal of files from the system
  • File Modification (file_modification): Changes to a stored file, including artifact domain hosting configuration
Every log entry includes the agent_id, agent_name, the operation performed, and the workspace_id when the agent belongs to a team workspace.
  • Agent Creation (agent_creation): A new agent was created. Agents created by cloning carry operation: clone along with the source_agent_id.
  • Agent Modification (agent_modification): Changes to an existing agent, including version_deploy when a saved version is deployed
  • Agent Deletion (agent_deletion): An agent was deleted
  • Agent Workspace Move (agent_workspace_move): An agent moved between workspaces
Trigger lifecycle changes are recorded as agent_modification events with one of these operations:Each entry records trigger_id, trigger_type, trigger_name, whether the trigger is active, and a source field distinguishing who made the change:
  • ui — a person changed the trigger in Gumloop
  • ai_agent — the agent changed its own trigger using its schedule or integration-trigger tools
Enabling, updating, or disabling an agent’s external channels is recorded as an agent_modification event.
  • Skill Attach (skill_attach) / Skill Detach (skill_detach): A skill linked to or removed from an agent
  • Knowledge Source Attach / Update / Detach (knowledge_source_attach, knowledge_source_update, knowledge_source_detach): Changes to the Brain sources an agent can search
Entries include the agent_id, the skill_id or knowledge source identifier, and the workspace context.
Serving an artifact on its own domain is recorded as a file_modification event.Entries include the artifact identifier, the filename, the hosting alias (and the previous alias on a rename), and the workspace context.

Audit Log Data Structure

Each audit log entry contains comprehensive metadata and contextual information to provide complete visibility into platform activities.

Example: Workbook Creation Log

Log Entry Components

Core Event Data

  • Event ID (unique identifier)
  • Timestamp (ISO format)
  • Event Type (action categorization)
  • User ID (who performed the action)

Request Context

  • Source IP Address
  • Session Information
  • Authentication context

Event Details

  • Action-specific JSON data
  • Resource identifiers
  • Configuration parameters

Resource Information

  • Team IDs
  • Workflow IDs
  • Affected entities

API Access

Access audit logs programmatically using the REST API for integration with external monitoring, SIEM systems, or custom reporting tools.

Quick Reference

1

Endpoint

2

Required Parameters

  • organization_id (string): Organization ID
  • user_id (string): Your user ID (admin required)
  • start_time (datetime): Start timestamp (ISO format)
  • end_time (datetime): End timestamp (ISO format)
3

Optional Parameters

  • event_type (string): Filter logs by a specific event type (e.g., "user_sign_in", "credential_retrieval", "flow_execution")
  • page (integer): Page number (default: 1)
  • page_size (integer): Records per page (default: 50)
4

Authentication

Include your API key in the Authorization header

Example Request

For complete API documentation and advanced usage, see: Gumloop API Reference

Data Privacy and Security

  • Encryption: All audit logs are encrypted at rest and in transit using industry-standard protocols
  • Access Control: Logs are accessible only to organization administrators with proper authentication
  • Data Isolation: Organization audit logs are completely isolated from other organizations through strict multi-tenancy controls
  • Data Retention: Audit logs are retained according to Enterprise agreement terms
  • Compliance Standards: Meets SOC2 Type II and GDPR requirements for audit trail management
  • Data Export: Full export capabilities for compliance audits and backup purposes
Only users with the Admin organization role can access audit logs. Security, Manager, and other feature roles do not grant audit log access. Ensure appropriate role assignments to maintain security controls.

Custom Roles

Configure granular permissions and access controls

Usage Data Export

Export comprehensive platform usage data

Organizations and Teams

Understand organizational structure

Security & Compliance

View our security certifications