Actions3
- Anonymize Actions
- Deanonymize Actions
Overview
This node integrates with an external anonymization service to either anonymize or deanonymize data. Specifically, for the File Anonymization operation under the "Anonymize" resource, it processes binary file data to anonymize sensitive information within files. This is useful in scenarios where you need to protect personal or confidential data before sharing or storing files, such as anonymizing medical records, legal documents, or customer data files.
Practical examples include:
- Uploading a PDF containing personal information and receiving back an anonymized version with sensitive details masked.
- Processing images or other binary files to remove identifiable metadata or content.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports only "API Key". |
| Input Binary Field | The name of the input binary field that contains the file to be anonymized (e.g., "data"). |
Output
The node outputs JSON data representing the result of the anonymization process. The output JSON typically includes the anonymized content or metadata returned by the external service.
If the node processes binary files, the output may also include binary data fields containing the anonymized file content, allowing downstream nodes to handle or save the anonymized files.
Dependencies
- Requires an external anonymization API service accessed via an API key credential.
- The node depends on a custom service class (
AnymizeCustomService) that handles communication with the anonymization API. - Users must configure the node with a valid API key credential to authenticate requests.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Incorrect input binary field name may lead to errors or empty results because the node cannot find the file data.
- Network or service downtime can cause request failures.
Error messages:
- Errors from the external service are caught and returned in the output JSON under an
errorproperty. - Typical error messages might indicate authentication failure, invalid input format, or service unavailability.
- Errors from the external service are caught and returned in the output JSON under an
Resolutions:
- Verify the API key is correctly set and has necessary permissions.
- Ensure the input binary field name matches the actual incoming binary data field.
- Check network connectivity and service status of the anonymization API provider.
Links and References
- No direct links provided in the source code. For more information, consult the documentation of the anonymization API service used by this node.