Automated Media Anonymization with BlurIt - n8n Workflow

Media companies and security firms needing to anonymize large volumes of video or photo data automatically.
Developers looking for robust n8n templates integrating specialized AI services.
Users requiring automated GDPR or privacy compliance for visual media.
Anyone needing an automated n8n workflow that handles file upload, API polling, and secure file retrieval.

This powerful n8n workflow solves the problem of manual face and license plate blurring by automating the entire process using the BlurIt API.

The automation begins with a simple form upload, making it easy for non-technical users to initiate the anonymization task. Once triggered, the n8n node sequence securely authenticates, uploads the media, and monitors the processing status using a sophisticated polling loop built with core n8n logic. This design ensures that even long video processing tasks are reliably managed. By leveraging this n8n template, users can integrate specialized visual anonymization capabilities directly into their existing business processes, saving time and ensuring regulatory compliance without custom coding.

The process begins when a user submits a file through the Upload Input File n8n trigger, which is an external Form Trigger.

1. Authentication & Configuration: The workflow first runs the Set Auth Config n8n node to define the BlurIt API credentials. This is immediately followed by the Auth Get Token n8n node, an HTTP Request, which uses these credentials to retrieve the necessary Bearer token for all subsequent API calls.


2. Data Preparation: A Merge n8n node combines the binary media data received from the initial n8n trigger with the authentication token.


3. Task Creation: The Create Blurit Task n8n node (an HTTP Request) uploads the merged file to the BlurIt service, instructing it to activate blurring for both faces (activationfacesblur) and license plates (activationplatesblur). This step returns a job ID.


4. Status Polling Loop: The workflow enters a polling sequence to monitor the asynchronous job. It starts with a Wait n8n node (set to 2 seconds) to avoid rate limiting. The Get Task Status n8n node then checks the job ID.


5. Conditional Routing: A Switch n8n node analyzes the returned status. If the status is 'Succeeded', the flow proceeds to download the result. If the status is 'Pending...', the flow loops back to the Wait n8n node, repeating the check until completion. If the status is 'Failed', the workflow terminates via the 'Task Failed' output.


6. Result Retrieval: Upon successful completion, the Get Result File n8n node uses the output media URL (provided by the status check) and the authentication token to download the final, anonymized binary file.

To deploy this n8n workflow and start processing media, follow these steps:

1. Import the n8n template: Copy the provided JSON code and import it into your n8n instance using the 'New' menu -> 'Import from JSON'.


2. Configure Credentials: Double-click the Set Auth Config n8n node. Replace the placeholder values ([REPLACEBYYOURCLIENTID] and [REPLACEBYYOURSECRETID]) with your actual BlurIt Client ID and Secret ID. These are required for the Auth Get Token n8n node to succeed.


3. Activate the n8n trigger: Double-click the Upload Input File node (Form Trigger) to retrieve the unique Test and Production webhook URLs. Use these links to upload media once the workflow is active.


4. Activate the Workflow: Set the workflow to 'Active' in your n8n dashboard. Execute the workflow manually or navigate to the form URL and upload a test file.

This n8n workflow utilizes several key nodes to manage the data flow, authentication, and polling logic:

Upload Input File (Form Trigger): This is the initiating n8n trigger. It provides a public form endpoint for users to upload a single image or video file, starting the entire automation process.
Function: Accepts binary file data as input.
Key Configuration: Configured as a Webhook Form, requiring one input file field named inputmedia.

Set Auth Config (Set n8n node): Stores static API configuration details, including the base URL, client ID, and secret ID.
Function: Centralized storage for connection parameters, referenced by subsequent HTTP Request n8n nodes.

Auth Get Token (HTTP Request n8n node): Handles the API authentication process.
Function: Sends a POST request with the Client ID and Secret to the /login endpoint to acquire the Bearer token, which is critical for authorizing the next steps in this n8n workflow.

Create Blurit Task (HTTP Request n8n node): The core processing initiation step.
Function: Uploads the input binary file (inputmedia) using multipart-form-data and sets the necessary blurring options (faces and plates are enabled).

Merge (Merge n8n node): Combines the file data stream from the n8n trigger with the token stream from the authentication step, ensuring both are available for the Create Blurit Task node.

Wait (Wait n8n node): Introduces a mandatory delay during the polling cycle.
Function: Pauses the execution for 2 seconds before checking the task status again, preventing excessive API calls.

Switch (Switch n8n node): Manages the conditional routing based on the task status returned by the API.
Function: Routes data based on the $json.status value (Succeeded, Failed, or Pending...). The 'Pending...' route loops back to the Wait node, implementing the essential polling logic of this n8n workflow.

Get Result File (HTTP Request n8n node): Downloads the final processed media file.
Function: Retrieves the anonymized output file using the URL provided in the successful task status response, authorized by the Bearer token.