Store CMS form file uploads in dedicated cloud storage

When a visitor submits a file via a web form in Case Status, automatically upload the submitted attachment to a designated folder in Box.

Try:

See all Case Status + Box integrations or talk to a human

Trusted by teams already building on Knit·

4.9/5 on G2·

Google for Startups Accelerator

How 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.

Case Status Explore Case Status →

Triggers

Page published

Fires when a new page or post is published on Case Status.

Form submitted

Fires when a form on Case Status is submitted.

CMS item updated

Fires when a CMS item is updated on Case Status.

Actions

Publish page

Publishes or updates a page on Case Status.

Create CMS item

Creates a new CMS item on Case Status.

Update content

Updates existing content on Case Status.

Box Explore Box →

Triggers

New file uploaded

Fires when a new file is uploaded to Box.

File shared

Fires when a file in Box is shared with someone new.

Folder updated

Fires when a folder's contents change in Box.

Actions

Upload file

Uploads a file to Box.

Create folder

Creates a new folder in Box.

Share file

Shares a file from Box with a link or user.

Create draft CMS items when media assets are uploaded When a new asset or image is uploaded in Box, automatically create a new CMS item in Case Status so content creators can easily publish it. See details

Create dedicated storage folders for newly published site pages Whenever a page is published in Case Status, automatically create a corresponding media folder in Box to house all official page assets. See details

See all Case Status + Box integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Store CMS form file uploads in dedicated cloud storage” between Case Status and Box?

Yes — describe it in the box above and Knit's Integrations Agent researches Case Status 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.

What's the most common Files & Storage + Website & CMS automation?

Publishing a new file from Box directly into a page or media library in Case Status, so content and assets stay in sync without a manual upload step.

Does this handle file replacements, or only brand-new uploads?

The Agent can also update an existing page's asset in Case Status when the source file in Box is replaced, not just handle new uploads.