Your comment on the Azure webjobs sdk extensions issue, was inspiring.

So having watched and read: the (Channel9 vid)[https://channel9.msdn.com/Shows/On-NET/Creating-custom-bindings-for-Azure-Functions?term=custom%20bindings&lang-en=true] with Cecil Phillip and (Matías Quaranta)[https://github.com/ealsur]

I have forked the (example repo)[https://github.com/ealsur/functions-extension-101] and your project and joining them together. If that's OK? My (repo is called 'SFTPSSHCustomBinding')[https://github.com/OzBob/SFTPSSHCustomBinding].

The comment in the AzFn ext issue#2 from @mathewc , could be further work here or in the forked repo:

• Configuration
• Default one FtpConfiguration, connecting using connnection string from config
• FtpTriggerValue: bind it to string, stream and maybe FileInfo?
• Path/Filemask moved to each function.
• ArxOneFtp migrate to SSH.Net library
• Dashboard integration
• FtpListener
• multi-instance with StatusFile
• Most of the time "get and delete" is the preferred scenario. Another solution we often use is moving to a processed folder.
• *Polling interval customizable, check. If I get time Ill add the same kind of cron timer as you have for scheduling jobs.
• *Will make it async.