Connect Azure DevOps and Google Drive to unlock the power of automation
- No credit card required
- Free forever for core features
- 14-day trial for premium features and apps
How Zapier works
Zapier makes it easy to integrate Azure DevOps with Google Drive - no code necessary. See how you can get setup in minutes.
Choose a trigger
A trigger is the event that starts your Zap—like a "Completed Build" from Azure DevOps.
Add your action
An action happens after the trigger—such as "Copy File" in Google Drive.
You’re connected!
Zapier seamlessly connects Azure DevOps and Google Drive, automating your workflow.
Supported triggers and actions
Zapier helps you create workflows that connect your apps to automate repetitive tasks. A trigger is an event that starts a workflow, and an action is an event a Zap performs.
- Build DefinitionRequired
- Build Status
- ProjectRequired
Try ItTriggerInstant- ProjectRequired
- Repository
- Branch
Try ItTriggerInstant- ProjectRequired
- Area Path
- Work Item Type
Try ItTriggerInstant- ProjectRequired
- Build DefinitionRequired
ActionWrite
- ProjectRequired
- PathRequired
Try ItTriggerInstant- ProjectRequired
- Area Path
- Work Item Type
- Contains StringRequired
Try ItTriggerInstant- ProjectRequired
- Area Path
- Work Item Type
- Changed Field
Try ItTriggerInstant- ProjectRequired
- TypeRequired
- TitleRequired
- Area
- Iteration
- Assigned To
- Description
ActionWrite
Zapier is the automation platform of choice for 87% of Forbes Cloud 100 companies in 2023




93%
Customers who say using Zapier has made them better at their job
25m
Customers have created over 25 million Zaps on the platform
6 mins
The average user takes less than 6 minutes to set up a Zap
Learn how to automate Google Drive on the Zapier blog
Frequently Asked Questions about Azure DevOps + Google Drive integrations
New to automation with Zapier? You're not alone. Here are some answers to common questions about how Zapier works with Azure DevOps and Google Drive
What triggers can be used to start an integration between Azure DevOps and Google Drive?
When integrating Azure DevOps and Google Drive, we can use various triggers such as work item updates, new pull requests, or build completions in Azure DevOps. These events can automatically initiate actions in Google Drive, like creating new files or updating existing ones.
How do I authenticate my Azure DevOps account with Google Drive for integration purposes?
Authentication is done securely by connecting both accounts through our platform. You'll need to provide the necessary permissions for both your Azure DevOps and Google Drive accounts to allow seamless communication between the services.
Can we automate file creation in Google Drive from changes in Azure DevOps?
Yes, automation allows us to create or update files in Google Drive when specific changes occur in Azure DevOps, such as a work item update or a build completion.
What actions can be performed in Google Drive when triggered by an event in Azure DevOps?
We can perform several actions such as creating a new document or spreadsheet, updating existing files, or adding comments to documents whenever a configured event occurs in Azure DevOps.
Is it possible to sync work items from Azure DevOps with specific folders in Google Drive?
Yes, you can configure the integration to sync specific work items from Azure DevOps into designated folders within Google Drive. This ensures that documentation stays organized and easily accessible based on your project needs.
Can I control who has access to the files created on Google Drive through this integration?
Access control for files created via this integration is managed through Google Drive's sharing settings. You can define who accesses these files after they have been created based on your organizational policies.
Do I need admin rights on both platforms to set up the integration?
Admin rights may be required at least initially for authorization purposes when setting up the connection between Azure DevOps and Google Drive. Once linked, ongoing management typically does not require continued admin access unless permissions change.