Sensitive Data Masking in Logs (Runs) with Field Suffixes - Or how to hide fields in the log

I am reaching out to request a new feature that enhances the privacy and security of data processed by ActivePieces, particularly for self-hosted instances. Our company uses ActivePieces for automation workflows, which has been instrumental in streamlining our registration process. The platform’s ability to construct automation by visually assembling components and the seamless data transmission via webhooks have significantly improved our operational efficiency.

Current Situation:

We are currently leveraging ActivePieces for various workflows, including one that handles our registration process. This workflow receives initial data through webhooks, processes it, and logs each step under “Runs” with detailed input and output data. While this transparency is invaluable for debugging and monitoring, it raises concerns regarding sensitive data visibility.


Our workflows occasionally process sensitive information submitted through forms, such as personal identification numbers, financial details, health information, etc. Even in a self-hosted environment, it’s crucial for us to ensure that this type of data is not visible in logs, to comply with privacy regulations and safeguard user data.

Feature Request:

We propose a feature that allows fields to be marked with a specific suffix (e.g., “_sensitive”) in their names, indicating that the data in these fields should be masked in the logs. Instead of displaying the actual data, the logs would show a masked representation (e.g., “*****”). This feature would provide an additional layer of data protection and privacy, making ActivePieces an even more attractive solution for companies that handle sensitive information.

Examples of Sensitive Data Fields:

  • Personal Identification Numbers (e.g., social security numbers, driver’s license numbers) with a suffix “_ssn_sensitive” or “_license_sensitive”.
  • Financial Information (e.g., credit card numbers, bank account details) marked as “_cc_sensitive” or “_bankaccount_sensitive”.
  • Health Information (e.g., medical records, health insurance numbers) indicated with “_medicalrecord_sensitive” or “_insurance_sensitive”.
  • Personal Contact Information (e.g., home addresses, email addresses) suffixed with “_address_sensitive” or “_email_sensitive”.

Implementing this feature would not only help in maintaining the integrity and confidentiality of sensitive data but also assist in compliance with global data protection regulations, such as GDPR, CCPA, etc.


We believe this feature would significantly enhance the security posture of ActivePieces, especially for businesses that are committed to protecting sensitive information. It would offer an added advantage in industries where data privacy is paramount, without sacrificing the convenience and efficiency of automation workflows.

Thank you for considering this feature request. We look forward to your feedback and are excited about the possibility of this enhancement to the ActivePieces platform.

Best regards,

I love this idea! 100% agree!

Hi @dpunktdaniel,

Can you please move it to here → Issues · activepieces/activepieces · GitHub?

I believe this feature is related to the core, and I would love to get input from other developers.