I have a free account - a subscription is not in the budget for me. From what I can find on various Postman article, free accounts should be able to run Manual Collection Runs with local files. This is perfect - I want this. I want to run a single collection for user creation and deactivation with a local CSV file.
I click ‘Run’ then make sure ‘Run Manually’ is selected, and when I click ‘Select File’ a paywall appears that will not let me continue without a minimum $9 a month Solo subscription. Even though apparently Free accounts can run up to 25 Collections per month with only local files?
I am unable to get past the paywall to run my collection. I can confirm I have not exceeded my 25 collections per month. When I check resource usage, I have used nothing recently:
But I am locked out of running a collection run with a locally hosted file by the paywall. Can anyone advise at all?
Edited to Add some extra Clarity:
I am 1 person, I am not sharing or collaborating. There is noone else in my ‘Team’ but me - I know the free account is now limited to non-sharing which is totally fine.
I have tried creating a ‘restricted’ workspace that is just accessible to me (in case there was an issue with the old ‘my team’ style workspace) and the same issue applies when I try to perform a collection run via that workspace too.
The Free plan gives you access to a number of different features on the platform including Unlimited Collection Runs, however more advanced automation features like Data Driven Testing and Reporting within the platform is part of the Solo plan.
You can still use the Postman CLI to run your Collections with a data file using the -d flag.
postman collection run <collectionFile> -d <data.csv>
With the built-in terminal, it can be run inside the platform.
Thank you for your reply, however Terminal is disabled for me by my organisation. I do not understand why we cannot just run the collections via the interface the same way we did previously - if unlimited collection runs are part of the free package? The file path itself is also locally hosted - e.g. c:\users\myname\documents\postman\file.csv, so I assume (if I were able to run the command - which I can’t) that I would need to include the whole path in the command? Or would I set the source folder in my settings?
Edited for more clarity, also to add: I have no interest in reporting or any of the other aspects - I literally just need to be able to run collection runs to perform bulk updates to my system as the UI doesn’t really support these and I have 8000+ user records I need to be able to administrate - sometimes in bulk. My sole purpose for using Postman is running manual collections. I don’t even want to schedule them. I want to run them myself during specific downtime windows.
Using the terminal, either inside or outside of Postman, feels more like a question that needs to be directed at your organisation. That’s not something that I would be able to help with.
Using data files with the Collection Runner, is not part of the Free plan. It’s part of the Solo plan.
Perhaps I’ve misunderstood - I thought uploading data files into the environment was part of solo but locally hosted via the client were part of the free plan? This is a shame as I had to go through quite a rigorous IG review to allow me to use this software within our org, but terminal access is very much restricted (At least currently). I have discussed a subscription with my organisation but there is no budget unfortunately.
Data Driven Testing is part of the Solo plan, which includes using all data files with the Collection Runner, inside the platform.
The comparison table on the pricing page shows what is included in each plan.
If you’re able to get full terminal use on your machine cleared by your organisation, you will be able to run the Collection with a data file using the Postman CLI.
You also have the option of using the Postman CLI in a pipeline, GitHub Actions for example. That could replicate using the terminal.
