Postman Monitors vs Newman CLI: Persisting Environment Variables During Scheduled Runs

Answer the Core Question

1. Monitors do not persist changes. When a monitor starts, Postman takes a snapshot of the selected environment. Any variable updates made during the run are written to the in‑memory copy only and discarded when the run finishes. The next scheduled run starts again with the original values stored in the Postman account.

2. No built‑in persistence. Because the snapshot is immutable, there is no documented way for a monitor to automatically carry forward updated values. Workarounds rely on external storage or manual steps.

3. Newman can keep the environment in sync. Running the collection with --environment test.env.json --save-environment updated.env.json writes the modified variables back to updated.env.json. That file can then be uploaded to Postman via the API (POST /environments or PUT /environments/{id}) or used as the environment for a new monitor.

Confirmed Facts

• All current Postman Monitor releases snapshot the environment at run start.
• Newman’s --save-environment flag writes any runtime changes to a JSON file.
• Postman’s REST API can update environments programmatically.

Practical Steps (Newman + API)

1. Run Newman:

   newman run collection.json \
     --environment test.env.json \
     --save-environment updated.env.json
   

2. Upload the updated file to Postman:

   curl -X PUT \
     -H "X-Api-Key: YOUR_POSTMAN_API_KEY" \
     -H "Content-Type: application/json" \
     -d @updated.env.json \
     https://api.getpostman.com/environments/:environment_id
   

3. Configure the monitor to use the updated environment (or trigger the upload in a CI job before the monitor runs).

Possible Workaround for Monitors Alone

• Use a pre-request script to read a value from an external key‑value store (e.g., Postman’s own environment via the API, a database, or a file served over HTTP) and set it in the environment before each request.
• This approach does not persist the value back to Postman but ensures each monitor run starts with the latest data.

Missing Diagnostic Detail

To tailor the recommendation further, could you confirm whether the environment you use for monitors is a personal or a team/shared environment? The API endpoints differ slightly, and rate limits apply to shared environments.

Diagram

Component
Monitor Snapshot
Environment Persistence
Newman Save‑Environment
Postman API Sync