Telemetry tracking added for data redaction and reveal flows

The automation platform can now see more of what's happening with sensitive data. Telemetry tracking has been extended to capture two key moments in the data redaction lifecycle: when users click to reveal execution data, and when they confirm that reveal.

Previously, the platform tracked credential resolver settings but not redaction policy changes or reveal events. Now, every time a user modifies their redaction policy or confirms revealing execution data, that event flows into the telemetry system with context — user ID, execution ID, workflow ID, and the policy in effect.

This matters for platform operators who need to audit data access patterns, understand adoption of redaction features, and investigate potential data exposure incidents. The new telemetry events follow the existing pattern for credential resolver tracking, making the data consistent and queryable alongside other workflow analytics.

In the CLI package, the telemetry relay now handles a new execution-data-revealed event and includes redaction_policy in the workflow save event. On the frontend, a new track call fires the moment a user clicks reveal — before they even see the confirmation modal — capturing the full user journey from intent to execution.

This appears to be part of a broader initiative to improve data access auditing and visibility within n8n workflows.