[MEGATHREAD] Workflow feature request collection

[Vogeluff]

I have searched the existing feature requests, both open and closed, to make sure this is not a duplicate request.

• Yes

The feature

I thought it would be a good idea to have a topic for all feature requests regarding workflows, as i assume there will be many ideas by many people with lots of possible duplicates. when i tested around with it there were so many ideas immediatly in my mind, which speaks to the potential of the feature in general i assume.

Platform

• Server
• Web
• Mobile

[Vogeluff]

My feature requests for workflows so far (i assume many are already in the works or atleast in the devs mind haha):

• add dynamic naming of a created/added to album based on filename with regex matching the same way its done in filename filterin
• add a scheduled trigger with some presets and manually adjuastable timing
• add the ability for one workflow to trigger another one
• add the ability for multiple triggers in one workflow (right now u have to create the same workflow twice to have all available triggers)
• tagging as a step (preferably also with the same dynamic regex from filename then mentioned before)
• person detection as a trigger
• change timestamp and other metadata as steps

[multi-suggester]

The ideas that comes to my mind is

• for cosmetic itd be nice if filters in the workflow steps were grouped rather then alphabethical imo

• auto sorting filters to top automatically in the workflow view in general (not sure if it exist or not)

• pinning or hiding some steps in steps list

• maybe changing the word "then" to "do" ? in workflow summary unless there is a reason

• perhaps the filters or steps can be generalized with a structure in the image below ?
  (its code.org building blocks basiccaly and i thought similiarish approach may be applied perhaps or not?)
  https://www.epanorama.net/newepa/wp-content/uploads/2014/09/Screenshot-2014-09-14-19.44.49.png

filter by xxx of xxx of xxx sorta?(filter by counts of tags? , filter by xxx tag? ..... , provides default modifiable blocks?)
do xxx

also perhaps for creation of steps vaiables like in api might be used perhaps?(i never used api but i feel like it can be a fast source of inspiration for potential steps or may provide a different appoach? as modifiable blocks but like i said i didnt used apis)

[multi-suggester]

also i have a feeling that we will need a way to seperate pre designed steps and custom steps for non tech savvie peoples perhaps

[isZYKerman]

#29108
#29110

[r3moob]

Feature request:

• Add support for filtering by EXIF metadata.

Example use case:

• Add support for filtering by the full file path. This would be particularly useful for external libraries, allowing files to be automatically archived, moved to locked folders, or otherwise organized based on their directory structure.

• Extend the Album action to support creating albums from file path patterns. For example:

[jonvdveen]

Yes! And because I'm not quite sure whether these things are included in EXIF metadata, I'll add:

• Tags
• Resolution (great for finding low quality images)
• Duration (helps in locating and deleting 1 second videos)

[multi-suggester]

i think the sub elements in general view can be more good looking by saying something like

"if rating is bigger then 3 then" sorta thing perhaps? , its just cosmetic tho

[r3moob]

In general, workflows could be very powerful and useful, especially with external libraries. It would also be great to have the ability to filter by any metadata, not just the metadata stored or processed by Immich. I think storing all file metadata in a JSON field and exposing it to workflows would provide a lot of flexibility.

Additionally, supporting inputs and outputs for workflow functions could unlock many more use cases. However, implementing that would likely require a significant rework of the current plugin architecture.

[nitwitt10]

• Filter by File Path
• Add Tag(s)

[laundmo]

I would love a way in the workflow to get external data back and integrate it into the metadata, like tags/description for example. I suppose this could be done using an external tool that updates things through the API, but having a built in 'get web request and write results to field' step could make sense. Perhaps with jq-like json paths to make it useable with APIs

[laundmo]

Another more power-user workflow step idea would be scripting. This would allow powerusers to create complex behaviour without needing to add tons of complex workflow steps.

[bo0tzz]

Full third-party workflow steps through https://extism.org/ will be available eventually

[Vogeluff]

another idea would be to have settings to share your workflows with other users on your istance. for example just having a toggle "share with other users" or something similar.

related but not sure about how realistic: admins could have a toggle "activate for every user"

[Eskuero]

• Trigger: cron format scheduling
• Filter: by upload date with relative values supported
• Action: Move to trash

My usecase is some family members download a shitton of Tiktok to share via other apps and the tiktok app saves them to the Camera folder. Which means they get uploaded via immich and clutter their timeline.

Thankfully they all get saved with some hex string that matches [a-z0-9]{32}.mp4

But ideally I would not want to delete them immediately after upload so as not to remove it from their phones so what I kinda want to do is

• Trigger: Daily schedule
• Filter 1: Filename matching [a-z0-9]{32}.mp4
• Filter 2: Uploaded more than a week ago
• Action: Move to trash

[Eskuero]

Another interesting thing would be ability to do dry-runs so we could test what files are passing the filters before enabling the workflow

[sonalys]

I would love to be able to filter either by a positive or negative match on a CLIP query.
This would allow people to add or not add new assets on workflows with more complex behavior like:

• Add all photos containing black cats over a match threshold to an album
• Do not add photos containing screenshots to this album

My thought is that the closer to the existing search bar functionality, the better.
So, not limited to:

• CLIP Search
• OCR

[bo0tzz]

(nb, a CLIP query has no such thing as match/no match)

[sonalys]

(nb, a CLIP query has no such thing as match/no match)

what I mean is: If that asset would appear in the results for a given context search

[kvalev]

This has been beaten to death, but still: all images will appear in the results for every context search. They will be sorted by the matching probability, meaning the images at the top will be most relevant, but if you scroll long enough you will find images that have absolutely nothing to do with the context.

[sonalys]

This has been beaten to death, but still: all images will appear in the results for every context search. They will be sorted by the matching probability, meaning the images at the top will be most relevant, but if you scroll long enough you will find images that have absolutely nothing to do with the context.

Oh, that's sad to hear. I would imagine you could calculate some highly dimentional vector distance and use it as a threshold.

I'm really looking forward towards smart pet albums.

[kvalev]

1. It should be possible to easily (even automatically) "inverse" the whole workflow. For example if I have a workflow that puts assets with a certain tag in an album, if the asset gets untagged, then it should be automatically removed from the album. Currently I think you have to have two workflows which is very annoying.

2. Once a workflow is created (but also later on), it should run on all relevant assets.

3. There should be workflow based on detected person (both detected by ML, as well as manually tagged).

4. The metadata update trigger should work on every metadata change - both after extracted from exif, as well as manually updated (e.g. via the geolocation utility)

[multi-suggester]

i think 2 should be an option (am not sure if it would create a problem and cant think of one atm but i feel like there might be cases it can cause problems)

[Vogeluff]

ability to have forks in automations to basically combine multiple ones in bigger complexer ones. if then else etc basically