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 Kintone so content creators can easily publish it.
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.
Kintone Explore Kintone →
TriggersFires when a new page or post is published on Kintone.
Fires when a form on Kintone is submitted.
Fires when a CMS item is updated on Kintone.
Publishes or updates a page on Kintone.
Creates a new CMS item on Kintone.
Updates existing content on Kintone.
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 Kintone + Box workflows
See all Kintone + Box integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Create draft CMS items when media assets are uploaded” between Kintone and Box?
Yes — describe it in the box above and Knit's Integrations Agent researches Kintone 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 Kintone, 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 Kintone when the source file in Box is replaced, not just handle new uploads.