Send pre-meeting Slack briefings with Google Calendar and GitHub
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 21 nodes and runs on a schedule (every hour). Along the way it connects GitHub, Slack and Google Calendar. It also calls api.github.com and slack.com over HTTP.
How it runs
Trigger: On a schedule (every hour).
- Get events from Google calendar (Google Calendar): get many
- Format Calenda Event Payload (Code): runs custom JavaScript code
- Get Last Meeting Notes (HTTP Request): calls an HTTP API
- Is Previous Meeting (Filter): keeps only the items that match a condition
- Normalize Calendar and Payloads (Edit Fields (Set)): sets 4 fields: previousMeetingNotes, eventStart, summary…
- Add 5 minute Early Time (Code): runs custom JavaScript code
- Wait: pauses until specific time
- Extract Meeting Keywords (Code): runs custom JavaScript code
- Get PRs from Repo (GitHub): work with repository
- HTTP Request: calls api.github.com
…plus 10 more steps. See the full node list below.
Services it uses
HTTP calls to: api.github.com, slack.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (11)
- Code
n8n-nodes-base.code - Filter
n8n-nodes-base.filter - Wait
n8n-nodes-base.wait - GitHub
n8n-nodes-base.github - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack - Merge
n8n-nodes-base.merge - Google Calendar
n8n-nodes-base.googleCalendar - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
Quick Overview This workflow checks Google Calendar hourly for the next upcoming meeting, pulls recent GitHub meeting notes, finds related GitHub PRs and issues, and sends each attendee a Slack DM with a pre-meeting briefing five minutes before the event. How…