Send Files to Many Devices on a Recurring Schedule With Follow-Up Actions

Overview

Distribute files from a single source device to multiple destination devices on a recurring schedule, and perform additional tasks after the transfer completes. The recurrence drives the run and the follow-up actions cover the work that belongs after each delivery.

Key components

• Source device (e.g., Windows)
• Multiple destination devices
• Recurring schedule
• Follow-up actions (after transfer)

How it fits your workflow

Use this solution when a repeating distribution also needs a step on the other side, such as notifying a team, reloading a service, or starting a script that consumes the delivered files. The transfer and the task that depends on it stay inside a single recurring workflow.

Common use cases

• Push daily data sets to multiple servers and start an import routine
• Refresh content on several endpoints and clear local caches afterwards
• Deliver weekly exports and notify the teams that consume them
• Update application files on multiple hosts and restart the service