The flow
Starts it 1Logic 13Service 2
The steps in the order they run, from what starts it.
- 1When clicking ‘Execute workflow’Manual triggerStarts it
- 2Set VariablesSetLogic
- 3Get EntraID Applications and SecretsHttp RequestService
- 4Split Out ApplicationsSplit OutLogic
- 5Split Out Client SecretsSplit OutLogic
- 6Split Out CertificatesSplit OutLogic
- 7Filter Client SecretsFilterLogic
- 8Filter Client CertificatesFilterLogic
- 9Build Client Secrets ReportSetLogic
- 10Build Certificates ReportSetLogic
- 11MergeMergeLogic
- 12AggregateAggregateLogic
- 13If Expiring Secrets not emptyIfLogic
- 14HTML Table with Expiring SecretsHtmlLogic
- 15No Operation, do nothingNo OpLogic
- 16Send emailEmail SendService
How it's built
- Starts on
- An event in a connected app
- Steps
- 16, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Email
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Email 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. 16 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 16 steps before you point it at anything that matters.