The flow
Starts it 1Logic 5Service 6
The steps in the order they run, from what starts it.
- 1When clicking 'Execute workflow'Manual triggerStarts it
- 2Set Document InputSetLogic
- 3Fetch Document ContentHttp RequestService
- 4Prepare Document for AICodeLogic
- 5Score Documentation with AIHttp RequestService
- 6Parse AI Compliance ReportCodeLogic
- 7Route by Compliance StatusSwitchLogic
- 8Build Slack ReportCodeLogic
- 9Slack, FAIL Alert (Engineering Channel)Http RequestService
- 10Slack, WARNING Alert (Review Channel)Http RequestService
- 11Slack, PASS Notice (Docs Channel)Http RequestService
- 12Log Result to Google SheetsGoogle SheetsService
How it's built
- Starts on
- An event in a connected app
- Steps
- 12, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Google Sheets
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Sheets account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
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.