M
Mitchell Black
Problem Summary
When workflows/automations update contacts, the Audit Logs do not show which workflow performed the change. Instead, admins only see that a field changed on a contact, often with no user attribution (system/automation) and no workflow name or link.
With hundreds of active workflows, the current workarounds (naming conventions, time-based correlation, tags/helper fields, etc.) become:
  • Operationally untenable
  • Error-prone
  • Time-consuming
This directly impacts:
  • Auditability – It’s difficult or impossible to answer “Which workflow changed this contact field and why?” in a reliable, repeatable way.
  • Compliance – For regulated industries or strict internal controls, you need a clear, defensible trail showing which automated process made which change.
  • Debugging & QA – When a workflow misbehaves, tracking down the exact automation responsible for a change is far harder than it should be.
Current Behavior
Audit Logs (Settings › Audit Logs) focus on:
  • User-initiated changes and some system-level events.
  • Showing what changed on a record and when.
  • For automation-driven contact changes:
  • The log shows the field-level change (e.g., tag added, stage changed, DND updated).
  • The actor is often a system/automation, not a named user.
  • No workflow name or direct link is included in the log entry.
As a result, with many workflows in play, there is no scalable, built-in way to attribute a specific contact change to a specific workflow.
Why Existing Workarounds Don’t Scale
Common suggestions today include:
  • Strict workflow naming conventions.
  • Centralizing ownership of certain fields into a single “owner” workflow.
  • Using tags or custom fields as “breadcrumbs” (e.g., Changed-by:WF-XYZ).
  • Time-window correlation between logs and known workflow schedules.
These may work for a small number of automations, but with hundreds of workflows:
  • The mental and operational overhead becomes too high.
  • Breadcrumb tags/fields can clutter data and still don’t provide a clean, authoritative audit trail.
  • Time-based correlation is fragile when multiple workflows can run around the same time.
In short: these are stopgaps, not a sustainable solution for large, automation-heavy accounts.
Requested Enhancements
  1. Include Workflow Name in Audit Logs for Automation-Driven Changes
For any contact (or other object) change initiated by a workflow, add:
  • Workflow name (e.g., WF – Lead Nurture – Stage Updates).
  • Optionally, the specific action step name/ID within the workflow.
  • Display this in the Audit Log entry so admins can immediately see:
  • “Field X changed from A → B by Workflow Y.”
  1. Add a Direct Link from Audit Logs to the Workflow
In each relevant Audit Log entry, include:
  • A clickable link that opens the corresponding workflow in the builder.
This would dramatically speed up:
  • Root-cause analysis.
  • Debugging misconfigured logic.
  • Reviewing the exact automation that caused a change.
  1. Clear Actor Attribution for Automations
Distinguish clearly between:
  • Human users (e.g., “Edited by John Doe”), and
  • Automations (e.g., “Edited by Workflow: [Workflow Name]”).
  • This helps both operational teams and auditors understand whether a change was manual or automated.
  1. Expose Workflow IDs in the Automation Builder
For each automation within the automation builder:
  • expose the workflow ID in the workflow settings UI
  • this would allow for effective cross referencing with the audit logs
  1. (Optional, but powerful) Filter/Reporting by Workflow in Audit Logs
Ability to filter Audit Logs by workflow:
  • “Show me all changes made by Workflow X in the last 30 days.”
This would support:
  • Change-impact analysis before deprecating or modifying a workflow.
  • Compliance reviews for specific automations.
Impact & Justification
Scale:
  • In environments with hundreds of workflows, automation is the backbone of operations.
  • Without workflow-level attribution, the more you automate, the harder it becomes to understand and trust your data.
Audit & Compliance:
  • Many businesses must be able to answer:
  • “Who or what changed this field?”
  • “Why was this consent/DND/pipeline status updated?”
  • Today, the answer is often “a system process, but we can’t definitively say which one,” which is not sufficient for serious audits or regulatory reviews.
Risk Reduction:
  • Misconfigured workflows can silently change large volumes of data.
  • Without clear attribution, detecting and correcting these issues is slow and risky.
  • Workflow names/links in Audit Logs would significantly reduce time-to-diagnosis and blast radius of automation errors.
User Trust & Adoption:
  • Strong, transparent auditability encourages customers to:
  • Use more automation.
  • Trust the system with more critical processes.
  • Conversely, opaque automation behavior can limit adoption in risk-sensitive organizations.