File & mailbox automation
Pick up, transform and deliver files from buckets, SFTP servers and mailboxes.
Scheduled jobs pull files from Amazon S3, Azure Blob Storage, SFTP and FTP servers and POP3 mailboxes, turn each one into an exchange, and move or delete it at the source only after it is safely stored.
How it works
Four things to know.
Never lose an item
Each item is deleted or moved at the source only after its exchange exists, so a failed run never loses a file.
Archive instead of delete
Point DeleteMovesFileTo at an archive prefix or folder, and processed files are moved there instead of deleted.
Binary-safe
Base64 encoding carries PDFs, images and other binary files through the pipeline intact.
Batch it up
Aggregations roll up to 10,000 finished exchanges per run into a single list of file URLs for downstream batch processing.
{ "recurrence": "Daily", "hours": 2, "minutes": 30 }
// Quartz: 0 30 2 * * ? (UTC)
// Receive now runs the job once without changing it.Outcomes
What your team gets.
- Files from four kinds of source on one schedule engine
- Receive attempts record what each run found
- Stuck or unscheduled jobs flagged automatically
- Upload handlers for S3, Azure Blob and SFTP
Good to know: The SFTP/FTP adapters and one POP3 receiver use the commercial Rebex library and appear once a Rebex license key is saved. The MailKit-based POP3 receiver needs no license.
Documentation
Read the details.
Industries
Where this pattern shows up.
Put every integration on one governed pipeline.
Talk to the architects who build Bitween about your partners, systems and message volumes, or start from the docs and run it yourself today.