# SharePoint + ServiceNow integration > Stop manually copying files and chasing approvals between your document management and IT service management platforms. tray.ai handles it automatically. **Canonical page:** https://tray.ai/connectors/sharepoint-servicenow-integrations/ **SharePoint connector:** https://tray.ai/connectors/sharepoint-integrations/ **SharePoint documentation:** https://tray.ai/documentation/connectors/service/sharepoint **ServiceNow connector:** https://tray.ai/connectors/servicenow-integrations/ **ServiceNow documentation:** https://tray.ai/documentation/connectors/service/servicenow ## Overview SharePoint and ServiceNow run a lot of enterprise operations — one managing documents, knowledge, and collaboration, the other handling IT service delivery and business workflows. Yet teams routinely waste hours copying files, updating records, and chasing approvals across both platforms by hand. Integrating SharePoint with ServiceNow through tray.ai closes that gap so service tickets, knowledge articles, change records, and supporting documents stay synchronized without anyone manually moving them. When SharePoint and ServiceNow operate in silos, context gets lost between systems. An IT technician resolving a ServiceNow incident may never find the runbook sitting in SharePoint, while a compliance team managing SharePoint documents has no visibility into the ServiceNow change requests tied to those files. Connecting the two platforms with tray.ai means document creation, ticket updates, approvals, and knowledge management all flow automatically between systems. Resolution times drop, governance policies get enforced, duplicate data entry disappears, and every stakeholder gets a complete, real-time picture — whether they work primarily in SharePoint or ServiceNow. ## Use cases ### Auto-Attach SharePoint Documents to ServiceNow Incidents When a new incident is created in ServiceNow, tray.ai can automatically pull relevant runbooks, SOPs, or knowledge documents from SharePoint and attach them as links or files directly to the ticket. Technicians get the context they need without leaving ServiceNow or digging through SharePoint libraries. Faster document access means faster mean-time-to-resolution across your service desk. - Reduces time technicians spend searching for supporting documentation - Always references the latest version of runbooks and SOPs - Speeds up incident resolution by surfacing relevant knowledge automatically ### Create SharePoint Document Libraries for ServiceNow Change Requests Every approved change request in ServiceNow can automatically trigger the creation of a dedicated SharePoint document library or folder, pre-populated with templates for change plans, test results, and rollback procedures. Teams have a structured documentation workspace ready the moment a change is approved, organized and auditable from day one. - Standardizes change documentation structure across every project - Eliminates manual folder creation and template distribution - Strengthens audit trails for regulatory compliance reviews ### Sync ServiceNow Knowledge Articles with SharePoint Pages Keep your enterprise knowledge base consistent by automatically publishing or updating ServiceNow knowledge articles as SharePoint pages — and vice versa — whenever content is approved or revised. Non-technical stakeholders who prefer SharePoint get the same accurate information as IT staff working in ServiceNow, with versioning metadata preserved across both platforms. - Maintains a single source of truth for organizational knowledge - Reaches broader audiences without duplicating authoring effort - Keeps knowledge articles current with the latest approved content ### Trigger ServiceNow Requests from SharePoint List Changes When a row is added or updated in a SharePoint list — a new hardware request, onboarding entry, or vendor record — tray.ai can automatically open a corresponding ServiceNow request or catalog item. SharePoint lists become lightweight intake forms that feed directly into structured ITSM workflows. Business users get a familiar interface while IT teams receive properly routed, fully detailed service requests. - Lets business users kick off IT workflows without ServiceNow access - Reduces miscategorized or incomplete service requests - Bridges departmental intake processes with formal ITSM governance ### Automate Approval Workflows Across Both Platforms Route ServiceNow approval tasks to SharePoint document approvers, or trigger ServiceNow approval chains when a SharePoint document reaches a specific status. tray.ai handles multi-step approval logic that spans both platforms, notifying the right people at the right time via their preferred system. Approvals are logged in both environments for complete traceability. - Removes approval bottlenecks caused by siloed notification systems - Creates end-to-end audit logs across SharePoint and ServiceNow - Cuts approval cycle times with automated escalations and reminders ### Sync User Offboarding Actions Between ServiceNow and SharePoint When an employee offboarding task is completed or a user account is deactivated via a ServiceNow HR service request, tray.ai automatically updates SharePoint permissions, transfers document ownership, and archives the departing user's content. Security and compliance teams can be confident that access is revoked and documents are retained according to policy — no manual intervention required. - Prevents orphaned documents and lingering SharePoint access after offboarding - Enforces data retention and document ownership policies automatically - Reduces risk of unauthorized access to sensitive SharePoint content ### Generate SharePoint Reports from ServiceNow ITSM Data Automatically push ServiceNow metrics — ticket volumes, SLA compliance rates, open incident summaries — into SharePoint lists or Excel files on a schedule. Business stakeholders who live in SharePoint get current ITSM data without needing ServiceNow licenses or logins. No manual exports, no formatting work. - Opens up ITSM reporting to non-ServiceNow users across the business - Eliminates manual data exports and copy-paste reporting - Keeps leadership current with operational data in familiar SharePoint dashboards ## Templates ### New ServiceNow Incident → Attach SharePoint Runbook Automatically searches a specified SharePoint document library for matching runbooks or SOPs when a ServiceNow incident is created, then attaches the relevant document links to the incident record and notifies the assigned technician. Connectors used: SharePoint, ServiceNow ### Approved ServiceNow Change Request → Create SharePoint Folder When a change request moves to Approved status in ServiceNow, this template automatically creates a structured SharePoint folder with pre-defined document templates and notifies the change owner with the folder link. Connectors used: SharePoint, ServiceNow ### SharePoint List Item Created → Open ServiceNow Service Request Monitors a SharePoint list for new entries and automatically creates a fully populated ServiceNow catalog request or incident, mapping SharePoint column values to the appropriate ServiceNow fields. Connectors used: SharePoint, ServiceNow ### ServiceNow Knowledge Article Published → Create SharePoint Page Each time a knowledge article is published or updated in ServiceNow, this template creates or updates the corresponding SharePoint page in a specified site, keeping both knowledge bases consistent for all audiences. Connectors used: SharePoint, ServiceNow ### ServiceNow Offboarding Task Completed → Revoke SharePoint Access Automatically removes a departing employee's SharePoint site memberships, transfers document ownership to their manager, and archives their personal SharePoint content when a ServiceNow offboarding task is marked complete. Connectors used: SharePoint, ServiceNow ### Scheduled ServiceNow Metrics Export → SharePoint Report Update On a defined schedule, this template pulls ITSM metrics from ServiceNow — including open incidents, SLA compliance, and resolved ticket counts — and writes the data into a SharePoint list or Excel workbook for stakeholder reporting. Connectors used: SharePoint, ServiceNow ## Challenges Tray.ai solves ### Complex Permission and Authentication Models SharePoint uses Microsoft 365 OAuth and granular site-level permissions, while ServiceNow relies on its own role-based access control and API credentials. Keeping authentication configurations secure and compliant across both platforms is a real technical hurdle for integration teams. **How Tray.ai helps:** tray.ai manages OAuth connections to Microsoft 365 and supports ServiceNow REST API authentication natively, storing credentials securely and refreshing tokens automatically. Admins configure connection credentials once and reuse them across all workflows without exposing secrets in workflow logic. ### Large File Transfers and SharePoint Throttling SharePoint enforces API throttling and file size limits that can break integrations when syncing large documents or processing high-volume events in bulk. ServiceNow has its own API rate limits that need to be respected to avoid degraded performance or blocked requests. **How Tray.ai helps:** tray.ai has built-in retry logic, exponential backoff, and rate-limit handling for both SharePoint and ServiceNow connectors. Large file transfers are chunked automatically, and workflow steps are queued to stay within platform API limits without losing data. ### Data Field Mapping Mismatches Between Platforms ServiceNow and SharePoint use fundamentally different data models. ServiceNow organizes data around tables, records, and CIs; SharePoint structures data as lists, libraries, and columns. Mapping fields accurately between the two requires careful transformation logic that can break when either platform updates. **How Tray.ai helps:** tray.ai's visual workflow builder includes a flexible data transformation layer where teams can map, reshape, and normalize fields between SharePoint and ServiceNow without writing custom code. When either platform changes its schema, the transformations are straightforward to update. ### Keeping Document Versions and Ticket States Consistent When SharePoint documents are revised and ServiceNow tickets change state at the same time, integration workflows can create race conditions, duplicate records, or overwrite current data with stale information. The compliance and accuracy consequences are real. **How Tray.ai helps:** tray.ai supports conditional logic and idempotency checks within workflows, so integrations can verify the current state of a record before writing updates. Version metadata from SharePoint and state fields from ServiceNow are compared before any action is taken, which prevents conflicting writes. ### Maintaining Audit Trails Across Both Systems Regulated industries need end-to-end audit trails showing exactly when documents were created, who approved them, and how they relate to change or incident records. Tracking this manually across SharePoint and ServiceNow is error-prone and usually incomplete. **How Tray.ai helps:** tray.ai logs every workflow execution with input and output data, timestamps, and step-level detail — giving you a complete audit record of all cross-platform actions. Teams can also configure workflows to write audit metadata back into SharePoint item fields and ServiceNow record notes, creating native audit trails in each system. ## Learn more - Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/ - Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/ - Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/ - Book a demo: https://tray.ai/contact/