The flow
Starts it 1Logic 13Service 5
The steps in the order they run, from what starts it.
- 1Capture New Google Calendar EventGoogle Calendar triggerStarts it
- 2Format Calenda Event PayloadCodeLogic
- 3Get Last Meeting NotesNotionService
- 4Is Previous MeetingFilterLogic
- 5Normalize Calendar and Notion PayloadsSetLogic
- 6Add 15 minute Early TimeCodeLogic
- 7Wait for Time to ComeWaitLogic
- 8Extract Meeting KeywordsCodeLogic
- 9Get Jira Issues Related to MeetingJiraService
- 10Get PRs from RepoGithubService
- 11Merge Jira Tickets and Github PRMergeLogic
- 12Filter PRs Related to MeetingCodeLogic
- 13Prepare PRs and Jira Ticket ListCodeLogic
- 14Build Message for SlackCodeLogic
- 15Normalize Attendees and Slack MessageSetLogic
- 16Fan Out AttendeesCodeLogic
- 17Get User Slack Info from EmailHttp RequestService
- 18Check Slack User FoundIfLogic
- 19Send Meeting Context in Slack DMSlackService
How it's built
- Starts on
- An event in a connected app
- Steps
- 19, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- GitHub, Jira, Notion, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own GitHub, Jira, Notion and Slack accounts. 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. 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.
Before you run itNothing 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.