This page shows how to send files from one source device to a single destination device when an external request arrives through a supported integration. 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 transfer to one destination device in response to an external request raised by your own application through the supported integration mechanism. The request interface, the destination, and the transfer behavior are all defined in configuration.
Key components
Source device (e.g., Windows)
Single destination device
External request trigger (API)
How it fits your workflow
Use this solution to let an application or service start a file delivery at the moment its own process calls for it, instead of waiting for a clock or an operator. It connects request-driven business events to file movement.
Common use cases
Deliver a document when a user submits a form
Push a generated file when an order is confirmed
Start a transfer from a workflow automation tool
Send a file on demand from an internal portal
COMMON QUESTIONS
Frequently asked questions
Find answers to the most common questions about this configuration.
1How do I trigger a file transfer from an external request?
Integrate the supported request mechanism, configure the destination, and define the transfer behavior.
2Which external request methods are supported?
Consult the API documentation for the available request interfaces, authentication requirements, and supported parameters.
3How should I secure request-triggered transfers?
Apply the authentication, authorization, validation, and transport-security controls supported by your deployment.