Source and destination
Each side of a job specifies a connector, a credential, and a path. Get these right — and grant the right access — and the rest of the job is straightforward.
Last updated July 17, 2026
#What each side specifies
- Connector type — Local, SMB, FTP, SFTP, Amazon S3, or Azure Blob.
- Credential — a stored credential for that endpoint (local paths don't need one).
- Path — the folder, share path, or bucket/container prefix to read from or write to.
#Permissions each side needs
Confirm the account behind each credential has:
- Read/list on the source.
- Write on the destination.
- Delete on the relevant side for Move and Sync/Mirror.
Point each side at the most specific folder or prefix you can. Narrow scopes run faster and make logs easier to read.
#Mixing systems
Any supported system can be a source or a destination, so you can combine them freely — SMB → S3, SFTP → local, local → Azure Blob, and so on. Files flow through the FileAgent host, so place the host where bandwidth to both sides is good.
#Renaming on the way out
A job can write files to the destination under a different name using a destination filename pattern — handy when a downstream system expects a specific naming convention. See File patterns & filters.