The flow
Starts it 1Logic 14Service 6
The steps in the order they run, from what starts it.
- 1Hourly Check TriggerSchedule triggerStarts it
- 2Get events from Google calendarGoogle CalendarService
- 3Format Calenda Event PayloadCodeLogic
- 4Get Last Meeting NotesHttp RequestService
- 5Is Previous MeetingFilterLogic
- 6Normalize Calendar and PayloadsSetLogic
- 7Add 5 minute Early TimeCodeLogic
- 8Wait for Time to ComeWaitLogic
- 9Extract Meeting KeywordsCodeLogic
- 10Get PRs from RepoGithubService
- 11HTTP RequestHttp RequestService
- 12Filter PRs Related to MeetingCodeLogic
- 13Merge Github issues and Github PRMergeLogic
- 14Prepare PRs and issues ListCodeLogic
- 15IfIfLogic
- 16Build Message for SlackCodeLogic
- 17Normalize Attendees and Slack MessageSetLogic
- 18Fan Out AttendeesCodeLogic
- 19Get User Slack Info from EmailHttp RequestService
- 20Check Slack User FoundIfLogic
- 21Send Meeting Context in Slack DMSlackService
How it's built
- Starts on
- A clock
- Steps
- 21, with 2 branches, 1 loop or waits
- Size
- Large: read it before trusting it with anything live
- Connects to
- GitHub, Google Calendar, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own GitHub, Google Calendar 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?
Take your time. At 21 steps it is large: read it before trusting it with anything live.
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 21 steps before you point it at anything that matters.