The moment it happens

Save articles to a Notion reading list

Send a link and get a summary saved to your Notion reading list, with a note in Slack.

Runs: The moment it happens
Apps: Notion, Slack
AI: Yes, uses the built-in AI allowance
Access: Notion insert; Slack chat:write

Send this to your assistant

Create a ClickRuntime automation: give me a link I can send article URLs to. Summarise each article, add it to my Reading List database in Notion, and tell me in Slack.

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

Someone in the team finds an article, a competitor's pricing page or a regulation update and pastes the link into chat with a note saying this is interesting. Few people click, nobody records it, and the same link is shared again a month later by someone else. Reading long pages takes time most people do not have, so useful material is passed around without being understood or filed.

When a URL is sent to the link ClickRuntime provides, it fetches the page text, uses its built-in AI to write a summary of the main points, creates a Notion page containing the title, source URL and summary, and posts a short notice in Slack with the page link. The whole path takes about a minute.

It is useful for research, sales and strategy teams that read a lot and want what they read to be kept.

What you get out of it

Pages are understood in thirty seconds
The summary gives the main points so people can decide whether to read the original. A colleague who would never open a long report reads three sentences. A colleague who would never open a long report will read three sentences and decide if it matters to them.
Shared links are kept in one place
Every URL sent in becomes a Notion page with its source. The team's reading list is searchable rather than scattered through chat history. The team's reading list becomes searchable instead of being scattered across chat history and browser tabs.
Duplicates are easy to spot
Because each link has a page, searching for it shows whether someone shared it before. The same article stops circulating under different names. The same article stops circulating under different titles and being summarised three separate times.
Research gets a head start
When starting a project, you can search the collection for relevant summaries. Background reading that took days to gather is already assembled. Background reading that would have taken days to gather is already assembled and waiting.
Slack alerts keep the team informed
A short message tells people something new was added and where to read it. Nobody has to ask what was shared on Friday. Nobody has to ask what was shared on Friday while they were out.

How it works

What happens, step by step

When you send a link to your private ClickRuntime address, the automation starts.
It fetches the page and reads its title and text.
AI writes a three-sentence summary of the article.
The article is added to your Notion reading list with the summary, and a note in your #me Slack channel shows the title and summary.

Before it runs live

Connect Notion and share the database you want it to use
Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Save articles to a Notion reading listjust nowSucceeded

Slack · #me📚 Added to Reading List: How Acme scaled support without hiring They moved FAQs into the product and…

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
Change what the AI looks for, or how it writes the result
Add another app, for example also send it to Google Sheets
Combine it with other Notion and Slack 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.

url_to_notion_page_summary_with_slack_alert.pyexample

from bs4 import BeautifulSoup
from clickruntime import on_event, credentials, http, ai, notify

DATABASE_ID = "your-reading-list-database-id"

@on_event
def handle(event):
    url = (event.json or {})["url"]
    soup = BeautifulSoup(http.get(url).text, "html.parser")
    title = (soup.title.string or url).strip() if soup.title else url
    text = " ".join(p.get_text(" ", strip=True) for p in soup.find_all("p"))[:12000]
    summary = ai.generate(f"{title}\n\n{text}", max_output_tokens=250,
                          system="Summarise this article in 3 sentences for a reading list.").text
    page = http.post("https://api.notion.com/v1/pages",
                     headers={"Authorization": f"Bearer {credentials.secret('NOTION_TOKEN')}", "Notion-Version": "2022-06-28"},
                     json={"parent": {"database_id": DATABASE_ID}, "properties": {
                         "Name": {"title": [{"text": {"content": title[:200]}}]}, "URL": {"url": url},
                         "Summary": {"rich_text": [{"text": {"content": summary[:2000]}}]}}}).json()
    notify.slack(f"📚 Added to Reading List: {title}\n{summary}\n{page['url']}", channel="#me")
    return {"page": page["id"]}

FAQ

Common questions

How do I send a URL?

Post it to the ClickRuntime link from a browser bookmarklet, a Slack workflow, a shortcut on your phone or any tool that can make an HTTP request with the URL in it. Each URL arrives as a simple request.

Does it work on paywalled or login-protected pages?

It can only read what a plain web request can see. Pages behind a login or paywall return limited text, so the summary may be thin or the run may fail. Public articles and documentation work best.

How long are the summaries?

Typically a short paragraph and a few key points. You can ask for something shorter or longer, or for particular details, such as prices or dates, to be pulled out of every page. Only pages that load as plain text can be summarised well.

What permissions does it need?

Notion insert; Slack chat:write. 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 for each event the app sends.

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