Product Announcements

Box AI in a Hub is moving from a window centered over your content to a side panel docked to the right of it - the same pattern Box AI already follows in Box Notes or Documents. With the panel open, the Hub will stay fully usable: you'll be able to scroll the page, move between pages, and open content items without interrupting the conversation or dismissing anything first. The panel will open with suggested prompts - Summarize this Hub, What are the key takeaways?, What is the goal of this Hub? Answers will appear beside the content they describe, so you can read a document and ask about it side by side.  Coming soon, you'll be able to:Select Box AI in the Hub header to open the panel, then ask a question about the Hub or the content in it, using the suggested prompts or your own. Or type your question into the Hub's search bar and choose Ask AI - the panel opens with that question already asked. Select Box AI again to close the panel, and once more to reopen it - your conversation is

Box Shuttle is introducing a new API, which allows you to connect to Box Shuttle via the standard Box API. This API contains all of the functionality of the existing legacy API, connecting directly to the native Box experience. For large, complex jobs that would be tedious to manage via the Admin Console user interface, the Box Shuttle API allows you to manage jobs at the scale you require for your onboarding project. The new API will allow you to connect with the new native Box Shuttle and perform all standard operations that have been possible via the legacy API. You can create jobs, register source systems, perform bulk mapping, start and manage Shuttle jobs, and so much more. Using the API, you can automate your Shuttle tasks to ensure maximum efficiency when onboarding your data into Box.

One workflow, multiple triggers. Automate will soon support multiple triggers per workflow, so processes that share the same steps but start from different events can live in one place, and every change you make applies to all of them. Why this mattersBusiness processes are rarely started by just one event. An contract lifecycle management process, for example, might need to begin when a form is updated, a file request is initiated, or when a file is uploaded to a specific folder. Because previously a workflow could only have one trigger, teams had to duplicate the same logic for each entry point. What you can doAdd up to 20 triggers per workflow, as long as they belong to the same item type: File workflows: any file event, plus metadata events on a file Folder workflows: any folder event, plus metadata events on a folder Repeat the same trigger type with different settings. For example, add several “File Uploaded” triggers to one workflow, each watching a different folder. See what