Skip to content

Every 15 minutes

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

Runs
Every 15 minutes
Apps
GitHub, Notion
AI
Not needed
Access
Notion read+write; GitHub issues:write

Send this to your assistant

Create a ClickRuntime automation: every 15 minutes, find feature requests in my Notion Requests database with status Approved and no GitHub link, open an issue for each in acme/app, write the link back, and email me.

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 product manager collects feature requests from customers in a Notion database and reviews them with the team each week. Approved requests then have to be copied into GitHub, which happens slowly and sometimes not at all, and the Notion page never shows whether work has started.

Opening an issue the moment a request is approved, and linking it back, makes the hand-off instant. Customer-facing teams can follow the link from Notion to see progress without asking engineers.

What you get out of it

  • Approval leads straight to work

    An approved request becomes an issue within minutes. Nothing waits for someone to copy it.

  • Linked in both directions

    The Notion page links to the issue, and the issue links to the Notion page. Context is never lost.

  • Product decides, engineering builds

    Product managers work in Notion, engineers in GitHub. Each team stays in its own tool.

  • No duplicates

    Pages that already have a GitHub link are skipped. Each request becomes exactly one issue.

How it works

What happens, step by step

  1. Every 15 minutes, ClickRuntime looks in your Notion database for requests marked Approved that have no GitHub link.

  2. For each one, it opens a GitHub issue with the request's title, description and a link back to Notion.

  3. The issue link is written into the Notion page, so it is not created twice.

  4. You get an email listing the new issues.

Before it runs live

  • Connect GitHub
  • Connect Notion and share the database you want it to use

What you get

RunsEvery 15 minutes
Turn approved Notion feature requests into GitHub issuestoday, 9:00Succeeded
Email · 2 feature requests sent to GitHubBulk edit tags: github.com/acme/app/issues/640 Export to PDF: github.com/acme/app/issues/641

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

  • Act only on the items that match your own rules, and skip the rest
  • Add an AI step, for example to summarize, sort or draft a reply
  • 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.
turn_notion_feature_requests_into_github_issues.pyexample
from clickruntime import on_trigger, credentials, http, notify, report_fetched

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, DB = "acme/app", "your-notion-database-id"

@on_trigger
def run(event):
    pages = notion("POST", f"/databases/{DB}/query", json={"filter": {"and": [
        {"property": "Status", "status": {"equals": "Approved"}}, {"property": "GitHub", "url": {"is_empty": True}}]}})["results"]
    report_fetched(len(pages))
    if not pages:
        return {"created": 0}
    created = []
    for p in pages:
        title = "".join(t["plain_text"] for t in p["properties"]["Name"]["title"])
        desc = "".join(t["plain_text"] for t in p["properties"].get("Description", {}).get("rich_text", []))
        issue = gh("POST", f"/repos/{REPO}/issues", json={"title": title, "labels": ["feature-request"], "body": f"{desc}\n\nNotion: {p['url']}"})
        notion("PATCH", f"/pages/{p['id']}", json={"properties": {"GitHub": {"url": issue["html_url"]}}})
        created.append(f"{title}: {issue['html_url']}")
    notify.email_me(f"{len(created)} feature requests sent to GitHub", "\n".join(created))
    return {"created": len(created)}

FAQ

Common questions

Which Notion properties does it need?
A title, a Status property with an Approved option, and a URL property for the GitHub link. A description property is used for the issue body if you have one.
Can it add labels to the issue?
Yes. Every issue can get a label such as feature-request, and a Notion property like Area can be added as a label too.
Does it update Notion when the issue is closed?
Not in this version. You can ask for that as a separate step that marks the request as shipped.
What permissions does it need?
Notion read+write; GitHub issues:write. Nothing else in your accounts is used.
Does it need AI?
No. It runs without AI, so it doesn't use your plan's AI allowance.
How many runs does it use?
One run each time it checks. Checks that find nothing new 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 “Turn approved Notion feature requests into GitHub issues” from your assistant

Copy the prompt above, or connect your assistant first. Free plan, no credit card.