The flow
Starts it 1Logic 5Service 6
The steps in the order they run, from what starts it.
- 1Webhook TriggerWebhookStarts it
- 2Parse Webhook DataCodeLogic
- 3Get Device TemplatesSudo MockService
- 4Create Screenshot×Device MatrixCodeLogic
- 5Loop (2 at a time)Split In BatchesLogic
- 6Group by DeviceCodeLogic
- 7Render Device ScreenshotSudo MockService
- 8Download All ScreenshotsHttp RequestService
- 9Collect ResultCodeLogic
- 10Create ZIP ArchiveCompressionService
- 11Upload to DriveGoogle DriveService
- 12Notify TeamSlackService
How it's built
- Starts on
- Another system calling it
- Steps
- 12, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Google Drive, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Drive and Slack accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on another system calling it.
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. 12 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.
Nothing 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 12 steps before you point it at anything that matters.