Connect Google Drive and Netlify to unlock the power of automation
- No credit card required
- Free forever for core features
- 14-day trial for premium features and apps
Set up your first integration
Quickly connect Google Drive to Netlify with a Zapier template.
Our most popular template
How Zapier works
Zapier makes it easy to integrate Google Drive with Netlify - 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 "New File" from Google Drive.
Add your action
An action happens after the trigger—such as "Start Deploy" in Netlify.
You’re connected!
Zapier seamlessly connects Google Drive and Netlify, 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.
- Drive
Try ItTriggerPolling- Drive
- Folder
Try ItTriggerPolling- FileRequired
- Convert to Document?
- File Name
- Drive
- Folder
ActionWrite- Drive
- Folder
- Folder NameRequired
ActionWrite
- Drive
- Folder
- Include Deleted Files?
Try ItTriggerPolling- Drive
- Folder
- Include_deleted
Try ItTriggerPolling- Drive
- Folder
- FileRequired
- Convert to Document?
- File Name
- File Extension
- Idempotency_key
ActionWrite- FileRequired
- Drive
- Folder
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 Google Drive + Netlify integrations
New to automation with Zapier? You're not alone. Here are some answers to common questions about how Zapier works with Google Drive and Netlify
How can I trigger a deployment on Netlify when a file is added to Google Drive?
To trigger a deployment on Netlify when a file is added to Google Drive, you can set up an automation that watches for new files in a specific Google Drive folder. Once a new file is detected, it can initiate a build hook to deploy your site on Netlify. This process requires setting up both the Google Drive and Netlify actions properly in our integration platform.
Can I use updated files in Google Drive to trigger builds on Netlify?
Yes, you can use updates or modifications to files within Google Drive as triggers for builds on Netlify. By monitoring changes in specific folders or files, our platform can automatically commence deployments whenever there are alterations.
Is it possible to stop a deployment if a certain file type is uploaded to Google Drive?
Currently, deployments cannot be directly stopped based on the type of file uploaded. However, you can configure triggers that only activate for specific file types by adding conditions within your automation setup.
How do I connect my Google Drive account with Netlify through the integration tool?
Connecting your Google Drive account with Netlify requires authentication of both services within our integration platform. Once authenticated, you can select desired triggers from Google Drive and corresponding actions in Netlify to automate deployments.
What happens if I delete a file from the watched folder in Google Drive? Will it affect ongoing deployments?
Deleting files from the watched folder in Google Drive does not cancel or affect ongoing deployments already triggered. The deletion will only prevent future activities related to this specific file from initiating further automations.
Are there any limitations on the number of files that can trigger an action at once within this integration?
While there aren't specific limits set by us regarding how many files can trigger an action at once, both Google Drive and Netlify may have their own restrictions based on usage tiers or account limits.
Can I filter which files should trigger deploy actions based on keywords or metadata in their names?
Yes, it's possible to filter which files should initiate deploy actions by setting up conditions that include keywords or certain metadata attributes of the filenames when configuring your integrations.