Weekly

Back up your Postman collections every week

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

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

Send this to your assistant

Create a ClickRuntime automation: every Sunday at 10pm, export all collections in my Postman workspace as JSON and email them to me.

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

Postman collections hold months of a team's work: requests, tests, examples, pre-request scripts and documentation. Yet they live in one workspace, tied to one account. A deleted collection, a careless merge or a lost login can wipe them out, and the first sign is a developer asking where the payments collection went. Many teams only discover that no copy exists at the moment they need one.

Once a week, the collections in your workspace are listed and each one is fetched in full. The JSON for every collection is attached to an email addressed to you, so you hold a portable copy of your API work outside Postman. If something goes wrong, the file can be imported straight back into a workspace.

It suits developers and small teams who keep important API tests and documentation in Postman and want an inexpensive safety net.

What you get out of it

Recover quickly from accidental deletion
If a collection is removed or overwritten, you can import the latest backup. At worst you lose a week of edits, instead of the whole body of work that took months to build.
A copy that does not depend on your account
The JSON in your inbox exists outside Postman. If access to the workspace is lost because of a departed admin or a locked account, your requests and tests remain available to import elsewhere.
Versions you can compare over time
Weekly files show how a collection evolved. When a bad edit breaks a test suite, you can compare against an older copy and see exactly which request or script changed.
A snapshot for audits and handover
A dated backup shows the state of your API tests at a point in time. It also gives a new team a clean starting file when a project is handed over to another group.
No manual exporting to forget
Exporting each collection by hand is easy to postpone, and the week you skip it is the week something breaks. A weekly email makes the routine happen without anyone remembering.

How it works

What happens, step by step

Every Sunday, ClickRuntime lists all the collections in your Postman workspace.
It downloads each collection in full, with every request and folder.
Each collection arrives in your inbox as its own email containing the complete export, which you can import back into Postman if needed.

Before it runs live

Connect Postman

What you get

RunsWeekly

Back up your Postman collections every weektoday, 9:00Succeeded

Email · Postman backup: Refunds API{"info": {"name": "Refunds API", "schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"}, "item": [ ... ]}

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

import json
from clickruntime import on_trigger, credentials, http, notify

API = "https://api.getpostman.com"
WORKSPACE_ID = "1f0df51a-8658-4ee8-a2a1-d2567dfa09a9"

@on_trigger
def run(event):
    headers = {"X-Api-Key": credentials.secret("POSTMAN_API_KEY")}
    collections = http.get(f"{API}/collections", params={"workspace": WORKSPACE_ID},
                           headers=headers).json()["collections"]
    sent = 0
    for c in collections:
        full = http.get(f"{API}/collections/{c['uid']}", headers=headers).json()["collection"]
        body = json.dumps(full, indent=1)
        if len(body) > 95_000:
            body = body[:95_000] + "\n... truncated, collection is larger than one email"
        notify.email_me(f"Postman backup: {c['name']}", body)
        sent += 1
        if sent == 10:  # email limit per run
            break
    return {"collections": len(collections), "emailed": sent}

FAQ

Common questions

Does the backup include environments and secrets?

Collections are backed up. Environments can hold tokens and passwords, so they are not included unless you ask for them. If you do add them, store the emails carefully, because they may then contain sensitive values.

How do I restore a collection from the email?

Open Postman, choose Import and select the JSON attachment. The collection reappears with its folders, requests, tests and examples as they were when the backup ran. You can restore one collection or several, and keep the current version alongside.

Can it cover more than one workspace?

It covers the workspace you point it at. For several workspaces, instruct your AI assistant to list them all or set up one per workspace, and review the plan before it goes live so you know where each file will come from.

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 (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