Upload new transcripts and summaries in Comu to Box as files.
Automatically save new transcripts and summaries from Comu as files 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.
Comu Explore Comu →
TriggersFires when a new chat or conversation begins in Comu.
Fires when Comu captures a lead during a conversation.
Fires when Comu escalates a conversation to a human.
Sends a message to a user through Comu.
Asks Comu a question against its knowledge base and returns the answer.
Uses Comu to summarize a chat transcript.
Opens a support ticket from an Comu conversation.
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 Comu + Box workflows
See all Comu + Box integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Upload new transcripts and summaries in Comu to Box as files.” between Comu and Box?
Yes — describe it in the box above and Knit's Integrations Agent researches Comu 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 Comu automatically organize files shared during customer chats into Box?
Yes, whenever leads or customers share files or start chats, you can automatically create dedicated folders or upload assets directly into Box.
How can automated summaries from Comu be stored in Box?
Chat transcript summaries generated by Comu can be saved as new files inside specific folders in Box for team records.