Skip to content
ClickRuntime

Automate Postman

Postman holds your collections and runs monitors against your APIs, and most of what teams want from it on a schedule is a quick read of that state: which monitors passed overnight, which collections someone edited, how close the account is to its usage limits. ClickRuntime pulls those answers out of your workspace and sends them to your inbox or chat. Tell your AI assistant what you want to hear about, review the plan it shows you, and from then on the checks happen on their own.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

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.

Ideas

What you can automate in Postman

A morning pass/fail report for your monitors, quick word when one breaks, a weekly record of collection edits and JSON backups, and a warning before you run out of API calls. These are ready-made starting points. Anything else you can describe works too.
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.

See how it works
Every 15 minutes

Hear about failed monitor runs in Slack

When a monitor run fails, your channel gets one message about it, not a repeat on every check.

See how it works
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.

See how it works
Weekly

Back up your Postman collections every week

Each Sunday a JSON export of every collection in the workspace arrives in your inbox.

See how it works
Daily

Get warned before you hit Postman's usage limits

You get an email the first time any of your account's usage limits passes the threshold you chose.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Postman, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Postman automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Postman should do in your own words, with your conditions, other apps or an AI step, and 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.

For example, ask your assistant

Every 30 minutes, check my Postman monitor results and alert me with the failing requests if any test failed.

Every morning, post a summary of last night's Postman monitor runs to Slack with pass and fail counts per collection.

Every night, check Postman monitor results, log pass rates in Google Sheets, and create a Jira ticket for any endpoint that failed three nights in a row.

Beyond chat

Have Postman work when you're not in the chat

Connecting Postman to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Postman

Postman connects with a personal API key that you generate in your own Postman settings. The key acts as you, so it reaches every workspace and collection your account can.

Postman

Developer / API tooling

  1. In Postman, click your avatar and open Settings, then API keys.
  2. Choose Generate API Key, give it a name such as clickruntime, and set an expiry if you want one.
  3. Copy the key straight away. Requests send it in the X-API-Key header.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the key as a secret for Postman.

Good to know

Postman limits that affect automations

  • A personal API key carries every permission your Postman user has, so anything an automation does is done as you.
  • Requests are capped at 300 per minute per user, and some endpoints have tighter limits.
  • Your Postman plan sets a monthly API call quota. Frequent polling and full collection exports both draw from it, so a 15-minute monitor check costs more than a daily summary.
  • SCIM provisioning uses a separate key, so user and group management is not covered by this connection.

FAQ

Questions about automating Postman

What does ClickRuntime read from Postman?
Whatever your API key can reach: your workspaces, collections, monitors with their latest runs, and your account's usage against its limits. The ready automations here only read. Nothing gets edited unless you ask for an automation that does it.
Postman already emails me about monitor failures. Why add this?
Built-in alerts are fine for a single monitor. ClickRuntime is useful when you want one daily roll-up of every monitor with response times, alerts posted to a team channel, or failures reported once per incident instead of on every run.
Will these automations use up my monthly API calls?
They do count, because every request against the Postman API is counted. A daily summary uses a handful of calls, while a backup uses one per collection. If you are near your quota, there is an automation that warns you when any limit crosses a threshold you pick.
Can I back up collections to somewhere other than email?
Yes. The emailed backup is plain text, so a very large collection may be cut short. Ask your assistant to save the exported JSON to cloud storage or a repository you have connected instead.
Is AI involved in the Postman automations?
None of the ready ones need it, since they report pass/fail, dates and counts. If you want a written summary of what changed, the AI included in every ClickRuntime plan handles it with no AI key of your own.
Is this a Postman connector for ChatGPT or Claude?
Not for chatting with Postman data. A chat connector lets your assistant read and change Postman while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Postman event.

Related pages

Keep exploring

Tell your assistant what Postman should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude