Block 1 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Quick overview This workflow runs every 15 minutes, checks a VNTANA product for a new XLSX attachment with a defined filename prefix, reads attribute key and attribute value rows from the spreadshe...
n8n-nodes-base.stickynote, n8n-nodes-base.code, n8n-nodes-base.scheduletrigger, n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.spreadsheetfile
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Ben Conway.
Original n8n.io sourceThis workflow runs every 15 minutes, checks a VNTANA product for a new XLSX attachment with a defined filename prefix, reads attribute_key and attribute_value rows from the spreadsheet, and replaces the product’s attributes in VNTANA with the values from that file.
Attribute values that are JSON objects should be serialized as strings in the spreadsheet (the VNTANA API stores all attributes as string key-value pairs).
The workflow uses n8n static data to track the last processed attachment UUID, so re-uploads of the same file will not trigger a re-run unless the attachment is deleted and re-added.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Update VNTANA product attributes from scheduled Excel (.xlsx) attachments |
|---|---|
| Complexity | advanced |
| Nodes | 17 |
| Categories | Document Extraction |
| Author | Ben Conway |
| Published | 04 Jun 2026 |
Use the JSON export at /data/workflows/16129/16129.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Quick overview This workflow runs every 15 minutes, checks a VNTANA product for a new XLSX attachment with a defined filename prefix, reads attribute key and attribute value rows from the spreadshe...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Document Extraction use case.