Key-based connection

This connector signs in to an SFTP server with a private key rather than a password. A Beam agent uses the stored key to open the session, reads the directories your rule allows, and works only within the paths you name. Each connection and action is logged. If the key is rejected, the host fingerprint changes, or a path your rule does not permit is requested, the agent stops and routes the case to an administrator, who checks the key, the server identity, or the permissions before any transfer resumes, so a silent authentication problem never turns into missing files.

Scheduled file pickup

Many partners leave files in an SFTP folder for you to collect on a cadence. The agent connects on schedule, reads the target directory, and applies your rule for which files to take by name, date, or size. It downloads the matching ones, records what it moved, and notifies the owner. Files that arrive half written, carry an unexpected name pattern, or exceed a size your rule flags are left in place and reported to a person, who confirms the file is complete and correct before the agent picks it up on the next pass.

Outbound file delivery

Sending a file to a partner means placing it in the right SFTP folder with the right name. When your workflow produces an export, the agent connects with the key, applies your naming and destination rule, and uploads the file to the agreed path. It logs the delivery and notifies the recipient's contact if you ask. Exports headed to a new destination, larger than a set limit, or missing a field your rule checks for stop and route to a person, who verifies the target and the contents before the file leaves your environment.