- Pull files from external directories into the flow
- Push files from the flow into external directories
Key Capabilities
- Local and network file system integration with UNC path support
- Configurable authentication for protected network locations (.NET edition only)
- Advanced filtering with glob patterns and recursive directory support
- Temporary file handling with staging and rename operations for reliable transfers
- Optional caching to ensure only new or updated files are downloaded
Overview
Each File connector is configured with a path on disk that determines what folder it reads files from or writes files to. This can be a local file path or a UNC path to access other file locations on the network. When a File connector receives a file from the configured path, it passes the received file off to the next connector in the flow without modifying the file. In this way, File connectors can be used to poll an external folder location for files to pull into the flow. When a file in the flow is processed by a File connector, that file is written to the folder at the configured path. In this way, File connectors can be used to drop off processed files at a location external to the application. File connectors can be configured with username/password credentials to provide access to external filepaths that otherwise would not be accessible to the application. This allows to pull files from protected folder locations without needing to grant the entire application access to the protected location. The path configured in the File connector can be dynamically populated using macros. For more information, see the Macros section.Connector Configuration
This section contains all of the configurable connector properties.Settings Tab
Connector Settings
Settings related to the core operation of the connector.Receive
Settings related to pulling files from the external filepath.Authentication
Caching
Settings related to caching and comparing files between multiple downloads. When you enable caching, the file names are case-insensitive. For example, the connector cannot distinguish between
TEST.TXT and test.txt.Advanced Tab
Advanced Settings
Settings not included in the previous categories.Logging
Miscellaneous
Automation Tab
Automation Settings
Settings related to the automatic processing of files by the connector.Performance
Alerts Tab
SLAs Tab
Establishing a Connection
File connectors must have the appropriate permissions to read/write from the configured path. Permissions issues are primarily a concern when the configured path is a UNC path to another server on the network, but can also arise when pushing or pulling files from a protected folder on the local disk. If the user running does not have permission to access the path, set the Username, Password, and Domain fields in the Authentication section of the Settings tab to a specific user with the appropriate permissions.Sending and Receiving Files
Sending Files
The File connector sends files from the Transactions tab to the external folder specified in the configured path. Files are automatically sent if Send is enabled on the Automation tab.Receiving Files
The File connector receives files from the external folder specified in the configured path and places them in the connector’s Transactions tab. If the File connector is connected to another connector in the flow, the file does not remain in this folder and is instead passed along to the next connected connector. The connector automatically polls the external folder for files if Receive is enabled on the Automation tab. The connector only pulls files that match the specified File Mask. If Enable Timestamp Comparison or Enable File Size Comparison is enabled, the connector caches file names pulled from the remote path and only receives files that are new or have been modified since they were last received.Subfolder Headers
If Recurse Subdirectories is set to True, when receiving a file:- The message for the received file contains a Subfolder header in its metadata.
- This header contains the subfolder, relative to the configured path, that the file was received from.
- This subfolder header is supported by other connectors that support a Subfolder header in Send operations.
- The file is placed in the subfolder (relative to the path setting in the File connector) that is specified in the subfolder header.
- The subfolder is created if permissions are available.