Weekly

See which collections changed this week

On Monday you get a list of the collections in your workspace that were edited during the past seven days.

Runs: Weekly
Apps: Postman
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: every Monday at 9am, email me the Postman collections in my Payments workspace that were updated in the last 7 days, with when each was changed.

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

On a team where several people edit shared Postman collections, changes happen without any announcement. A request is renamed, a test assertion is quietly removed, a new folder appears, an example response is replaced. Nobody is told. A colleague then finds on Friday that the request they relied on has changed, or a lead realizes that a critical collection was edited for weeks without a single review.

Once a week, collections are listed with their updatedAt times and those modified in the last seven days are kept. One email names each collection that changed and when it was last touched. It takes a minute to read, and it tells you where work actually happened in the workspace instead of where people say it did.

It suits team leads, QA engineers and API owners who share collections with several editors and want light oversight without meetings.

What you get out of it

See where work happened this week
A list of edited collections shows which APIs are changing. You can look closer at anything unexpected before a surprise turns into a broken integration or a failing test run.
Notice edits nobody reviewed
Important test suites should not drift unobserved. When a critical collection appears in the digest and nobody mentioned it, that is a prompt to ask what changed and why. That one line often prevents a long debugging session.
Keep documentation in step
When an API collection is edited, its published docs and examples may be out of date. The weekly list reminds owners to review related pages instead of waiting for a customer to report a mismatch.
Know who to ask
Seeing which collection changed tells you whom to ask when something stops working. That saves a round of guesswork in chat and shortens the time to find the cause. Time saved there adds up across a team.
Oversight without another meeting
A short weekly email replaces a standing check-in about collection edits. Leads stay informed with almost no effort, and teammates keep their autonomy to work in the shared space. Trust between teammates grows too.

How it works

What happens, step by step

Every Monday, ClickRuntime lists the collections in your Postman workspace along with when each was last updated.
It keeps the ones edited in the past seven days.
You get one email listing each changed collection and when it was updated, newest first.

Before it runs live

Connect Postman

What you get

RunsWeekly

See which collections changed this weektoday, 9:00Succeeded

Email · Collection changesRefunds API: updated 2026-10-16 14:02 Acme checkout flows: updated 2026-10-14 09:40

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

get_a_weekly_digest_of_collection_changes.pyexample

from datetime import datetime, timedelta, timezone
from clickruntime import on_trigger, credentials, http, notify

WORKSPACE_ID = "1f0df51a-8658-4ee8-a2a1-d2567dfa09a9"  # Payments workspace

@on_trigger
def run(event):
    resp = http.get("https://api.getpostman.com/collections", params={"workspace": WORKSPACE_ID},
                    headers={"X-Api-Key": credentials.secret("POSTMAN_API_KEY")})
    resp.raise_for_status()
    since = (datetime.now(timezone.utc) - timedelta(days=7)).isoformat()
    changed = sorted((c for c in resp.json()["collections"] if c["updatedAt"] >= since),
                     key=lambda c: c["updatedAt"], reverse=True)
    lines = [f"{c['name']}: updated {c['updatedAt'][:16].replace('T', ' ')}" for c in changed]
    notify.email_me(f"{len(changed)} Payments collections changed", "\n".join(lines) or "No changes this week.")
    return {"changed": len(changed)}

FAQ

Common questions

Does it show who made each change?

The list shows the collection and its last update time. Where Postman supplies the editor's name for your plan, it can be added to the line. Give your AI assistant if you want it included and review the updated message first.

Are deleted collections mentioned?

No, a deleted collection no longer appears in the workspace listing, so it cannot be reported as changed. A weekly backup is the better protection against deletion, and the two can run side by side.

Can I watch only specific collections?

Yes. You can restrict the digest to a named set, such as your billing and authentication collections, and ignore the rest. Give the names to your AI assistant and confirm the result before it replaces the live one.

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 runs (weekly). 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.

Daily