Command Line Interface

Command Line Interface

Run a transfer without opening the window — handy for scripts, cron jobs, or Windows Task Scheduler. The CLI reuses the exact same tasks and destinations configured in the GUI (settings.json) — there's nothing separate to set up.

1clickTransfer — command line

Usage:
  1clickTransfer --task "Name"      send that task (repeat --task for several)
  1clickTransfer --all              send all enabled tasks
  1clickTransfer --list             list saved tasks
  1clickTransfer --silent           no console output (exit code only)
  1clickTransfer --help             this help

With no arguments, opens the normal window.
Exit codes: 0 = ok, 1 = some failure, 2 = usage error.
Tasks and destinations are those configured in the app (settings.json).

Short aliases also work: -t for --task, -a for --all, -l for --list, -s for --silent, -h/-?//? for --help.

Examples

# Send one specific task by name
1clickTransfer --task "Nightly Backup"

# Send several tasks in one call
1clickTransfer --task "Nightly Backup" --task "Language Files"

# Send every enabled task (same as clicking TRANSFER)
1clickTransfer --all

# See what's configured before automating it
1clickTransfer --list

# Silent run for a scheduled task — only the exit code matters
1clickTransfer --all --silent

Exit codes

Code	Meaning
0	Everything requested was sent successfully (or there was nothing to do).
1	At least one file/destination failed.
2	Usage error (e.g. --task given with no name, or an unrecognized flag).

Platform notes

• Windows: run 1clickTransfer.exe --task "Name" directly, from cmd, PowerShell, or a scheduled task's "Program/script" field.
• Linux: ./1clickTransfer-linux-x64 --task "Name" (make sure it's executable: chmod +x).
• macOS: the CLI binary lives inside the .app bundle at 1clickTransfer.app/Contents/MacOS/1clickTransfer — that's the path to invoke from a script or cron/launchd, not the .app itself.

Using it with Task Scheduler / cron

Because the CLI writes exit codes and (optionally, unless --silent) console output, it works naturally as a script step:

• Windows Task Scheduler: set the Program/script to the full path of 1clickTransfer.exe, and Add arguments to something like --all --silent.
• cron (Linux/macOS): a line like 0 * * * * /path/to/1clickTransfer-linux-x64 --all --silent runs it hourly.

The CLI does not require the GUI to be closed — you can run --task/--all while the window is open at the same time; they don't conflict with each other.