Import: Create WebDav independent (transport agnostic) version of PHOTOPRISM_AUTO_IMPORT #2467

New issue

Open

opened 2026-02-20 01:12:01 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-20 01:12:01 -05:00

Owner

Originally created by @kgara on GitHub (Jan 1, 2026).

Confirmation

I checked this request against the roadmap and existing issues

What Problem Does This Solve and Why Is It Valuable?

Currently PHOTOPRISM_AUTO_IMPORT triggered job only imports the content of the import folder after the WebDAV initiated upload event (correct me if I am wrong).
Actually it seems strange that we don't have it yet. Maybe I don't know some under the hood considerations or something.

What Solution Would You Like?

I think we should make a scheduled auto import feature independent from WebDAV.
E.g. I use separate SCP/SFTP sync to an import folder. And would love to have a scheduled import trigger. I have it now, but as a compromise I am obligated to call REST API import method and hence keep the admin credentials or a token on the host running the REST call job.

What Alternatives Have You Considered?

As an alternative we could also make a separate scope for the tokens limited to import job triggering only or make it authentication less (worst option).

Additional Context

No response

Originally created by @kgara on GitHub (Jan 1, 2026). ### Confirmation - [x] I checked this request against the roadmap and existing issues ### What Problem Does This Solve and Why Is It Valuable? Currently PHOTOPRISM_AUTO_IMPORT triggered job only imports the content of the import folder after the WebDAV initiated upload event (correct me if I am wrong). Actually it seems strange that we don't have it yet. Maybe I don't know some under the hood considerations or something. ### What Solution Would You Like? I think we should make a scheduled auto import feature independent from WebDAV. E.g. I use separate SCP/SFTP sync to an import folder. And would love to have a scheduled import trigger. I have it now, but as a compromise I am obligated to call REST API import method and hence keep the admin credentials or a token on the host running the REST call job. ### What Alternatives Have You Considered? As an alternative we could also make a separate scope for the tokens limited to import job triggering only or make it authentication less (worst option). ### Additional Context _No response_