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

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

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

Microsoft To Do
⚙

Google Drive

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

Google Drive
Trigger on Webhook
⚙
Microsoft To Do
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Microsoft To Do, Google Drive, 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 To Do and Google Drive integration works as expected. Depending on your setup, data should flow between Microsoft To Do and Google Drive (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Microsoft To Do and Google Drive
Microsoft To Do + Google Drive + Microsoft Teams: When a task is completed in Microsoft To Do, its details are saved to a new text file in Google Drive, and a message with a link to the file is sent to a dedicated channel in Microsoft Teams.
Google Drive + Microsoft To Do + Google Calendar: When a new file is added to Google Drive, a task to review the file is created in Microsoft To Do, and an event is created in Google Calendar to schedule the review.
Microsoft To Do and Google Drive integration alternatives
About Microsoft To Do
Automate task management by integrating Microsoft To Do with Latenode. Automatically create tasks from emails, database entries, or other apps. Sync tasks between systems, set reminders based on triggers, and manage projects visually using Latenode's low-code interface. Stop manual updates and build scalable task workflows.
Related categories

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
See how Latenode works
FAQ Microsoft To Do and Google Drive
How can I connect my Microsoft To Do account to Google Drive using Latenode?
To connect your Microsoft To Do account to Google Drive on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Microsoft To Do and click on "Connect".
- Authenticate your Microsoft To Do and Google Drive accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically back up completed tasks to Google Drive?
Yes, you can! Latenode allows you to automatically back up completed Microsoft To Do tasks to a Google Drive folder, ensuring important data is securely stored and easily accessible for auditing.
What types of tasks can I perform by integrating Microsoft To Do with Google Drive?
Integrating Microsoft To Do with Google Drive allows you to perform various tasks, including:
- Automatically saving task attachments from To Do to a Google Drive folder.
- Creating a Google Doc report of completed tasks on a weekly basis.
- Generating shareable Google Drive links when a task is created.
- Adding new Google Drive files to a To Do task as attachments.
- Updating a Google Sheet with task completion status in real-time.
Can I use JavaScript to enhance this integration?
Yes! Latenode supports JavaScript, letting you customize the integration with complex logic or data transformations.
Are there any limitations to the Microsoft To Do and Google Drive integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Large file transfers might impact workflow execution time.
- Microsoft To Do API rate limits may affect high-volume task processing.
- Changes to Google Drive or To Do APIs could require workflow updates.