The flow
Starts it 1Logic 14Service 4
The steps in the order they run, from what starts it.
- 1Every 15 Minutes TriggerSchedule triggerStarts it
- 2Set Configuration ParametersSetLogic
- 3Fetch Last Run TimestampCodeLogic
- 4Query Updated Rows from PostgresPostgresService
- 5Aggregate Postgres ResultsCodeLogic
- 6Check Rows to SyncIfLogic
- 7Construct Graph Batch PayloadsCodeLogic
- 8Update Timestamp No RowsCodeLogic
- 9Loop Over Batch PayloadsSplit In BatchesLogic
- 10Dispatch Sync Summary NoteMicrosoft TeamsService
- 11Post Batch to Graph APIHttp RequestService
- 12Process Looped ResultsCodeLogic
- 13Verify Batch API ResponseCodeLogic
- 14Check for Errors in RunIfLogic
- 15Prepare Next BatchNo OpLogic
- 16Remove Duplicate AlertsCodeLogic
- 17Refresh Last Run TimestampCodeLogic
- 18Check for New AlertIfLogic
- 19Send Sync Error AlertMicrosoft TeamsService
How it's built
- Starts on
- A clock
- Steps
- 19, with 3 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Postgres
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Postgres 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. 19 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 19 steps before you point it at anything that matters.