Concepts

This section explains the core concepts behind Blober’s design. Understanding these will help you use the app effectively.

Workflows

A workflow is a saved configuration that defines:

1. Source - Where files come from (adapter + path + credentials)
2. Destination - Where files go (adapter + path + credentials)
3. Action - What to do (copy, move, sync, delete)

Workflows are templates that can be run multiple times. Each run creates a task.

See Workflows Guide for details.

Tasks

A task is a single execution of a workflow. When you start a workflow, Blober creates a task that:

• Enumerates files matching the source criteria
• Processes each file according to the action
• Tracks progress (files, bytes, status)
• Logs operations and errors

Tasks have states: pending, running, paused, completed, failed, cancelled.

See Progress Guide for details.

Actions

An action defines what happens to source files:

Action	Description	Source Files After
Copy	Duplicate files to destination	Unchanged
Move	Transfer files to destination	Deleted
Sync	Mirror source to destination	Unchanged
Delete	Remove files from source	Deleted

Path Templates

Path templates let you organize destination files dynamically using placeholders:

{file_created_date}/{filename}

This creates a date-based folder structure automatically.

Available variables include:

• {filename}, {filename_no_ext}, {file_ext}
• {file_created_date}, {file_modified_date}
• {current_date}, {current_datetime}
• {file_size}, {file_size_mb}
• {file_dir}

See Workflows Guide for the full list.

Source Filters

Filters control which files are included in a transfer:

• Include patterns: *.jpg, *.{png,gif}
• Exclude patterns: !*.tmp, !.DS_Store
• Folder patterns: documents/**

Filters use glob syntax for flexible matching.

Credentials

Each adapter requires credentials to authenticate with the provider:

• API Keys: AWS, Wasabi, Backblaze (key ID + secret)
• Connection Strings: Azure Blob
• OAuth: Google Drive, Google Photos (browser authorization)

Credentials are stored securely in your local database and never sent to Blober’s servers.