The flow
Starts it 1Logic 5Service 5
The steps in the order they run, from what starts it.
- 1Configure ValuesCodeLogic
- 2When Every 15 MinutesSchedule triggerStarts it
- 3Merge Config and TriggerCodeLogic
- 4Post Auth to VNTANAHttp RequestService
- 5Post Search AttachmentsHttp RequestService
- 6Check Newest AttachmentCodeLogic
- 7If New File ExistsIfLogic
- 8Fetch Attachment FileHttp RequestService
- 9Parse Spreadsheet DataSpreadsheet FileService
- 10Build Attribute ArrayCodeLogic
- 11Update Product AttributesHttp RequestService
How it's built
- Starts on
- A clock
- Steps
- 11, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 11 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Before you run itNothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 11 steps before you point it at anything that matters.