Quick overview
This workflow watches a Google Drive review folder for AI-generated assets, fingerprints each file with a SHA-256 hash, generates an EU AI Act Article 50 disclosure manifest, and logs everything to Google Sheets, routing items for Gmail-based human sign-off when required.
How it works
- Triggers when a new file is created in a specific Google Drive review folder.
- Reads disclosure settings from a Google Sheets Settings tab, downloads the file from Google Drive, and calculates a SHA-256 hash of the file contents.
- Classifies the asset by MIME type/extension and determines which EU AI Act Article 50 disclosure duties apply, including whether human sign-off is required.
- Builds a JSON disclosure manifest (including a visible label and schema.org JSON-LD) and saves it back to the Google Drive review folder beside the asset.
- Writes or updates a row in a Google Sheets Register tab with the file details, hash, duties, manifest file ID, reviewer, and current status.
- If sign-off is required, sends the reviewer an email via Gmail with what to confirm and instructions to mark the row as signed off in the register; otherwise, moves the file straight to a Google Drive approved folder.
- Runs hourly to read the register, moves newly signed-off files to the approved folder, and updates the register to mark them as moved/published with a timestamp.
Setup
- Create Google Drive folders for review and approved content, then paste their folder IDs into the workflow where indicated.
- Create a Google Sheets spreadsheet with a Settings tab (Organisation, Role, Generation Tool, Label Wording, Publishes Public Interest Content, Reviewer Email) and a Register tab with the columns listed in the workflow notes.
- Add Google Drive and Google Sheets credentials in n8n and set the correct spreadsheet ID in all Google Sheets steps.
- Add a Gmail credential and ensure the reviewer email in the Settings tab is valid and can receive the sign-off notifications.