Daily

Get a morning report on your Postman monitors

Every day you get one email listing each monitor, whether its last run passed, and how fast it responded.

Runs: Daily
Apps: Postman
AI: Not needed
Access: API key (read)

Send this to your assistant

Create a ClickRuntime automation: every day at 7am, email me each of my Postman monitors with pass or fail from its last run and the average response time.

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

An API that fails overnight is a problem for customers long before it is a problem for the team. Postman monitors run checks on a schedule, but the results sit in a dashboard that people open only when something is already wrong. A failing endpoint can quietly return errors for hours, and a developer discovers it when a customer writes in at nine, before the first coffee.

Each morning, all monitors are listed and the most recent run for each is fetched. One email shows which monitors passed and which failed, along with the time of the last run. It takes under a minute to read and tells you whether your API is healthy before the working day starts, even on mornings when nobody wants to log in anywhere.

It suits small teams that run Postman monitors but have not built full alerting, and engineering leads who want a daily check.

What you get out of it

Start the day knowing the API is healthy
A morning list of passing and failing monitors tells you whether anything needs attention before customers notice. That is a calm way to begin a working day, and a fast way to spot trouble.
Overnight failures are not left alone
A monitor that failed at three in the morning appears in your inbox when you wake. You can begin investigating before the first customer writes in about errors. That head start is the whole point.
All monitors in one place
Instead of opening each monitor in Postman one at a time, you see them in a single list. That saves minutes every day and makes sure none is forgotten during a busy week.
Monitors that stopped running show up
A monitor with an old last-run time is as worrying as a failing one. The email shows the timestamp, so a paused or broken schedule does not go unnoticed for weeks.
A daily record of API reliability
The emails pile up into a history of API health. If a customer or auditor asks about reliability, you can point to the days on which the checks passed instead of relying on memory.

How it works

What happens, step by step

Every morning, ClickRuntime lists your Postman monitors.
For each one it looks up the most recent run: whether it passed, how many checks failed and the average response time.
You get one email with a line per monitor, like "Payments API health: success (0/24 assertions failed, avg 212 ms)".

Before it runs live

Connect Postman

What you get

RunsDaily

Get a morning report on your Postman monitorstoday, 9:00Succeeded

Email · Postman monitorsPayments API health: success (0/24 assertions failed, avg 212 ms) Northwind sandbox: failed (3/18 assertions failed, avg 940 ms)

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_daily_summary_of_monitor_results.pyexample

from clickruntime import on_trigger, credentials, http, notify

API = "https://api.getpostman.com"

@on_trigger
def run(event):
    headers = {"X-Api-Key": credentials.secret("POSTMAN_API_KEY")}
    monitors = http.get(f"{API}/monitors", headers=headers).json()["monitors"]
    lines = []
    for m in monitors:
        run = http.get(f"{API}/monitors/{m['uid']}", headers=headers).json()["monitor"].get("lastRun") or {}
        stats = run.get("stats", {})
        a = stats.get("assertions", {})
        latency = stats.get("responseLatency")
        avg = f", avg {latency} ms" if latency is not None else ""
        lines.append(f"{m['name']}: {run.get('status', 'no runs')} "
                     f"({a.get('failed', 0)}/{a.get('total', 0)} assertions failed{avg})")
    notify.email_me("Postman monitors today", "\n".join(lines))
    return {"monitors": len(monitors)}

FAQ

Common questions

What does a passing monitor mean?

It means the most recent run finished with every request and test succeeding. A failing monitor had at least one failing request or test, and the email shows which monitor failed and when it last ran.

Will the email show which request failed?

The email lists each monitor and its result. Details of the failing request can be pulled from the run data and included. Let your AI assistant know if you want more than a pass or fail, and review the updated message before it goes out.

Does this run the monitors for me?

No. Monitors run on their own schedule in Postman, and the summary only reads their latest results. You still decide what is tested and how often inside Postman, and nothing about the monitors is changed.

What permissions does it need?

API key (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 (daily). 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.

Weekly