How to connect Google Drive and Microsoft Teams
Create a New Scenario to Connect Google Drive and Microsoft Teams
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 Google Drive, triggered by another scenario, or executed manually (for testing purposes). In most cases, Google Drive or Microsoft Teams will be your first step. To do this, click "Choose an app," find Google Drive or Microsoft Teams, and select the appropriate trigger to start the scenario.

Add the Google Drive Node
Select the Google Drive node from the app selection panel on the right.


Google Drive

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


Google Drive
⚙
Microsoft Teams

Authenticate Microsoft Teams
Now, click the Microsoft Teams node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Microsoft Teams settings. Authentication allows you to use Microsoft Teams through Latenode.
Configure the Google Drive and Microsoft Teams 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 Google Drive and Microsoft Teams 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
⚙
Microsoft Teams
Trigger on Webhook
⚙

Google Drive
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Google Drive, Microsoft Teams, 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 Google Drive and Microsoft Teams integration works as expected. Depending on your setup, data should flow between Google Drive and Microsoft Teams (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Google Drive and Microsoft Teams
Google Drive + Microsoft Teams + Slack: When a new file is added to a specific folder in Google Drive, a message with a link to the file is posted in a designated Microsoft Teams channel, and a notification is sent to users in a specified Slack channel.
Zoom + Google Drive + Microsoft Teams: When a Zoom recording is completed, the recording is uploaded to a specific folder in Google Drive. Then, a message with the link to the recording is sent to a Microsoft Teams channel.
Google Drive and Microsoft Teams integration alternatives

About Google Drive
Automate file management with Google Drive in Latenode. Trigger workflows from new files, automatically back up data, or sync documents across platforms. Use Latenode's visual editor and built-in tools for custom logic, JavaScript, and AI. Scale your Google Drive workflows without code and connect to any service.
Similar apps
Related categories
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
See how Latenode works
FAQ Google Drive and Microsoft Teams
How can I connect my Google Drive account to Microsoft Teams using Latenode?
To connect your Google Drive account to Microsoft Teams on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Google Drive and click on "Connect".
- Authenticate your Google Drive and Microsoft Teams accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically post Google Drive file updates to Teams?
Yes, you can! Latenode's visual editor makes it simple to monitor Google Drive folders and instantly notify your team on Microsoft Teams about new files, boosting collaboration.
What types of tasks can I perform by integrating Google Drive with Microsoft Teams?
Integrating Google Drive with Microsoft Teams allows you to perform various tasks, including:
- Post new Google Drive files directly to a Microsoft Teams channel.
- Create new Google Drive folders when a new Teams channel is created.
- Send a digest of recent Google Drive activity to a Teams channel daily.
- Automatically back up Microsoft Teams files to a designated Google Drive folder.
- Search Google Drive files directly from Microsoft Teams using a custom command.
What kind of Google Drive triggers are available on Latenode?
Latenode supports triggers like new file, updated file, and file moved. Use them to start automated workflows.
Are there any limitations to the Google Drive and Microsoft Teams integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Large file transfers may take longer depending on network speeds.
- Complex workflows with numerous steps may require more processing time.
- Real-time updates are subject to API rate limits of both services.