Overview
IT admins now have a single place to track everything that happens inside a pipe. Structural configuration changes and card activities are consolidated in one interface, with search, export, and full details on who performed each action and when — no more manually logging changes or opening items one by one.
What's new?
Inside the Pipe under Manage → Audit Logs:
- New “Configuration Changes” tab: records structural pipe changes, including AI Agents, automations, phases, fields, field conditionals, connections, members, and permissions
- Card Activities: key card events consolidated in the pipe log, with no need to open each card individually
- Resource Type column: identifies the type of resource affected by each event
- Sortable Time column: sort history chronologically or from most recent to oldest
- Full actor details: name and email of who performed each action. If the actor is an AI Agent or automation, its name is also shown
- 180-day history in the interface
- CSV export: last 30 days of events
How does this help?
- Makes detective work easier: answering “who changed this automation?” used to mean manually checking each configuration or card. Now the answer is readily available.
- Reduces incident response time: IT teams pinpoint the source of a process break without relying on memory or support tickets.
- Supports audits and compliance: 180 days of auditable history with “who did what and when” — usable for internal or external review.
- Shortens troubleshooting cycles: “Was this card deleted? By whom?” or “When was this field updated?” — answerable in seconds directly in the log.
- Export for offline analysis: combined 30-day CSV lets you slice data and cross-reference with other tools without accessing the interface.
Use cases
- Automation break investigation: a critical approval automation stopped working on Friday night. The IT admin opens the Configuration Changes tab, filters by “Automations,” and identifies in seconds who made the change, the exact time, and what was modified — no need to interview the team or dig through emails.
- Permissions and access audit: the security team needs to prove that only authorized users had access to a pipe processing sensitive HR data. Using the members and permissions log, they generate the CSV and deliver the report — no Pipefy support needed.
- Deleted card tracking: a purchase request card disappeared before approval. The Procurement manager opens the Card Activities tab, locates the deletion event, and identifies who was responsible — no support ticket or manual history reconstruction required.
- Change control during new rollouts: while rolling out a new process, the IT admin monitors the Configuration Changes tab daily to ensure no unplanned changes were made by users with edit access. Real-time governance without status meetings.
- Response to report discrepancies: a value field in a financial pipe shows inconsistent data. The operations analyst opens the Card Activities tab, filters by the specific field, and reconstructs the update timeline — pinpointing the edit that caused the deviation.
Most relevant for
- IT admins responsible for production pipes
- Process managers with high-criticality pipes (Procurement, HR, Finance)
- Security and compliance teams
- Operations analysts who troubleshoot processes
Documentation
For the complete step-by-step guide, see the Help Center article.
