@Russ My screenshot is a .lnk shortcut as well - of Chrome opening with the URL of this discussion in a maximized window.

Zoom level is pretty moot because, unless wants to change a commonly viewed site, pretty much all browsers remember the zoom level of all sites visited. He can go to whateversite.com, set the zoom to 175%, and when the shortcut opens the site, it will be at 175%.
The clicking or scrolling is another, more complicated matter.

@Russ The request for #1 was "launch a shorcut, webpage or .exe" so creating a shortcut this way covers it, no? The shortcut I just created opens a maximized window in Chrome to this page.
My only point being that it might not be necessary to reinvent the wheel. OP would still need to work out the zoom (but remember that browsers remember the zoom level of a given website so that pretty much covers the second step).

@Russ Could you create a shortcut with that parameter and start the program by calling the shortcut?

@Russ It's a spammer -- the new method they're doing is to not actually link the crap they're spamming. More subtle but still crap.

@Convaiyer Every trigger has a Paywall button. I've had no luck thinking of a way to use it because who wants to pay me to run a command on my own PC? I mean, you'd have to pay me to play Fortnite but other than that

@Russ ‍️Not sure what the bottleneck was but I've been distracted prepping for a short camping trip.

I just realized I didn't restart the PC and, lo and behold, the install went fine. Not sure what was preventing the installer from running.

(Distracted enough that I never hit Submit on this until I just got back)

Hi, Russ. I saw in the New comments that you'd posted an update so went to install it. The app updating itself failed so I downloaded the new installer.

The install failed and I wanted to prune down the log so that only that attempt was in there (less clutter) so I cleared it out and went to reinstall again BUT, when it failed, the log was empty. That said, there were multiple mentions in the log of not having access to "C:\Users\User\AppData\Local\Discord" which seemed odd but I set that folder for Everyone's access which didn't help.

Any ideas?

(Fully updated Win11 Home)

@Russ Yes, just the .json into a clean install. Seemed safest.

I've un/reconnected the Triggercmd Smart home skill. It re-found the triggers on my less-used other computer but nothing from the new one. After some fiddling, it finally kicked in - I think setting a voice name finally did it.

It was just Alexa -- "triggers work on the PC and from the dashboard here" (this site)

Banana set to run notepad was added into Alexa within seconds. Which got me thinking and what I did was Cut out all my content from my .json, saved, ensure that the triggers disappeared from the Alexa app, repasted them back in, saved, and they all showed up ... AND WORKED.

Thanks for your help.
Saying "good night" to Alexa and having her turn off my monitors (smart plug) and hibernate the PC (trigger) is a big part of my routine.

@Russ Been trying that since last night and now the Alexa app won't rediscover them at all now, "organically" or even when I try to force detection.

@Russ Necroposting as this is pretty much on target for me. Replaced my old computer with a newer one, copied everything over ... triggers work on the PC and from the dashboard here. I've made the new one the default and even deleted the old one but the devices in Alexa aren't triggering. I thought I might need to delete them and let them be rediscovered so I tried that and the newly-discovered ones aren't working.

I'm scratching my head here.