The flow
Starts it 1Logic 7Service 6
The steps in the order they run, from what starts it.
- 1Every Morning at 9amSchedule triggerStarts it
- 2Target AccountsCodeLogic
- 3Fetch FundingHttp RequestService
- 4Fetch AcquisitionsHttp RequestService
- 5Fetch Exec MovesHttp RequestService
- 6Split FundingSplit OutLogic
- 7Split AcquisitionsSplit OutLogic
- 8Split Exec MovesSplit OutLogic
- 9Funding on My AccountsCodeLogic
- 10Acquisitions on My AccountsCodeLogic
- 11Exec Moves on My AccountsCodeLogic
- 12Post Funding to SlackSlackService
- 13Post Acquisitions to SlackSlackService
- 14Post Exec Moves to SlackSlackService
How it's built
- Starts on
- A clock
- Steps
- 14
- 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. 14 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 14 steps before you point it at anything that matters.