Deploy on every release tag
Connect
SPIRITT
TRIGGERcmdTRIGGERcmd
Your machines, on cue
SPIRITT runs the commands you have set up in TRIGGERcmd exactly when they are needed. Backups after hours, restarts during incidents, deploy scripts after releases and room setups before meetings.
What you can do with TRIGGERcmd.
Commands with perfect timing
Saved commands run on schedules, after releases or when another app reports a problem.
Every machine in reach
Office PCs, home servers and workstations are listed and targeted by name.
Panels turned into routines
Panel buttons become steps in larger workflows that span your other apps.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for the machine routines you want handled.
02
Connect TRIGGERcmd
Connect TRIGGERcmd with your token so SPIRITT can see your computers, commands and panels.
03
Delegate an outcome
Say when each command should run. SPIRITT wires the timing to your apps and keeps a log.
Hand over a mission.
Choose a mission. Make it yours.
Put TRIGGERcmd to work.
Your computers, working on schedule.
Questions
TRIGGERcmd, with SPIRITT.
01What can SPIRITT do with TRIGGERcmd?+
List your computers, commands and panel buttons, and trigger any saved command or panel button, with parameters where the command accepts them.
02How do I connect TRIGGERcmd?+
Connect it with your TRIGGERcmd token. Your commands stay defined on your own computers.
03Which commands can SPIRITT run?+
Exactly the commands and panel buttons you have configured in TRIGGERcmd. You decide what exists; SPIRITT decides when, based on your rules.
04What can start a command?+
A schedule, a release, an incident, a calendar event or a change in another connected app that SPIRITT watches.
05Can I pass values to a command?+
Yes, for commands set up to accept parameters, such as a file name or version tag.
06Is there a record of what ran?+
SPIRITT logs each run with time, machine and reason in the place you choose, such as Google Sheets.