Use cases SFTP File Processing
SFTP File Processing use case
Scheduled SFTP download → transform/validate → upload results — reliable file pipelines without cron spaghetti.
This page is an industry overview (templates + protocols). For step-by-step configuration, use the blog/wiki links below — those URLs are the primary how-to pages.
The problem
Partners still drop CSV/XML on SFTP. Nodlyn owns the poll, parse, and push with retries and alerts.
Who it’s for: Integration engineers and ops teams exchanging batch files with vendors.
How Nodlyn approaches SFTP File Processing
SFTP still dominates B2B batch exchange. Nodlyn’s SFTP template owns schedule, vaulted credentials, download/upload, and failure notify so you retire fragile cron scripts.
Combine with CSV transforms or document OCR when partners send mixed payloads. Run the agent on a host that can reach the remote SFTP endpoint.
Example workflows
- Nightly SFTP pull → validate CSV → upload processed file → Slack done
- Failed transfer → retry policy → ticket
- Pair with document OCR when partners send PDF batches
Quick start
- Open the SFTP File Transfer Pipeline template.
- Set host, credentials (vault), remote paths, and schedule.
- Add Transform/Condition for validation; notify on failure.
- Run as a runtime agent on a server that can reach the SFTP host.
Starter templates in Studio
Open Templates in desktop Studio and search these names — they are real built-in graphs, not placeholder titles.
- SFTP File Transfer Pipeline
Related protocols
Guides (blog & wiki)
Why use Nodlyn instead of cron + scripts?
The SFTP template owns schedule, vaulted credentials, retries, and failure notify in a visual graph you can monitor — still running on your agent host.
Related use cases
Try this use case
Download the free desktop beta, sign in with your free account, and open the templates above.
Download Free Beta All use cases