Skip to main content
Audit logs provide a comprehensive record of all user actions and system events in Activepieces, essential for security monitoring, compliance, and troubleshooting.

Overview

Audit logging captures:

User Actions

Authentication, authorization, and user management events

Resource Changes

Modifications to flows, connections, and configurations

System Events

Flow executions, errors, and system operations

Audit Event Types

Activepieces tracks these event categories:

Authentication Events

Captures:
  • New user registrations
  • Authentication method (SSO, credentials, managed auth)
  • User details and IP address

Flow Events

Tracked Operations:
  • ADD_ACTION, UPDATE_ACTION, DELETE_ACTION
  • CHANGE_NAME, CHANGE_STATUS, CHANGE_FOLDER
  • LOCK_AND_PUBLISH, USE_AS_DRAFT, LOCK_FLOW
  • MOVE_ACTION, DUPLICATE_ACTION
  • UPDATE_TRIGGER, UPDATE_METADATA
  • And more…

Flow Run Events

Connection Events

Project Role Events

Folder Events

Querying Audit Logs

List Events

Filter Parameters

Response Format

Audit Log Storage

Database Schema

Retention

Configure log retention:
Default retention is 90 days. Adjust based on compliance requirements (e.g., SOC 2 requires 1 year).

Archival

Archive old logs to cold storage:

Compliance Use Cases

SOC 2 Type II Requirements

Access Monitoring:
Change Management:
Required Retention: 12 months minimum

Security Monitoring

Suspicious Activity Detection

Alerting

Set up alerts for critical events:

Export & Integration

Export to CSV

Stream to SIEM

Integrate with security information and event management systems:

Event Summary

Generate human-readable summaries:

Best Practices

Regular Reviews

Review audit logs weekly for unusual patterns or security incidents.

Compliance Checks

Perform quarterly compliance audits using audit log queries.

Retention Policy

Set retention based on strictest compliance requirement (usually 1-7 years).

Access Control

Restrict audit log access to security and compliance teams.

Automated Alerts

Configure real-time alerts for critical security events.

Archive Strategy

Archive old logs to cost-effective storage (S3, Glacier, etc.).

Troubleshooting

Check:
  • Audit logging is enabled
  • Database has sufficient storage
  • No errors in application logs
  • Events not filtered by retention policy
Solutions:
  • Add database indexes on frequently queried fields
  • Implement log archival for old events
  • Use pagination for large result sets
  • Consider read replicas for audit queries
Check:
  • User identity mapping is working
  • Project information is available
  • IP extraction configured correctly (reverse proxy)

Users & Permissions

Track permission changes

Security Practices

Security monitoring

SSO Configuration

Track SSO logins