Every 15 minutes

Post Confluence page edits to Slack

When a page in your space is changed, your channel sees its title, who edited it and a link.

Runs: Every 15 minutes
Apps: Confluence
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: every 15 minutes, check my Confluence space DOCS and post any updated page to #docs in Slack with its title, the editor and a link.

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 Confluence page can change under your feet. A runbook is rewritten the night before an on-call shift, a spec is edited after the team agreed on it, or a process page loses a step. The people who depend on that content are not told, and the change only comes to light when something goes wrong.

Every fifteen minutes, this runs a CQL search for pages in your documentation space that were modified since the last run, posts each page's title, author and link to Slack, and stores a cursor so nothing is reported twice. People hear about edits to the pages that matter to them.

It suits documentation owners, engineering managers and compliance leads who need to know when controlled pages change. The query names your space and the time of the last run, so only real edits since then are posted, and an author's name and a link come with each one.

What you get out of it

Catch edits to runbooks before they bite
Someone on call should know the runbook changed before a night shift. A Slack post shows who edited it and gives a link to review the revision. Someone starting a night on call should know that the runbook changed, and the post shows who edited it and where to look.
Stop silent changes to agreed specs
When a spec changes after sign-off, the channel shows it. Reviewers can ask why immediately, instead of discovering the difference at implementation time. A spec that changes after sign-off is visible straight away, so reviewers can ask why before anyone implements the old version.
Know who changed what
Each post names the author, so questions go to the right person. That removes the guessing game of working out who touched a page. Each post names the author, so questions go to the right person and nobody has to work out who touched the page.
Support controlled-document processes
For policies and procedures, evidence that changes were noticed matters. The Slack history records when each edit was announced. For policies and procedures, proof that edits were noticed matters, and the channel history records when each one was announced.
Keep a team informed about its space
Everyone watching the channel sees the whole picture of activity in the space. Nobody needs to enable email notifications page by page. Everyone watching the channel sees the full pattern of activity in the space, without each person enabling page-level email watches.

How it works

What happens, step by step

Every 15 minutes, ClickRuntime checks your Confluence space for pages edited since the last check.
It only picks up edits it hasn't seen yet, so each one is posted once.
Each edit is posted to your Slack channel with the page title, who changed it and a link.

Before it runs live

Connect Confluence

What you get

RunsEvery 15 minutes

Post Confluence page edits to Slacktoday, 9:00Succeeded

Slack · #docsOnboarding checklist updated by Priya at Northwind https://northwind.atlassian.net/wiki/spaces/DOCS/pages/48211

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

page_updated_alerts.pyexample

from datetime import datetime, timezone
from clickruntime import on_trigger, report_fetched, state, notify, http, credentials

SITE = "https://northwind.atlassian.net"

@on_trigger
def run(event):
    auth = (credentials.secret("CONFLUENCE_EMAIL"), credentials.secret("CONFLUENCE_API_TOKEN"))
    now = datetime.now(timezone.utc).strftime("%Y-%m-%d %H:%M")
    since = state.get("since") or now
    pages = http.get(f"{SITE}/wiki/rest/api/content/search", auth=auth, params={
        "cql": f'space = DOCS and type = page and lastmodified > "{since}"', "expand": "version", "limit": 50,
    }).json()["results"]
    report_fetched(len(pages))
    if not pages:
        return {"summary": "No updated pages"}
    for p in pages:
        notify.slack(f"{p['title']} updated by {p['version']['by']['displayName']}\n{SITE}/wiki{p['_links']['webui']}", channel="#docs")
    state.set("since", now)
    return {"posted": len(pages)}

FAQ

Common questions

Which space does it watch?

The setup names the space, such as DOCS, in the CQL search. If you want several spaces or specific labels, your AI assistant can adjust the query and show the new version for approval. Naming the space, such as DOCS, in the search means other spaces are ignored, and adding more spaces or labels is a reviewed change.

Do small saves create posts too?

Yes, any save that updates the modified time can appear. If you want to ignore small edits by a particular user or bot, a filter can be added when you request it. Any save that updates the modified time can produce a post, and filters for a particular user or bot can be added.

Does the post show a diff of the page?

It shows the title, author and link, not a line-by-line diff. The link opens the page, where Confluence's version history can compare revisions for you. Confluence's version history compares revisions, and the link in each post takes you straight to the page where that comparison is available.

What permissions does it need?

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

Every 15 minutes