This is a paid feature. See plans and pricing, or talk to sales about an enterprise plan.
What are audit events?
Activepieces records an audit event for every meaningful action on the platform — a flow gets created, a run finishes, a user signs in, a connection is saved, a signing key is rotated, and so on. Each event captures what happened, who did it, when, and the project or platform it belongs to. Agent actions are recorded too. When an agent runs a piece action that writes something — sending an email, updating a row, posting a message — the event names the agent, the app, the action, the account it used and where the run came from. Reads are not recorded, and the values the agent passed to the action are never stored. The other tool types an agent can carry do not write this event: a flow tool is recorded as a flow run instead, and an MCP server tool is not recorded at all, so neither shows up here even though both can change things. You can do two things with these events: view them in the audit log table for compliance and forensics, or stream them to a webhook to react in real time.View them in the audit log
Open Platform Admin → Security → Audit Logs to browse the full table. Filter by action, user, project, or date range to find a specific event, and click any row to see the full payload.
Forward them to your tools
To react to events in real time — get a Slack alert when a flow fails, forward audit logs to your SIEM, send a daily digest of new sign-ups — use Event Streaming. It POSTs each event to a webhook URL of your choice, which you can point at an external system or at an internal handler flow that routes each event to the channel you care about.Event catalog
The full list of documented events. We add new ones as the platform grows; the source of truth for every event we emit is the event schema in the codebase.Flows
Flow runs
Agents
Folders
Connections
Users
Platform
See also
- Event Streaming — forward audit events to a webhook URL