We recently had a customer who wanted to obtain files coming from a custom web application into their Box account. The custom web application supported file transfer via SFTP. Box only supports FTPS. No dice. The vendor that created the application offered to implement FTPS capability if our customer paid for it. Aside from our position that a FTPS integration with Box was not the best choice, we found that our customer could save a significant amount of money and development time by purchasing BrickFTP and connecting it to Box via Zapier. The cost savings made it an easy decision.
BrickFTP supports SFTP. It also had the Zap triggers and actions needed to get the files to Box once they were uploaded. Great! However, we wanted to minimize the management requirement from our customer. We wanted to delete the file from BrickFTP once we confirmed it uploaded to Box, so our customer wouldn’t have to keep checking BrickFTP to make sure it had enough storage. The problem is that there is no Zap available to delete a BrickFTP file. That’s where the Zapier Webhook Zap comes in.
The configuration to delete a specific BrickFTP file
By reading the BrickFTP REST API documentation, we learned what we needed: How to delete and how to authenticate. The Zapier Webhook could handle that easily. We generate the appropriate API Key and included it within the Zap under the Basic Authentication setting. Done.