Replicate directory updates across file hubs
When a folder is updated in Box, automatically create a folder in Brick FTP so document structures stay organized identically across both systems.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Brick FTP Explore Brick FTP →
TriggersFires when a new file is uploaded to Brick FTP.
Fires when a file in Brick FTP is shared with someone new.
Fires when a folder's contents change in Brick FTP.
Uploads a file to Brick FTP.
Creates a new folder in Brick FTP.
Shares a file from Brick FTP with a link or user.
Box Explore Box →
TriggersFires when a new file is uploaded to Box.
Fires when a file in Box is shared with someone new.
Fires when a folder's contents change in Box.
Uploads a file to Box.
Creates a new folder in Box.
Shares a file from Box with a link or user.
More Brick FTP + Box workflows
See all Brick FTP + Box integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Replicate directory updates across file hubs” between Brick FTP and Box?
Yes — describe it in the box above and Knit's Integrations Agent researches Brick FTP and Box's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Why sync two file storage applications together?
Connecting Brick FTP and Box ensures automated cross-platform backups and keeps folder organizational structures synced across all your cloud storage tools.
Will new files and folder updates replicate across both systems?
Yes, whenever a folder is updated or a new file is uploaded in Brick FTP, matching files and folders can automatically be created or uploaded in Box.