# Connect Evisort to SharePoint > Sync contracts, metadata, and approvals between your document repository and AI-powered contract intelligence platform, without manual effort. **Canonical page:** https://tray.ai/connectors/evisort-sharepoint-integrations/ **Evisort connector:** https://tray.ai/connectors/evisort-integrations/ **Evisort documentation:** https://tray.ai/documentation/connectors/service/evisort **SharePoint connector:** https://tray.ai/connectors/sharepoint-integrations/ **SharePoint documentation:** https://tray.ai/documentation/connectors/service/sharepoint ## Overview Evisort and SharePoint are two of the most widely used platforms for managing contracts and enterprise documents, yet teams often struggle to keep them aligned. Legal, procurement, and operations teams store executed agreements in SharePoint while relying on Evisort's AI-driven analytics to extract obligations, track milestones, and flag renewals. Integrating these two platforms through tray.ai eliminates duplicate uploads, missed deadlines, and disconnected metadata so your contract data is always accurate and accessible. Organizations that rely on SharePoint as their central document repository often face a real gap: contracts sit in folders with little to no structured intelligence applied to them. Evisort fixes this by using AI to extract key terms, dates, parties, and obligations directly from contract documents. When connected via tray.ai, new contracts uploaded to SharePoint are automatically ingested into Evisort for analysis, while extracted metadata and risk flags flow back to enrich SharePoint document libraries with structured columns and tags. Legal teams get AI-powered insights without leaving SharePoint, and Evisort's contract repository stays current with the source of truth. The result is faster renewals management, reduced compliance risk, and a reliable view of contract data across the enterprise. ## Use cases ### Auto-Ingest New SharePoint Contracts into Evisort Whenever a new contract document is uploaded to a designated SharePoint library or folder, tray.ai automatically sends it to Evisort for AI analysis. Legal and procurement staff don't have to manually re-upload contracts into a separate system, saving hours of repetitive work each week. - Eliminate manual double-uploads of contracts into two separate systems - Ensure every contract is analyzed by Evisort's AI the moment it lands in SharePoint - Reduce the risk of contracts being missed or overlooked in Evisort's pipeline ### Write Evisort Metadata Back to SharePoint Document Libraries After Evisort extracts contract data — counterparty name, effective date, expiration date, contract value — tray.ai maps those fields back to SharePoint document library columns. Static SharePoint folders become searchable, filterable contract repositories with structured AI-extracted metadata. - Populate SharePoint columns automatically with AI-extracted contract metadata - Let legal and business teams search and filter contracts by key fields directly in SharePoint - Maintain a single source of truth for contract metadata without manual data entry ### Trigger Contract Renewal Alerts from Evisort to SharePoint and Teams When Evisort detects an upcoming contract renewal or expiration milestone, tray.ai updates the contract document's metadata in SharePoint and sends a notification to the responsible owner. Contract owners get alerted in the tools they already use, so nothing slips through. - Surface renewal deadlines from Evisort into SharePoint before they're missed - Ensure contract owners are alerted with enough lead time to act - Reduce costly auto-renewals and missed termination windows ### Sync Executed Contracts from E-Signature Workflows into Both Platforms After a contract is fully executed through a signature tool, tray.ai routes the final signed document to both a designated SharePoint library and Evisort at the same time. The executed version is stored in the enterprise document repository and immediately queued for AI extraction, with no manual handoff required. - Automatically archive executed contracts in SharePoint the moment signing is complete - Trigger Evisort ingestion of signed agreements without human intervention - Maintain consistent folder structures and naming conventions across both systems ### Sync Contract Status and Lifecycle Stage Between Systems As contracts move through stages in Evisort — draft, review, execution, active management — tray.ai updates corresponding metadata fields in SharePoint to reflect the current status. Business stakeholders who primarily work in SharePoint always know where each agreement stands without needing Evisort access. - Keep SharePoint contract records updated with live lifecycle stages from Evisort - Give non-legal stakeholders contract status visibility without Evisort access - Support audit trails by maintaining consistent status metadata across both platforms ### Organize SharePoint Folders Automatically Based on Evisort Contract Classification Evisort classifies contracts by type — NDAs, MSAs, SOWs, vendor agreements — and tray.ai uses those classifications to automatically move or tag documents within the appropriate SharePoint folder structure. Document libraries stay organized without anyone manually sorting contract archives. - Automatically sort contracts into correct SharePoint folders based on Evisort AI classification - Standardize folder taxonomy across the enterprise without manual document sorting - Make it easier for teams to locate specific contract types quickly in SharePoint ### Archive and Retire Expired Contracts Across Both Platforms When Evisort identifies that a contract has expired or been terminated, tray.ai triggers an archival workflow that moves the document to a designated archive folder in SharePoint and updates its status metadata. Active contract libraries stay clean, and expired agreements remain accessible for reference and compliance audits. - Automatically move expired contracts to archive folders in SharePoint based on Evisort signals - Keep active SharePoint contract libraries free of outdated or terminated agreements - Maintain a compliant archive of historical contracts for audit and reference purposes ## Templates ### New SharePoint Contract Document → Evisort Ingestion Monitors a specified SharePoint document library for newly uploaded contract files and automatically submits them to Evisort for AI-powered extraction and analysis, so every contract is processed without manual intervention. Connectors used: SharePoint, Evisort ### Evisort Contract Metadata → SharePoint Column Update After Evisort completes AI extraction on a contract, this template reads the extracted fields and writes them back as structured metadata columns in the corresponding SharePoint document, eliminating manual data entry and enriching the SharePoint library. Connectors used: Evisort, SharePoint ### Evisort Renewal Alert → SharePoint Metadata Flag + Notification When Evisort identifies a contract approaching its renewal or expiration date, this template flags the document in SharePoint with an upcoming renewal status and sends an alert to the designated contract owner, so nothing gets missed at the last minute. Connectors used: Evisort, SharePoint ### Executed Contract → Simultaneous SharePoint Archive + Evisort Ingestion Triggered when a contract reaches fully executed status in an upstream signing or CLM workflow, this template saves the final document to the correct SharePoint folder and submits it to Evisort at the same time. Both platforms are updated in one automated motion, no manual steps needed. Connectors used: SharePoint, Evisort ### Evisort Contract Classification → SharePoint Folder Routing Uses AI contract type classifications from Evisort to automatically move or copy documents into the correct SharePoint folder — NDAs, SOWs, Vendor Agreements — maintaining a clean, consistently organized document library without manual sorting. Connectors used: Evisort, SharePoint ### Expired Contract → SharePoint Archival Workflow When Evisort marks a contract as expired or terminated, this template automatically moves the document in SharePoint from the active contracts library to a designated archive folder and updates the document's status metadata to reflect its archived state. Connectors used: Evisort, SharePoint ## Challenges Tray.ai solves ### Maintaining Document Consistency Across Two Repositories When contracts exist in both SharePoint and Evisort, teams risk mismatched versions, missing documents, or conflicting metadata — especially if uploads happen manually or asynchronously across teams. **How Tray.ai helps:** tray.ai acts as an orchestration layer that enforces a single, automated flow for every new or updated contract. By triggering workflows from SharePoint events or Evisort webhooks, tray.ai keeps both platforms updated in lockstep, eliminating version drift and orphaned records. ### Mapping Evisort AI Fields to SharePoint Column Schemas Evisort extracts dozens of contract data points using its own field naming conventions, while SharePoint document libraries have custom column schemas that vary by organization. Manually mapping and translating these fields is error-prone and time-consuming. **How Tray.ai helps:** tray.ai's visual data mapper and transformation tools let teams define precise field mappings between Evisort's extracted contract data and SharePoint's column schema once, then apply that logic automatically across every contract processed. ### Handling Large Contract Document Files and Attachment Types Contracts can be large PDF or Word documents with complex formatting, and reliably transferring binary files between SharePoint and Evisort via API — especially at scale — requires careful handling of file streams, size limits, and authentication tokens. **How Tray.ai helps:** tray.ai manages file retrieval, streaming, and submission natively within workflows, handling authentication for both SharePoint (via Microsoft OAuth) and Evisort's API. Built-in error handling and retry logic ensure large or complex documents are transferred reliably without workflow failures. ### Triggering Real-Time Workflows from SharePoint Document Events SharePoint doesn't natively emit real-time webhooks for all document events in a way that's easy to consume in automation workflows, making it hard to trigger Evisort ingestion at the exact moment a contract is uploaded. **How Tray.ai helps:** tray.ai provides native SharePoint polling and webhook capabilities that reliably detect new and updated documents in designated libraries, even in complex SharePoint environments, and immediately trigger downstream Evisort ingestion workflows without custom code or middleware. ### Governing Access and Permissions Across Both Platforms Legal and compliance teams often have strict requirements around who can read or modify contract documents, and integration workflows that move data between SharePoint and Evisort must respect the permission models of both platforms to avoid unauthorized data exposure. **How Tray.ai helps:** tray.ai connects to SharePoint and Evisort using dedicated service account credentials with scoped permissions, so integration workflows only access the specific libraries and contract records they're authorized to touch. All credential management is handled securely within tray.ai's encrypted credential store. ## 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/