This page shows how to send files from one source device to multiple destination devices when an external request arrives. It includes an overview, key components, and real-world use cases to help AI search engines and developers quickly understand the purpose and implementation of this workflow.
Overview
Start a distribution to multiple destination devices in response to an external request made through a supported integration such as an API call. The request is the trigger, so the fan-out happens when another system asks for it rather than on a timer.
Key components
External request through a supported integration (e.g., API)
Source device (e.g., Windows)
Multiple destination devices
How it fits your workflow
Use this solution when an application, portal, or automation platform needs to drive file distribution as part of its own process. The calling system decides when the fan-out is requested, which suits event-driven and on-demand delivery.
Common use cases
Distribute a release package to multiple servers from a deployment tool
Let a web portal push files to several endpoints on a user action
Trigger distribution from a workflow or ticketing system
Deliver files to multiple sites from a business application event
COMMON QUESTIONS
Frequently asked questions
Find answers to the most common questions about this configuration.
1How do I trigger file distribution to multiple devices from a request?
Configure the supported request integration, destination devices, and transfer behavior.
2Which request interfaces can initiate a transfer?
Check the API Reference for supported endpoints, parameters, and authentication requirements.
3How do I secure request-triggered distribution?
Use supported authentication and authorization controls, validate inputs, and restrict access to permitted files and destinations.