FTP / SFTP

Recursive file ingestion from any FTP-compatible server. Useful for legacy systems that don't expose a modern API but still serve as a system-of-record.

variant=info text="Cloud storage" variant=secondary text="User + password"

What gets ingested

Element	Mapped to
Files	_FileEntry + _Blob
Directories	_Folder linked via _HasChild
File metadata (size, timestamp)	Properties on _FileEntry

Authentication

• Type: Username + password, or anonymous.
• Credentials are stored encrypted; the connector opens one connection per run.

Access control mapping

Source	Carried into the graph?
Filesystem permissions on the FTP server	No — not enumerated.
Anonymous FTP	Files map to _AccessGroup.Public.
Authenticated FTP	Files inherit the PermissionsSetting configured in the integration form.

Sync cadence

• Default cron: 0 23 * * * (daily at 23:00 UTC).
• Incremental sync: size/timestamp comparison — unchanged files are skipped.

Notable

• Works with ftp://, ftps://, and (depending on workspace build) sftp://.
• Configurable starting directory, so you can ingest only a subtree.