Automated Image Metadata Tagging
Configured with Convert To File, Extract From File, Google Drive, Google Drive Trigger, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Transform
- AI & models
- Files / media
- Trigger
- Code
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Extract from File | Transform | Extract From File | binaryToPropery |
| Convert to File | Transform | Convert To File | toBinary |
| Analyze Image Content | AI & models | Open Ai | image / analyze |
| Download Image File | Files / media | Google Drive | download |
| Trigger: New file added to Google Drive Folder | Trigger | Google Drive Trigger | See node parameters |
| Write Metadata to Base64 Code | Code | Code | See node parameters |
| Update Image File | Files / media | Google Drive | update |
| Merge Metadata and Base64 Code | Transform | Merge | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
googleDriveOAuth2ApiopenAiApi
Workflow notes
Welcome to my Automated Image Metadata Tagging Workflow!
Welcome to my Automated Image Metadata Tagging Workflow!
This workflow automatically analyzes the image content with the help of AI and writes it directly back into the image file as keywords.
This workflow has the following sequence:
- Google Drive trigger (scan for new files added in a specific folder)
- Download the added image file
- Analyse the content of the image and extract the file as Base64 code
- Merge Metadata and Base64 Code
- Code Node to write the Keywords into the Metadata (dc:subject)
- Convert to file and update the original file in the Google Drive folder
The following accesses are required for the workflow:
- Google Drive: Documentation
- AI API access (e.g. via OpenAI, Anthropic, Google or Ollama)
You can contact me via LinkedIn, if you have any questions: https://www.linkedin.com/in/friedemann-schuetz
Automated Image Metadata Tagging
Automated Image Metadata Tagging
Purpose and structure
This folder contains the Automated Image Metadata Tagging workflow. Its executable nodes use code, convertToFile, extractFromFile, googleDrive, googleDriveTrigger, merge, openAi. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Trigger: New file added to Google Drive Folder
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/1761_Code_Extractfromfile_Automate_Triggered.json MIT; preserve source notices.