The flow
Starts it 1Logic 8Service 6
The steps in the order they run, from what starts it.
- 1Daily Employee SyncSchedule triggerStarts it
- 2Fetch HR EmployeesHttp RequestService
- 3Check API ResponseIfLogic
- 4Expand Employee ListCodeLogic
- 5Teams Alert - API FailureMicrosoft TeamsService
- 6Split EmployeesSplit In BatchesLogic
- 7Map Employee FieldsCodeLogic
- 8Is Active Employee?IfLogic
- 9Prepare Coda RowSetLogic
- 10Set Teams Message (Inactive)SetLogic
- 11Create/Update Employee in CodaCodaService
- 12Teams Notify - Employee InactiveMicrosoft TeamsService
- 13Set Teams Message (Active)SetLogic
- 14Teams Notify - Employee SyncedMicrosoft TeamsService
- 15Slack Notify - New EmployeeSlackService
How it's built
- Starts on
- A clock
- Steps
- 15, with 2 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack 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. 15 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 15 steps before you point it at anything that matters.