# Connect DocuSign to SharePoint > Connect DocuSign eSignatures to SharePoint document libraries so signed contracts are organized, searchable, and accessible the moment they're complete. **Canonical page:** https://tray.ai/connectors/docusign-sharepoint-integrations/ **DocuSign connector:** https://tray.ai/connectors/docusign-integrations/ **DocuSign documentation:** https://tray.ai/documentation/connectors/service/docusign **SharePoint connector:** https://tray.ai/connectors/sharepoint-integrations/ **SharePoint documentation:** https://tray.ai/documentation/connectors/service/sharepoint ## Overview DocuSign and SharePoint handle two different parts of the same problem. DocuSign collects legally binding signatures; SharePoint is where enterprise content lives. Together, they cover the full document lifecycle: send for signature in DocuSign, automatically store and organize completed documents in SharePoint. Without an integration, teams are stuck manually downloading signed PDFs and uploading them to the right folders — a repetitive process that invites delays and errors. Connecting DocuSign with SharePoint cuts out the manual handoff that follows every completed envelope. When a contract, NDA, or approval form is signed in DocuSign, tray.ai can instantly route the finalized document into the correct SharePoint library, folder, or site — with metadata tagging, version control, and permission settings already applied. Compliance teams get an audit-ready archive. Legal teams find signed agreements without digging through email threads. Operations teams can trigger downstream workflows the moment a signature lands. Faster deal closing, tighter compliance, and one place to find all your signed documents. ## Use cases ### Auto-Archive Completed Envelopes to SharePoint When a DocuSign envelope reaches completed status, tray.ai automatically retrieves the signed PDF and certificate of completion, then uploads both to a designated SharePoint document library. Folder paths are built dynamically from envelope metadata such as recipient name, department, or contract type. - Eliminates manual downloading and uploading of signed documents - Every completed envelope lands in the correct SharePoint location, consistently - The DocuSign certificate of completion stays alongside the signed document for audit purposes ### New SharePoint Document Triggers a DocuSign Signing Request When a new contract template or agreement is added to a designated SharePoint library, tray.ai can automatically create and send a DocuSign envelope to the appropriate signatories. This works especially well for HR onboarding workflows where offer letters are drafted in SharePoint and need a signature fast. - Cuts time-to-signature by automating envelope creation from SharePoint-stored documents - Newly uploaded contracts don't sit unsigned and forgotten - Signing workflows stay consistent across departments without manual intervention ### Contract Renewal Reminders Based on SharePoint Metadata tray.ai monitors SharePoint document libraries for contracts approaching their expiration dates using custom metadata columns. When a renewal threshold is reached, it automatically triggers a new DocuSign envelope with the updated contract and sends it to the relevant parties for re-signing. - Contracts don't lapse because someone missed a renewal deadline - Renewal envelopes are generated and sent without manual tracking - SharePoint metadata is updated with new expiration dates once re-signing is complete ### Update SharePoint Document Metadata After Signing Once a DocuSign envelope is completed, tray.ai writes signing data — signer name, signature date, envelope ID — back to the corresponding SharePoint document's metadata fields. The SharePoint record gets richer without anyone touching it manually. - Signed documents in SharePoint become filterable and reportable - A traceable link exists between the SharePoint file and its DocuSign envelope - Compliance reporting gets easier when signature timestamps are visible in SharePoint views ### Declined or Voided Envelope Notifications and SharePoint Logging When a DocuSign envelope is declined or voided, tray.ai logs the event to a SharePoint list or document library and notifies relevant stakeholders via email or Teams. Every envelope outcome has a record in SharePoint, not just the successful ones. - A complete record of declined and voided agreements stays in SharePoint - The right team members get alerted to failed signings immediately - No envelope outcome goes unrecorded, which matters when audits happen ### HR Onboarding Document Automation When a new employee record is created in an HR system, tray.ai pulls the relevant onboarding document templates from SharePoint, generates a DocuSign envelope, and sends it to the new hire for signature. Once complete, the signed documents are automatically filed into the employee's SharePoint folder. - New hires get a smooth, professional onboarding experience - All required employment documents are signed and stored before day one - HR teams are out of the loop on sending, chasing, and filing documents manually ### Vendor and Supplier Agreement Management Procurement teams can store vendor agreement templates in SharePoint and use tray.ai to trigger DocuSign envelopes whenever a new vendor is approved. Signed agreements go back to the vendor's SharePoint folder automatically, with status metadata updated, so procurement always knows where things stand. - Vendor onboarding moves faster when the contract signature process runs itself - All vendor agreements are in SharePoint with a consistent folder structure - Procurement teams can see unsigned or expiring vendor contracts without digging ## Templates ### Save Completed DocuSign Envelopes to SharePoint Automatically retrieves the signed PDF and completion certificate from DocuSign whenever an envelope is marked complete, then uploads both files to a specified SharePoint document library with dynamic folder routing based on envelope metadata. Connectors used: DocuSign, SharePoint ### Send DocuSign Envelope When Document Added to SharePoint Monitors a designated SharePoint document library for newly uploaded files and automatically creates and sends a DocuSign envelope to a predefined list of signatories, routing from document creation to signature request without any manual steps. Connectors used: DocuSign, SharePoint ### Log All DocuSign Envelope Events to a SharePoint List Creates a real-time audit log in a SharePoint list that captures every DocuSign envelope event — sent, viewed, signed, declined, or voided — giving you a centralized, searchable record of all document signature activity. Connectors used: DocuSign, SharePoint ### Contract Renewal Automation from SharePoint to DocuSign Scans SharePoint document libraries on a scheduled basis for contracts with expiration dates approaching a configurable threshold, then automatically generates and sends renewal envelopes in DocuSign to the relevant signatories. Connectors used: DocuSign, SharePoint ### HR Onboarding: Send and File Employee Documents via DocuSign and SharePoint Runs the full onboarding document workflow — fetching HR document templates from SharePoint, sending them as a DocuSign envelope to new hires, and filing the completed signed copies back into the employee's dedicated SharePoint folder. Connectors used: DocuSign, SharePoint ### Write DocuSign Signing Data Back to SharePoint Metadata After a DocuSign envelope is completed, writes signing metadata — signer name, signed date, and DocuSign envelope ID — directly to the corresponding SharePoint document's item fields, so the record reflects what actually happened. Connectors used: DocuSign, SharePoint ## Challenges Tray.ai solves ### Matching DocuSign Envelopes to the Correct SharePoint Location Enterprise SharePoint environments often have complex site hierarchies, libraries, and folder structures. Automatically routing a completed DocuSign envelope to exactly the right location — without hardcoding paths — requires intelligent mapping of envelope metadata to SharePoint's folder taxonomy. **How Tray.ai helps:** tray.ai's data mapping and transformation tools let you build dynamic folder path logic using DocuSign envelope metadata such as contract type, department, or recipient company. Conditional branching routes documents to the correct SharePoint site, library, and subfolder every time, even as your folder structure changes. ### Handling Large or Multi-Document DocuSign Envelopes DocuSign envelopes can contain multiple documents, and SharePoint storage workflows need to handle each file individually — retrieving, naming, and uploading them correctly while keeping the relationship between files from the same envelope intact. **How Tray.ai helps:** tray.ai supports looping and iteration natively, so workflows can process each document within a multi-file DocuSign envelope in sequence. Each file is retrieved, given a consistent name, and uploaded to SharePoint independently, with envelope-level metadata applied consistently across all related files. ### Maintaining SharePoint Permissions on Sensitive Signed Documents Signed contracts and legal agreements are often sensitive, and automated uploads can deposit documents into SharePoint folders with overly broad access permissions — a real compliance and confidentiality risk. **How Tray.ai helps:** tray.ai workflows can include a dedicated permission-setting step after upload, using the SharePoint API to apply specific access controls or inherit permissions from a secure parent folder. Permission logic is configurable based on document type, department, or sensitivity level defined in the DocuSign envelope metadata. ### Keeping DocuSign and SharePoint Status in Sync Across Long Signing Cycles Enterprise contracts can take days or weeks to get through multiple rounds of signers. During that time, the status in SharePoint can easily fall out of sync with the actual state of the DocuSign envelope, causing confusion and redundant follow-up. **How Tray.ai helps:** tray.ai listens to every DocuSign Connect event throughout the envelope lifecycle — sent, delivered, viewed, signed by each party, and finally completed — and updates the corresponding SharePoint list item or document metadata at each stage. Stakeholders get an accurate status view without any manual updates. ### Avoiding Duplicate Document Uploads to SharePoint In environments where multiple teams or systems interact with DocuSign, the same completed envelope can trigger duplicate upload attempts, resulting in redundant files and version confusion in SharePoint document libraries. **How Tray.ai helps:** tray.ai workflows can include an idempotency check that queries SharePoint for a file matching the DocuSign envelope ID before attempting an upload. If a matching document already exists, the workflow skips the upload and optionally logs the attempt, keeping SharePoint libraries clean. ## 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/