On a schedule
Get a pre-meeting briefing from GitHub and Notion
Before each engineering meeting, Slack gets a short briefing with recent pull requests and issues and the latest notes from your Notion meeting page.
- Runs
- On a schedule
- Apps
- GitHub, Notion
- AI
- Yes, uses the built-in AI allowance
- Access
- GitHub read; Notion read
Send this to your assistant
Create a ClickRuntime automation: every Monday at 9:45, before our 10 o'clock planning meeting, summarise last week's PRs and issues in acme/app and the latest notes in my Notion Meetings database, and post it to #eng.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A team lead prepares for a weekly planning meeting by opening GitHub to see what moved, then Notion to find last week's notes and actions. The preparation takes twenty minutes and often does not happen, so the meeting starts with everyone catching up.
A briefing posted just before the meeting brings both sources together. Everyone arrives knowing what shipped and which actions were promised last time, and the meeting starts with decisions.
What you get out of it
Meetings start informed
Everyone reads the same briefing before joining. Less time is spent recapping.
Last week's actions are remembered
Notes from the previous meeting are summarised alongside the work. Promises are checked rather than forgotten.
Two sources, one message
GitHub progress and Notion notes arrive together. Nobody has to open both.
Timed to the meeting
The briefing arrives shortly before the meeting starts, when people are most likely to read it.
How it works
What happens, step by step
Shortly before your meeting, ClickRuntime searches GitHub for pull requests and issues updated in the last week.
It reads the latest page in your Notion meeting notes database.
AI writes a short briefing covering what shipped, what is still open and last meeting's actions.
The briefing is posted to your #eng Slack channel.
Before it runs live
- Connect GitHub
- Connect Notion and share the database you want it to use
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Run it at a different time, more or less often, or only on weekdays
- Change what the AI looks for, or how it writes the result
- Add another app, for example also send it to Slack
- Combine it with other GitHub and Notion steps into one automation
Under the hood
The code that runs this automation
from datetime import date, timedelta
from clickruntime import on_trigger, credentials, http, notify, ai
def gh(method, path, **kw):
resp = http.request(method, f"https://api.github.com{path}", headers={
"Authorization": f"Bearer {credentials.connection('github', 'work')}", "Accept": "application/vnd.github+json"}, **kw)
return resp.raise_for_status() or (resp.json() if resp.content else None)
def notion(method, path, **kw):
resp = http.request(method, f"https://api.notion.com/v1{path}", headers={
"Authorization": f"Bearer {credentials.secret('NOTION_TOKEN')}", "Notion-Version": "2022-06-28"}, **kw)
return resp.raise_for_status() or resp.json()
REPO, MEETINGS = "acme/app", "your-notion-database-id"
@on_trigger
def run(event):
since = date.today() - timedelta(days=7)
items = gh("GET", "/search/issues", params={"q": f"repo:{REPO} updated:>={since}", "per_page": 50})["items"]
work = "\n".join(f"{'PR' if 'pull_request' in i else 'Issue'} #{i['number']} [{i['state']}] {i['title']}" for i in items)
page = notion("POST", f"/databases/{MEETINGS}/query", json={"sorts": [{"timestamp": "created_time", "direction": "descending"}], "page_size": 1})["results"]
notes = ""
if page:
blocks = notion("GET", f"/blocks/{page[0]['id']}/children")["results"]
notes = "\n".join(t["plain_text"] for b in blocks for t in b.get(b["type"], {}).get("rich_text", []))
brief = ai.generate(f"GitHub work:\n{work}\n\nLast meeting notes:\n{notes[:6000]}", max_output_tokens=500,
system="Write a short pre-meeting briefing: what shipped, what is open, and last meeting's actions and their status.").text
notify.slack(f"Briefing for planning\n{brief}", channel="#eng")
return {"items": len(items), "notes": bool(notes)}FAQ
Common questions
Which Notion notes does it read?
Can it work for several meetings?
How long is the briefing?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Back up workflows to GitHub and document them in Notion
Each week your workflow definitions are saved to GitHub, and every changed workflow gets a plain-language description in your Notion database.
See how it worksFlag Notion docs that are older than your latest release
When a new release ships on GitHub, Slack lists the Notion docs pages for that product that have not been updated since before the release.
See how it worksAdd new GitHub issues to a Notion board with AI triage
Every new GitHub issue appears on your Notion board with a type and priority already set, and a link back to GitHub.
See how it worksKeep exploring
Set up “Get a pre-meeting briefing from GitHub and Notion” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.