On a schedule

Get a pre-meeting briefing from Jira and Notion

Before each project meeting, Slack gets a briefing with the open Jira issues and a summary of the latest Notion notes for that project.

Runs: On a schedule
Apps: Jira, Notion
AI: Yes, uses the built-in AI allowance
Access: Jira read; Notion read

Send this to your assistant

Create a ClickRuntime automation: every Thursday at 1:45, before the Northwind project meeting, summarise open Jira issues in project NW and the latest page in my Notion Meeting notes for Northwind, and post it to #northwind.

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

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A project manager runs weekly client meetings and prepares by checking open Jira issues and rereading last week's Notion notes. When a busy morning gets in the way, they walk into the meeting unprepared and the client notices.

A briefing that combines both, posted just before the meeting, means they always walk in knowing what is open and what was promised last time.

What you get out of it

Always prepared
The briefing arrives before every meeting, however busy the day.
Promises are followed up
Last meeting's actions are summarised next to current issues. Nothing promised is quietly dropped.
One message, two tools
Jira status and Notion notes arrive together. No switching between tabs.
The whole team is aligned
Posting in the project channel means everyone joins the meeting with the same picture.

How it works

What happens, step by step

Shortly before your meeting, ClickRuntime collects the open Jira issues for the project and those resolved in the past week.
It reads the latest notes page for the project in Notion.
AI writes a short briefing covering progress, open issues and last meeting's actions.
The briefing is posted to your project's Slack channel.

Before it runs live

Connect Jira
Connect Notion and share the database you want it to use

What you get

RunsOn a schedule

Get a pre-meeting briefing from Jira and Notiontoday, 9:00Succeeded

Slack · #northwindBriefing for today's Northwind meeting The import fix shipped on Tuesday. Two issues remain open. Last week we promised a revised timeline, which is still pending.

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 Jira 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_jira_and_notion.pyexample

from clickruntime import on_trigger, credentials, http, notify, ai

JIRA, SITE = "https://api.atlassian.com/ex/jira/your-cloud-id", "https://acme.atlassian.net/browse/"
adf = lambda text: {"type": "doc", "version": 1, "content": [{"type": "paragraph", "content": [{"type": "text", "text": text}]}]}

def jira(method, path, **kw):
    resp = http.request(method, JIRA + path, headers={"Authorization": f"Bearer {credentials.connection('jira', 'work')}", "Accept": "application/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()

NOTES, PROJECT = "your-notion-database-id", "NW"

@on_trigger
def run(event):
    issues = jira("POST", "/rest/api/3/search/jql", json={"jql": f"project = {PROJECT} AND (statusCategory != Done OR resolved >= -7d)",
                  "fields": ["summary", "status", "assignee"], "maxResults": 100})["issues"]
    work = "\n".join(f"{i['key']} [{i['fields']['status']['name']}] {i['fields']['summary']}" for i in issues)
    pages = notion("POST", f"/databases/{NOTES}/query", json={"filter": {"property": "Project", "select": {"equals": "Northwind"}},
                   "sorts": [{"timestamp": "created_time", "direction": "descending"}], "page_size": 1})["results"]
    notes = ""
    if pages:
        blocks = notion("GET", f"/blocks/{pages[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"Jira issues:\n{work}\n\nLast meeting notes:\n{notes[:6000]}", max_output_tokens=500,
                        system="Write a short pre-meeting briefing: progress, open issues and risks, and actions from last meeting.").text
    notify.slack(f"Briefing for today's Northwind meeting\n{brief}", channel="#northwind")
    return {"issues": len(issues), "notes": bool(notes)}

FAQ

Common questions

Which Notion notes does it use?

The most recent page in the notes database you choose, filtered by a project property if you keep several projects in one database.

Can it run before several different meetings?

Yes. Set up one briefing per meeting, each with its own schedule, Jira project and Notion filter.

Does it include closed issues?

It focuses on open issues, plus anything resolved since the last meeting so you can report progress.

What permissions does it need?

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

The moment it happensAI