The flow
Starts it 2Logic 2Service 12
The steps in the order they run, from what starts it.
- 1When Every 15 MinutesSchedule triggerStarts it
- 2When Contract SignedTurbo Docx triggerStarts it
- 3Fetch Contracts from ExcelMicrosoft ExcelService
- 4Fetch Signed Contract PDFTurbo DocxService
- 5Loop Over ContractsSplit In BatchesLogic
- 6Store PDF in SharePointMicrosoft Share PointService
- 7Generate Agreement DocxTurbo DocxService
- 8Update Signed Status in ExcelMicrosoft ExcelService
- 9Request Slack ApprovalSlackService
- 10Notify Slack of Signed ContractSlackService
- 11If Approved in SlackIfLogic
- 12Convert Agreement to PDFTurbo DocxService
- 13Update Rejected Status in ExcelMicrosoft ExcelService
- 14Send Agreement for E-SignatureTurbo DocxService
- 15Update Sent Status in ExcelMicrosoft ExcelService
- 16Notify Slack of Sent ContractSlackService
How it's built
- Starts on
- A clock
- Steps
- 16, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Excel, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Excel and Slack accounts. 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. 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.