Which DocuSign plan do I need?

An API plan. DocuSign sells the eSignature REST API and Connect through its Developer plans (Starter, Intermediate, Advanced, Enhanced) and describes the Personal, Standard and Business Pro seats as built for the web app and its own integrations, so check what your account includes before buying. The developer sandbox is free and is where the walkthrough was recorded.

How does it know which client folder to use?

From an envelope custom field called Client, which your senders fill when they send from a template. If the field is blank, the first signer's name is used instead. Both the field name and the fallback are set in one node.

What happens if SharePoint rejects the upload?

Teams still gets the message, with the error text and a link to the envelope in DocuSign, and the execution stays in n8n's list so you can re-run it once the folder or permission is fixed. The signed document is never lost; DocuSign keeps it.

Can it file to Google Drive and post to Slack instead?

Yes. Swap the SharePoint node for Google Drive and the Teams node for Slack; the rest is unchanged, and the setup guide shows both swaps. The export we test is the Microsoft version.

Does it run on Make or Zapier?

Make, yes: the DocuSign, OneDrive and Microsoft Teams modules cover every step except the certificate download, which uses the DocuSign app's generic API-call module, and the blueprint is in the package. Zapier is not included, because we have not tested a full Zap with the document download, and we only ship what we have run end to end.

DSSPTMade to order

Documents & e-signature

DocuSign envelope completed → signed PDF filed in SharePoint + Teams post

Signed contracts land in the right SharePoint folder before anyone downloads them.

A completed DocuSign envelope is a PDF in someone's inbox until they remember to file it. This package listens for DocuSign's envelope-completed event, downloads the signed document and its certificate of completion, and saves both into the client's SharePoint folder under one naming pattern. A Teams post with the link follows. Built for Microsoft 365 offices that send contracts, NDAs and engagement letters through DocuSign.

How it works

DS
Trigger
Envelope status changes to Completed, delivered by a DocuSign Connect webhook to n8n's Webhook node
DocuSign
if
Step 1
Verify the webhook and read the envelope
An HMAC check on the Connect payload comes first. Envelope ID, subject, completed date, signer names and the Client and Document type custom fields then come off the JSON; anything that is not a completed envelope stops here.
DS
Step 2
Download the signed PDF and the certificate
Two calls to the eSignature REST API fetch the combined signed document and the certificate of completion as PDFs. The JWT grant token they need is refreshed by the workflow itself.
if
Step 3
Build the folder path and filename
Folder comes from the Client custom field, or from the first signer's name when it is blank; the file is named by completed date, document type and counterparty so a folder sorts by signing date.
SP
Step 4
Find or create the client folder and upload both files
One Microsoft Graph call finds or creates the client folder in the document library. The signed PDF and the certificate are then uploaded into it, through a Graph upload session when a file is over 4 MB.
T
Step 5
Post the filing to a Teams channel
One message in the channel you choose names the document, the signers, the completed date and a direct link to the file in SharePoint, so the account owner sees it without opening DocuSign.
if
Step 6
Flag anything that could not be filed
If the upload fails, the Teams message still posts with the error text and a link to the envelope in DocuSign, and n8n keeps the execution in its list for a re-run.

What changes once it runs

Every signed document is in SharePoint within a minute or two of the last signature. Same name pattern, same folder logic, every time.
Certificates of completion sit next to their contracts, so an audit does not start with a DocuSign search.
One Teams post per completed envelope tells the account owner it is done and where it lives.
Nothing depends on a person downloading the attachment from the DocuSign email.

What you get

n8n workflow export with the Webhook node, HMAC check, DocuSign download calls, SharePoint upload and Teams post wired up
Setup guide covering the DocuSign integration key, JWT consent, the Connect configuration and the Microsoft Graph credential
A naming and folder convention sheet you can edit before the first run
Recorded walkthrough of a test envelope going from a DocuSign developer sandbox to a signed file in SharePoint
Make scenario blueprint on the DocuSign, OneDrive and Microsoft Teams modules, with one API-call module for the certificate download

Before you start

DocuSign account on an API plan (Developer Starter or above); the Personal, Standard and Business Pro seats do not list API or Connect access
A DocuSign integration key with JWT consent granted, created on the Apps and Keys page of your account (the guide walks through it)
Microsoft 365 with a SharePoint document library or OneDrive folder the workflow can write to
A Teams channel for the posts and an account allowed to post in it
n8n Cloud or self-hosted n8n with a public HTTPS URL for DocuSign Connect to call

Built for

Questions before you buy

Which DocuSign plan do I need?: An API plan. DocuSign sells the eSignature REST API and Connect through its Developer plans (Starter, Intermediate, Advanced, Enhanced) and describes the Personal, Standard and Business Pro seats as built for the web app and its own integrations, so check what your account includes before buying. The developer sandbox is free and is where the walkthrough was recorded.
How does it know which client folder to use?: From an envelope custom field called Client, which your senders fill when they send from a template. If the field is blank, the first signer's name is used instead. Both the field name and the fallback are set in one node.
What happens if SharePoint rejects the upload?: Teams still gets the message, with the error text and a link to the envelope in DocuSign, and the execution stays in n8n's list so you can re-run it once the folder or permission is fixed. The signed document is never lost; DocuSign keeps it.
Can it file to Google Drive and post to Slack instead?: Yes. Swap the SharePoint node for Google Drive and the Teams node for Slack; the rest is unchanged, and the setup guide shows both swaps. The export we test is the Microsoft version.
Does it run on Make or Zapier?: Make, yes: the DocuSign, OneDrive and Microsoft Teams modules cover every step except the certificate download, which uses the DocuSign app's generic API-call module, and the blueprint is in the package. Zapier is not included, because we have not tested a full Zap with the document download, and we only ship what we have run end to end.

Nearby on the shelf

Whole catalog