Dear TriggerCMD
I am looking to use TriggerCMD to pass parameters to a vbscript file for execution.
I see from the video that each parameter is used by specifying %1.

A few more questions:
1, I have used the parameter field in Zapier and called notepad only to see that notepad was not aware that it needed to open the file, so it appears that the parameter is not being passed?
2, How are parameters separated when specifying more than one? (is it just a space like on the cmd line?)
3, Are there only nine parameters that can be passed like with batch files?
4, Is there an upper limit on the number of characters sent?
Thanks for the great functionality
Jonathan

https://www.integromat.com has a good idea with their agent\app on the https://www.integromat.com/en/integrations/ios and even better on the Android https://www.integromat.com/en/integrations/android but with the flexibility of your solution and your automation focus, you would be a much more attractive all round management platform.

@Russ said in HTTP POST:
If you enable that feature on the agent itself rather than in the cloud, it would be secure by default. I'm thinking it should be a boolean flag on each command which would default to false, and like you said, the GUI should warn the user about turning it on.

Yes this arguments functionality could work well at the time of agent deployment and it does sure up the security with the functionality being disabled by default and only enabled on a task by task basis on the agent. Maybe the warning should also point the user to an article online that helps them to understand the vulnerability they would be opening up. A boolean flag sounds good and simple.
This would be a good strategery while access to agents via the cloud is still controlled by a key string.
I would, however, suggest that all task initiation channels are checked and enabled and documented for arguments to be passed to each task so that the Task and local Command can use it. E.g. POST commands and Zapier... (after thought: that probably did not need to be said)
This arguments functionality would revolutionise your solution with developers and automation specialists integrating your solution. I am one who would be using it in a production implementation right away.

Hi Russell
You are probably aware already that you are onto something of a special thing with your Triggercmd agent, and as soon as you manage to deploy to android and iPhone I believe you are going to get allot of interest from investors because you would then have a foothold and ability across all major platforms.

Just by installing an accessible agent on a device wipes out the most robust form of security, which is inaccessibility. Then opening channels\triggers over the agent diminishes the security further.
I believe security needs to come at the point of accessing the exposed webhook\agent on the device and not in limiting the functionality. By allowing variables you are enhancing your potential market place to automation specialists. The ability to only initiate a static predefined trigger is very restrictive.

Your concern is warranted, as there is a posibility of a breach in security especially because a simple key does not offer much of a security blanket. Maybe offer a warning that if the end user "enables" variables on a trigger he is increasing his risk. Maybe upgrade accessibility security to certificates as used by virtual private networks. Maybe limit the originating request to zapier and other trusted services.

If you gave me the option in my use case I would enable variables.
Thanks for considering it.
Jonathan

May I ask if I am able to send variables that are passed to the "Command" on the localhost just like a Tasker HTTP Post action?
It would be really great if I could send three variables and if possible up to five because this means that I can call scripts with variables that can do multiple things.
Many thanks
Jonathan