The building blocks

Condition: One question about a file. File Name Filter → Extension Is checks an exact extension, such as jpg. File Type Filter selects categories such as images.
Condition set: A named collection of conditions that selects files. It does not change tags.
Action: One operation, such as Add Tags. Adding tags keeps other existing tags.
Workflow: A named list of actions. Actions run sequentially, from first to last; later actions can change earlier results.
Rule: Connects a condition set with a workflow. Attach both to the rule; creating them in the editor alone does not connect them.
Automation: An ordered list of rules linked to a folder. Every matching enabled rule runs in order.

Example of the building blocks

One folder, two kinds of images

Here is how those parts work together. This is an example to help you understand them; you do not need to set it up to continue reading.

Create JPEG files with File Name Filter → Extension Is jpg OR Extension Is jpeg.
Create Add Photo tag with an Add Tags action containing Photo. Connect both items in the first rule.
Create TIFF files with Extension Is tif OR Extension Is tiff.
Create Add Print tag with Print under Tags to Add. Use Add Rule to connect these items in a second rule in the same automation.

holiday.jpg receives Photo; poster.tiff receives Print. Enter one extension per condition without a dot. Matching ignores case.

AND requires every condition to match. OR accepts any matching alternative, including files that satisfy more than one. OR does not mean exactly one.

If any enabled condition set on a rule matches, its workflows run once. OR selects files; workflow actions still run sequentially.

Preview: Check a condition match or proposed tags without changing the sample.
Play: Process existing files in the automation’s folder. This changes tags but does not enable monitoring.
Monitoring: Check new and changed files automatically while Taggy Tagger is running and the automation is enabled. Existing files need Play.
Activity: View processing results and errors. This is history, not undo.

Select a saved condition set or workflow on another rule to reuse it. Always check both selections on each rule.