Monitors can run your collection once per data row in a single cloud run — the same iteration model as the Collection Runner, on a schedule. Monitor data files are Solo+, limited to 1 MB and 50 rows, and must be uploaded in the monitor configuration. When your needs exceed fixed files — larger data, reuse across CI, or live queries — see Use datasets with a collection run in the next module.
Create a monitor with a data file
You'll point a new monitor at your collection and environment, then upload the same CSV so each scheduled run tests all three movies.
-
Click the Services tab in the left sidebar.
-
Click +, then select Monitor.
-
Enter the Monitor name:
textMovies Data File Monitor -
For What to monitor?, select Movies API — Data Driven.
-
Under How to run the monitor?, leave On Schedule selected and pick a frequency — Every day at a fixed time works well (or Every hour).
-
Leave Runner on Auto-select.
-
For Environment, select Data Files — without it,
{{baseUrl}}can't resolve in the cloud. -
Under Iteration data, open the dropdown and select Upload a datafile. Choose
movies.csvfrom Step 2 and confirm the file appears with three rows in the preview. -
Expand Notifications and confirm failure alerts go to your email address.
-
Click Create Monitor.
Expected outcome: The monitor appears under Monitors in the Services sidebar, and Postman kicks off the first run immediately when you click Create Monitor. Give it a minute to finish — you'll confirm the results in the next step.
Run the monitor and confirm data-driven iterations
A monitor without a data file executes the collection once. With three rows attached, one manual run should execute three requests — proof the file drove multiple iterations.
- Select Movies Data File Monitor in the Services sidebar.
- Click Run and wait for the run to finish (three GET requests usually complete in under a minute).
- Open the run results and confirm 3 requests executed and all tests passed.
Troubleshooting: If the run shows only 1 request, the data file likely wasn't attached — edit the monitor, re-upload movies.csv under Iteration data, and run again.