When all live events in api.video, sync it to Box.
When live stream events end in api.video, automatically store a high-resolution copy of the stream file in Box.
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.
api.video Explore api.video →
TriggersFires when a new video is recorded or shared in api.video.
Fires when someone comments on a video in api.video.
Fires when a new video recording or comment is added in api.video.
Sends a video message via api.video.
Shares a video link from api.video.
Posts a video from api.video to a channel.
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 api.video + Box workflows
See all api.video + Box integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “When all live events in api.video, sync it to Box.” between api.video and Box?
Yes — describe it in the box above and Knit's Integrations Agent researches api.video 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.
Can new team videos recorded in api.video save to Box?
Yes, whenever a new video is shared in api.video, it can automatically upload to your specified backup folder in Box.
How can file additions in Box send notifications to video channels?
When new files or shared assets are uploaded in Box, notification messages can automatically post to your team channels in api.video.