Overview
Start a transfer to one destination device when an external request arrives, and run additional tasks once the transfer finishes. The request integration and the follow-up actions are part of the same workflow configuration.
Initiate a transfer to one destination device in response to an external request and configure additional actions after completion.
When should it start?
You can add more than one action.
What should happen after the transfer?
Select a development language to generate sample code for this configuration.
You can download the complete sample code for the configuration set above.
Apply the downloaded code and explore more examples.
AI-FRIENDLY EXPLANATION
This page shows how to send files from one source device to a single destination device when an external request arrives, and run follow-up actions after the transfer completes. 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.
Start a transfer to one destination device when an external request arrives, and run additional tasks once the transfer finishes. The request integration and the follow-up actions are part of the same workflow configuration.
Use this solution when a request-driven delivery has to close its own loop, for example by notifying the calling system, writing a record, or starting a downstream job. It keeps the request, the transfer, and the work that follows in one configured flow.
COMMON QUESTIONS
Find answers to the most common questions about this configuration.
Configure the supported request integration, destination, and follow-up actions.
The response depends on the API and integration design. Consult the API Reference for supported response behavior.
Check authentication, request parameters, destination configuration, and available logs.