Build your automations
Organise automation into collections and scripts, then compose each script from keyboard and mouse actions that can be edited and reused whenever you need them.
Input automation
TriggerLoom
Build reusable keyboard and mouse automations, assign triggers, and run them whenever you need them.
Trigger from anywhere
Assign keyboard or mouse triggers and let TriggerLoom listen in the background, so your scripts remain available while you work, play, or use another application.
Run it your way
Run a script once, repeat it a fixed number of times, or keep it running until you trigger it again.
Stay in control
Keep track of armed collections and active scripts through TriggerLoom's compact overlay without having to return to the main application.
How TriggerLoom fits together
A collection belongs to a target app and contains one or more scripts. Each script has a trigger, a run mode, and an ordered list of steps describing the keyboard and mouse input to send.
Collection
Target app
Script
Trigger
Steps
Start here
Quick start
The usual setup is: create a collection, choose its target app, add a script, configure its trigger and steps, then enable the script and arm the collection.
1. Create a collection
Open the Collection editor from the right-hand ribbon, give the collection a name and description,
and create it. The new collection is selected for editing automatically.
2. Choose the target app
Pick a running app or enter its process details manually. TriggerLoom uses the target to make sure
automated input is only sent to the app the collection was created for.
3. Add a script
A collection can contain multiple scripts. Give each script a meaningful name and enable the scripts
you want to be available when the collection is armed.
4. Configure the trigger and run mode
Choose a keyboard or mouse trigger, then decide whether the script should run once, repeat a fixed
number of times, or keep running until the same trigger is used again.
5. Build the steps
Add keyboard, mouse-button, mouse-move, mouse-wheel, or delay steps in the order they should run.
Save the collection when you are happy with the result.
6. Arm the collection
Open Collections, make sure the scripts you want are enabled, and arm the collection. Only one collection
can be armed at a time.
Collections
Collections and target apps
Collections keep related scripts together and define the application those scripts are allowed to control.
Use one collection per app or workflow
A collection is the top-level group for your automation. For example, you might keep all scripts for one
game in one collection and scripts for a desktop application in another.
Set the target app
The process name is required before the collection can be armed. The executable path is optional and can
help distinguish applications that use the same process name.
Enable only the scripts you need
Scripts can be enabled or disabled independently. Disabled scripts stay in the collection but their
triggers are ignored while the collection is armed.
Arming activates the triggers
TriggerLoom listens for the enabled scripts in the armed collection. Only one collection can be armed at a
time, so disarm the current collection before arming another one.
The target app must be running and in the foreground
A collection cannot be armed if its target app is not running. TriggerLoom sends automated input only while
that target is the foreground app, and the collection is disarmed if the target app is closed.
Scripts
Triggers and run modes
A script describes what should happen, what starts it, and how long it should keep running.
Keyboard triggers
Choose a key and, if needed, one or more modifier keys. Modifiers are part of the trigger, so a modified
key combination is different from pressing the same key by itself.
Mouse triggers
A script can react to a mouse button or wheel direction, optionally combined with keyboard modifiers.
Run once
Runs the script steps once when the trigger is used. If the same script is already running, another trigger
does not start a second copy.
Repeat
Runs the complete list of steps the number of times you specify. A new trigger is ignored while that script
is still running.
Toggle
The first trigger starts repeating the script. Use the same trigger again to stop it. Disarming the
collection also stops active toggle scripts.
No trigger
The editor can temporarily leave a script without a trigger while you are working on it, but a keyboard or
mouse trigger is required before the collection can be armed successfully.
Steps
Building a script
Steps run from top to bottom. Reorder them to change the sequence and use delays when an application needs time between inputs.
Keyboard
Tap presses and releases a key. Key down and key up are separate actions for sequences that need to hold a
key across multiple steps.
Mouse button
Send a click, double click, button down, or button up action using the mouse button you choose.
Mouse move
Relative movement offsets the cursor from its current position. Screen position moves the cursor to a
specific screen coordinate.
Mouse wheel
Send vertical or horizontal wheel input in the chosen direction and choose how many wheel notches should be
sent.
Delays
Delay before waits before the step action. Delay after waits after it. A step can also contain only a delay
when you need a pause between other actions.
Order matters
TriggerLoom executes steps in their displayed order. Use the move controls to arrange the sequence before
saving the collection.
Overlay
Using the overlay
The overlay gives you a small always-on-top control for the collection you want available outside the main TriggerLoom window.
Choose the collection
In Collections, choose which collection the overlay should control. The overlay shows that collection and
lets you arm or disarm it without returning to the main window.
Show or hide it when needed
Use the Overlay control from Collections or Automation tools. You can also choose whether the overlay should
be shown when TriggerLoom starts.
Move and resize the experience
Drag the overlay by its top area to place it where it is convenient. The overlay size can be changed from
the Collections settings in the right-hand ribbon.
Active toggle scripts are visible
The overlay reflects the armed state and active toggle scripts so you can see when repeating automation is
currently running.
Utilities
Automation tools
The Automation tools view contains a few supporting actions for managing or creating collections outside the visual editor.
Import collection
Copy valid collection JSON to the clipboard and import it as a new collection. TriggerLoom validates the
content and assigns new IDs before saving it.
Open collection folder
Opens the local folder where collection JSON files are stored. This is useful for inspecting or backing up
your saved collections.
Copy generation prompt
Copies a starter prompt that can be used with an AI assistant to generate collection JSON in the format
TriggerLoom expects.
Show or hide the overlay
The same tools view also gives you direct control over whether the overlay is currently visible.
Troubleshooting
When something does not run
Most problems can be narrowed down by checking the armed collection, script state, trigger, and target app.
The collection will not arm
Check that a target app is configured and currently running. Every script must also be valid, with a name,
trigger, and at least one usable step.
A trigger does nothing
Make sure the correct collection is armed, the script is enabled, and the target app is in the foreground.
For keyboard triggers, also check that the configured modifier keys match what you are pressing.
Automation stops when switching apps
This is expected. TriggerLoom does not send automated input while the configured target is not the foreground
app. Return to the target before continuing the automation.
A toggle script needs to stop
Use the same trigger again to stop that toggle script, or disarm the collection to stop all currently running
scripts in the collection.
Recent edits are missing
Save the collection after editing its details, target app, scripts, triggers, or steps before moving on to
another collection.
Imported JSON is rejected
The imported collection must match TriggerLoom's expected structure and pass the same validation used by the
visual editor. Use Copy generation prompt as a starting point when creating JSON externally.