Skip to content

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.

Paste it into your assistant. It tells you what it will send or change before it runs live.

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

  1. Shortly before your meeting, ClickRuntime searches GitHub for pull requests and issues updated in the last week.

  2. It reads the latest page in your Notion meeting notes database.

  3. AI writes a short briefing covering what shipped, what is still open and last meeting's actions.

  4. 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

RunsOn a schedule
Get a pre-meeting briefing from GitHub and Notiontoday, 9:00Succeeded
Slack · #engBriefing for planning Shipped: saved carts and the export fix. Open: 3 checkout bugs. Last week's action to update the Northwind import is still open.

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.
  • 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

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.
pre_meeting_briefing_from_github_and_notion.pyexample
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?
The most recent page in the meeting notes database you choose, or pages tagged with the meeting name.
Can it work for several meetings?
Yes. Set up one briefing per meeting, each with its own schedule, repositories and Notion filter.
How long is the briefing?
A few short paragraphs: what shipped, what is open and the actions from last time. Long enough to be useful, short enough to read in a minute.
What permissions does it need?
GitHub read; Notion read. Nothing else in your accounts is used.
Does it need AI?
Yes. It uses ClickRuntime's built-in AI, so you don't need an OpenAI or Anthropic key. Every plan includes a monthly AI allowance.
How many runs does it use?
One run each time it runs (on a schedule). Checks that find nothing to do and stop right away aren't counted.
Can I change how it works?
Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

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.