Define how the Upload File to Website Action behaves when sending files to a remote server. Control whether execution continues immediately, waits for a server response, or applies a delay depending on how the upload result is used in your workflow.
These settings also determine how response codes and timeouts are handled, helping ensure reliable file uploads when working with authenticated endpoints, large files, or slower network conditions · Flow handling explained
| Flow | Details |
|---|---|
| After request | After the Upload File to Website Action sends a request, choose how the workflow should proceed:
Waiting is recommended when the upload result or server confirmation is needed while immediate continuation is suitable for background or non-critical file uploads. |
| Enable waiting timeout | Optionally, to prevent an unintended workflow lockdown (in case the Upload File to Website Action is waiting indefinitely), set the Do not wait longer than timeout value option and choose a procedure to perform when On timeout is reached… |
| On timeout | Choose behavior if the Upload File to Website Action times out:
|
| Process response codes | Define how specific server response codes are handled during execution:
Handle HTTP response codes (such as 401, 403, or 500) based on how critical a successful file upload is for your workflow. |
| Time units |  Define and set a time frame in your preferred format—be it milliseconds, seconds, minutes, hours, or days. |
| Variable Wizard |  Use dynamic data input—substitute a parameter from a file, web, connected Trigger, other Actions, date and time presets, etc. |
Note
- Currently, the Wait for server response option is the recommended and fully supported flow control option.
Ask for more…
If you have any questions, please do not hesitate to contact our support team.