How to connect Microsoft Teams and Docusign
Create a New Scenario to Connect Microsoft Teams and Docusign
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Microsoft Teams, triggered by another scenario, or executed manually (for testing purposes). In most cases, Microsoft Teams or Docusign will be your first step. To do this, click "Choose an app," find Microsoft Teams or Docusign, and select the appropriate trigger to start the scenario.

Add the Microsoft Teams Node
Select the Microsoft Teams node from the app selection panel on the right.

Microsoft Teams
Configure the Microsoft Teams
Click on the Microsoft Teams node to configure it. You can modify the Microsoft Teams URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Docusign Node
Next, click the plus (+) icon on the Microsoft Teams node, select Docusign from the list of available apps, and choose the action you need from the list of nodes within Docusign.

Microsoft Teams
⚙

Docusign

Authenticate Docusign
Now, click the Docusign node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Docusign settings. Authentication allows you to use Docusign through Latenode.
Configure the Microsoft Teams and Docusign Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Microsoft Teams and Docusign Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙

Docusign
Trigger on Webhook
⚙
Microsoft Teams
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Microsoft Teams, Docusign, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Microsoft Teams and Docusign integration works as expected. Depending on your setup, data should flow between Microsoft Teams and Docusign (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Microsoft Teams and Docusign
Docusign + Salesforce + Microsoft Teams: When a document is fully signed in Docusign, the automation updates a specified record in Salesforce. Then, a message is sent to a Microsoft Teams channel to notify the team about the update.
Docusign + Microsoft Teams + Slack: When a document is fully signed in Docusign, send a message to a specific Slack channel. Then, alert the team via a Microsoft Teams channel.
Microsoft Teams and Docusign integration alternatives
About Microsoft Teams
Use Microsoft Teams in Latenode to automate notifications and approvals. Instead of manual updates, automatically post messages based on triggers from other apps (like CRM or databases). Streamline workflows and improve team communication by connecting Teams to your automated processes without complex coding.
Similar apps
Related categories

About Docusign
Integrate DocuSign with Latenode to automate contract workflows. Automatically send, track, and store signed documents. Trigger actions based on signature status, update databases, and alert teams. Latenode adds flexible logic and integrations beyond standard DocuSign options, with pay-per-execution pricing and visual flow design.
Similar apps
Related categories
See how Latenode works
FAQ Microsoft Teams and Docusign
How can I connect my Microsoft Teams account to Docusign using Latenode?
To connect your Microsoft Teams account to Docusign on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Microsoft Teams and click on "Connect".
- Authenticate your Microsoft Teams and Docusign accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically notify Teams channel upon document completion?
Yes, you can! Latenode enables real-time notifications to Microsoft Teams when a document is signed in Docusign. This ensures immediate team awareness and accelerates workflows, utilizing visual logic and AI.
What types of tasks can I perform by integrating Microsoft Teams with Docusign?
Integrating Microsoft Teams with Docusign allows you to perform various tasks, including:
- Send Docusign envelopes directly from a Microsoft Teams channel.
- Post updates to a Teams channel when a document is signed.
- Create Docusign envelopes when a new team member joins.
- Automatically archive signed documents to SharePoint from Teams.
- Trigger document requests based on Teams channel activity.
Can I use JavaScript within my Microsoft Teams + Docusign automation?
Yes! Latenode's JavaScript node allows you to add custom logic, manipulate data, and extend the standard Microsoft Teams and Docusign integration, easily handling complex scenarios.
Are there any limitations to the Microsoft Teams and Docusign integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex document formatting may require custom JavaScript adjustments.
- Very high volume document processing may require scaling considerations.
- Initial setup requires admin permissions for both applications.