File transfers
Weik.io 2026.2Write a transfer, deploy it, choose what moves and how, read the record of every file, take it to production and react when a run ends.
On this page
A transfer moves files on a schedule between any two places rclone can reach, such as a supplier’s SFTP server and an Azure storage account, or an FTP server and a folder at your plant. You write a short YAML document and no Camel route. rclone ships inside the agent, so the site installs nothing. Every file a transfer moves leaves a log line you can read for as long as the logs are kept.
These pages follow one transfer, finance/supplier-invoices, which collects a supplier’s invoice PDFs every morning at five and moves them into Azure Blob storage.
A transfer runs on the agent at your site. Every morning at 05:00 UTC it moves the PDF files in the outgoing folder of the supplier's FTP server to the invoices/incoming folder of the invoice archive in Azure Blob storage, with retries, using rclone inside the agent. After each run the run summary goes to the channel supplier-invoices as an event, and an integration receives it and posts the invoices to the ERP's REST interface.
Pages#
weikio apply publishes it like any integration.Deploy a transfer weikio deploy runs the transfer on an agent, which writes the rclone configuration for that deployment and runs rclone on the schedule.Remotes and credentials Each end of a transfer is an rclone remote, kept in a variable or written inline, with its credentials as placeholders for secrets.Operations and filters The operation is an rclone command such as copy, move or sync, filters choose the files with patterns, and retries say how often rclone tries within one run.Runs and transferred files Every run of a transfer has an ID, a summary and a log line for each file it moved, and a failed run raises a problem that says where to look.To production Devtest and production give the same remote names different values, so weikio promote moves the tested version to production without a rebuild.React to a run Each run publishes a summary event that other integrations read with weikio-event-source, and emitPerFile adds an event for every file.