The Wait for Remote Directory Action conditionally pauses a workflow until a specific remote directory is created (or already exists) or removed (or already is absent), with additional options to wait for the directory to be empty or contain files.
This Action allows waiting for remote directories using FTP, SFTP, FTPS, and WebDAV file transfer protocols, as well as popular cloud storage platforms such as Amazon S3, Google Cloud, Backblaze B2 Cloud Storage, and any platform supporting the S3 protocol, like Dell ECS Enterprise Object Storage solution.
Wait | Details |
---|---|
Directory | Provide the directory name for which the workflow will wait. |
Condition | Choose the condition that, once satisfied, will allow the workflow to continue immediately:
|
Use connection | Select an existing connection to use for the directory waiting operation. If there are no defined connections, the new connection window will be opened to establish a connection to FTP, SFTP, WebDAV, Amazon S3, Google Cloud Storage, or DigitalOcean Spaces server. |
Variable Wizard | Use dynamic data input—substitute a parameter from a file, web, connected Trigger, other Actions, date and time presets, etc. |
Interconnect
- Wait for Remote Directory integration and auditing—Variables (dynamic data) and Events (recorded activity). Access the directory name and completion status. Log information events to indicate whether the waiting condition was met or a timeout occurred.
Delay options…
Automation Workshop includes options to pause a workflow and conditionally wait for different resource types. These waiting Actions operate similarly—they pause the workflow until a particular resource reaches a desired state, such as when a file appears or disappears.
- Wait · Overview
- Wait for Time · Overview
- Wait for Remote File · Overview
- Wait for File · Overview
- Wait for Folder · Overview
- Wait for Service · Overview
- Wait for App · Overview
Questions?
If you have any questions, please do not hesitate to contact our support team.