Thanks to
Agenda
Full recording here, highlights below:-
Main Topics
1. The Strategic Importance of Integration: Pegi Karger opened by explaining the core challenge the integration solves: ServiceNow manages critical business processes (like incidents, cases, and requests), but the supporting content often resides in Box. This historically led to manual, cumbersome workflows. The Box for ServiceNow integration addresses this by embedding a Box content panel directly within ServiceNow records. This allows teams to access, upload, and manage files in context, without creating duplicate copies, while ensuring all of Box's permissions, governance, classifications, and retention policies are automatically applied.
2. The Box & ServiceNow Ecosystem: Pegi provided an overview of the various ways the two platforms connect:
- Box-Owned Integrations: The new "Box for ServiceNow" integration (embedding Box UI), the "Box Agent for ServiceNow" (bringing Box AI into Now Assist), and the Box MCP server.
- ServiceNow-Owned Integrations: The Box Spoke for workflow automation in Flow Designer and the Box AI with Knowledge Center integration.
- Partner & Custom Solutions: Integrations built by partners like Reva and the ability to build custom experiences using Box APIs.
3. Deep Dive on the New "Box for ServiceNow" Integration:

4. Use Cases & Demo: The integration supports a wide range of horizontal use cases, including IT incident management (capturing logs and screenshots), customer service (managing contracts and forms), and legal/procurement.
5. Box Agent for ServiceNow (AI Capabilities): The session also revisited the Box Agent, which integrates Box AI with ServiceNow's Now Assist. This allows users to interact with their Box content via a conversational chat interface to perform tasks like content extraction, summarization, and conversational Q&A, all while respecting Box's document classification labels for security.

Q&A Session
The Q&A session addressed several key points:
- Comparison to Salesforce Integration: A user noted similarities to the Box for Salesforce integration. The team confirmed this was intentional and that future releases would include more UI configurability and support for custom folder mapping outside the default root structure.
- Feedback on Box Spoke: A user provided detailed feedback on the limitations of the current Box Spoke, noting they had to build 15 custom functions to achieve desired outcomes like moving files, updating metadata, and creating Box Sign requests. The Box team welcomed the feedback and offered to connect directly to help improve the official Spoke.
- Long-Term Vision:
@kadams Box articulated the long-term vision, positioning ServiceNow as the next-generation process platform that orchestrates content, and Box as the next-generation content platform that provides a single, secure content layer across all enterprise applications.
