Run a Postman Collection Folder
run_folderExecute all requests in a Postman collection folder, resolve variables, run pre-request scripts, and return structured test results.
Instructions
Execute every request in a collection folder and return structured results. Resolves {{variables}}, runs the collection + item pre-request scripts (so token auth works), fires each request, and evaluates the embedded pm.test scripts. Target the folder by folderName (typically the Jira ticket key, e.g. 'JIRA-12345') or folderId.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| folderId | No | Explicit folder id (use when folder names are ambiguous). | |
| collection | Yes | Postman collection v2.1 JSON (the `collection` object from the Postman API / connector's getCollection). | |
| folderName | No | Folder name to run (typically the Jira ticket key). | |
| allowWrites | No | Explicitly allow POST/PUT/PATCH/DELETE requests for this exact run. | |
| environment | No | Optional Postman environment JSON (the `environment` object from getEnvironment) supplying base URL, auth and variables. | |
| approvalNote | No | Short note naming who/what approved the target and methods. | |
| allowProduction | No | Explicitly allow production-like target URLs/auth URLs for this exact run. | |
| timeoutRequestMs | No | Per-request timeout in ms (default 30000). |