The flow
Starts it 1Logic 9Service 7
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Get FeedbackHttp RequestService
- 3Split OutSplit OutLogic
- 4Edit FeedbacksSetLogic
- 5Change survey ID according NicereplyAi TransformService
- 6FilterFilterLogic
- 7Set Empty Respondent to "Unknown Client"CodeLogic
- 8Change happiness valueAi TransformService
- 9Without CommentIfLogic
- 10Switch - Type of TeamSwitchLogic
- 11Switch - Type of Team1SwitchLogic
- 12Happiness ValueSwitchLogic
- 13Happiness Value2SwitchLogic
- 14Send to SupportMicrosoft TeamsService
- 15Send to Team Lead1Microsoft TeamsService
- 16Send to Support1Microsoft TeamsService
- 17Send to Team LeadMicrosoft TeamsService
How it's built
- Starts on
- A clock
- Steps
- 17, with 5 branches
- 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. 17 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 17 steps before you point it at anything that matters.