The moment it happens
Add 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.
- Runs
- The moment it happens
- Apps
- GitHub, Notion
- AI
- Yes, uses the built-in AI allowance
- Access
- GitHub webhook admin; Notion insert
Send this to your assistant
Create a ClickRuntime automation: when a new issue is opened in acme/app, have AI choose a type and priority, then add a card to my Notion Roadmap board with those properties and the issue link.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A product team plans its work on a Notion board, but bugs and requests arrive as GitHub issues. Someone has to copy each one across and decide its priority, so the board is always a few days behind the real backlog.
Adding each new issue to the board as it arrives, already labelled with a type and priority, keeps planning in step with reality. The team reviews and reorders cards instead of creating them.
What you get out of it
The board stays current
New issues appear on the board within seconds. Planning always reflects the latest backlog.
Priorities set from the start
AI suggests a type and priority from the issue text. The team adjusts rather than starts from blank.
One click back to the detail
Each card links to the GitHub issue. The full discussion is always one click away.
Product and engineering share a view
People who never open GitHub can see and discuss every issue on the board they already use.
How it works
What happens, step by step
When a new issue is opened, GitHub notifies ClickRuntime straight away.
AI reads the title and description and chooses a type and priority.
A card is created on your Notion board with the title, type, priority and a link to the issue.
Before it runs live
- Connect GitHub
- Connect Notion and share the database you want it to use
- Paste your automation's link into the other app's webhook settings
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
- Act only on the items that match your own rules, and skip the rest
- 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 clickruntime import on_event, credentials, http, verify, ai
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()
BOARD = "your-notion-database-id"
SCHEMA = {"type": "object", "properties": {"type": {"type": "string", "enum": ["Bug", "Feature", "Improvement", "Question"]},
"priority": {"type": "string", "enum": ["P1", "P2", "P3"]}}}
@on_event
def handle(event):
if not verify.github(event.body, event.header("X-Hub-Signature-256"), credentials.secret("GITHUB_WEBHOOK_SECRET")):
return {"ignored": "bad signature"}
body = event.json
if event.header("X-GitHub-Event") != "issues" or body["action"] != "opened":
return {"ignored": True}
issue = body["issue"]
t = ai.generate(f"{issue['title']}\n{(issue.get('body') or '')[:3000]}", json_schema=SCHEMA, max_output_tokens=40,
system="Classify this GitHub issue for a product board.").json
page = notion("POST", "/pages", json={"parent": {"database_id": BOARD}, "properties": {
"Name": {"title": [{"text": {"content": issue["title"]}}]}, "Type": {"select": {"name": t["type"]}},
"Priority": {"select": {"name": t["priority"]}}, "GitHub": {"url": issue["html_url"]}}})
return {"page": page["id"], **t}FAQ
Common questions
Which properties does the Notion board need?
Does closing the issue move the card?
Can it include pull requests?
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 worksGet 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.
See how it worksTurn approved Notion feature requests into GitHub issues
When a feature request in Notion is marked Approved, a GitHub issue is opened and its link is written back to the Notion page.
See how it worksKeep exploring
Set up “Add new GitHub issues to a Notion board with AI triage” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.