Troubleshooting Shared Drive Sync with Zapier/Make.com

When connecting Google Shared Drives to automation platforms like Zapier or Make (formerly Integromat), workflows frequently fail with missing drive drop-downs, “File not found” (404) errors, or permission rejections (403). These integration breakdowns typically happen because the automated connection either targets the wrong drive container, lacks the necessary Shared Drive API parameters, or runs under an unauthorized Google identity.

Quick Answer

Shared Drive sync failures in Zapier and Make occur when the connected Google account is not a member of the Shared Drive, the scenario is configured for “My Google Drive” instead of “Shared Drive,” or API permissions lack supportsAllDrives. First, verify the connected account is a Content Manager, then explicitly select your Shared Drive in the app’s configuration settings.

---

Why Shared Drive Integrations Behave Differently

Automations that work seamlessly in personal “My Drive” folders often fail immediately when moved to a Shared Drive. This occurs because Google Drive uses different backend rules for Shared Drives:

• Container Segregation: In personal Google Drive, files are tied to individual user accounts. In Shared Drives, files are owned by the organization container. Automations must query distinct endpoints.
• The supportsAllDrives Requirement: Under Google’s Drive API v3, calls made by tools like Zapier or Make must pass supportsAllDrives=true and includeItemsFromAllDrives=true. If the integration step omits these flags, the automation will return “File not found” even if the file is clearly visible in your browser.
• Identity and Permissions: Zapier and Make interact with Google Drive using the specific Google account you authorized via OAuth. If that identity is not explicitly listed on the Shared Drive’s member roster, the platform cannot see the drive.

---

Step-by-Step Diagnostic and Resolution Workflow

Step 1: Verify the Connected Identity’s Role

Check which Google Workspace account was used to create the connection in Zapier or Make.

1. Open your scenario or Zap and inspect the Google Drive Connection.
2. Note the authenticated email address.
3. Open Google Drive in your browser, navigate to the target Shared Drive, and click Manage members.
4. Confirm that the exact connected email is added as a member.
5. Verify the role:
   • Viewer / Commenter: The automation can only read data; write and upload steps will fail with a 403 error.
   • Contributor: The automation can create and edit files, but it cannot delete or trash items.
   • Content Manager (Recommended): The automation can create, edit, move, and trash files.
   • Manager: Required if the automation adjusts folder sharing or member permissions.

If your integration is receiving permission errors despite valid credentials, review Troubleshooting Shared Drive API 403: insufficientFilePermissions and Fix: “Manager” vs. “Content Manager” Conflict.

Step 2: Configure “Drive” and “Shared Drive” Drop-downs Correctly

Both Zapier and Make require you to specify where the system should search or write.

In Zapier:

• Look for the field labeled Drive. By default, it is often set to My Google Drive.
• Change this field to the specific name of your Shared Drive.
• If the dropdown list is blank, select Custom and paste the Shared Drive ID (the alphanumeric string found at the end of the URL when viewing the Shared Drive root in a browser).

In Make (Integromat):

• In modules like Watch Files in a Folder or Upload a File, locate Enter a Folder ID or Drive Type.
• Set the drive selector from My Drive to Shared Drive (Team Drive).
• Select your specific Shared Drive from the list. If you map it dynamically, ensure you pass both the Drive ID and the Folder ID.

Step 3: Check Container-Level Security Settings

Shared Drive Managers can enable restrictions that silently block third-party tools from interacting with files.

1. In Google Drive, right-click the Shared Drive and select Shared drive settings.
2. Check the status of Sharing with non-members (or “Allow people outside this shared drive to access files”).
3. If this setting is enabled and your automation attempts to share uploaded assets with an external recipient or webhook payload, Google will abort the action.

For an explanation of how this setting causes workflow issues, see Why “Prevent non-members from accessing files” is breaking flow.

Step 4: Re-Authorize OAuth Scopes and App Access

If your Google Workspace administrator restricted third-party API access, Zapier or Make might be operating with limited permissions that exclude Shared Drives.

1. Go to your automation platform’s Connections or Apps manager.
2. Reconnect or re-authenticate your Google Drive account.
3. Review the Google consent prompt: ensure you approve full access to manage files across all Google Drive storage.
4. If an administrator policy blocks third-party app consent, your Workspace admin must approve the Zapier or Make Client ID under Admin Console > Security > Access and data control > API controls > App access control.

---

Hidden Problem: Polling Triggers Missing Rapid Batch Uploads

A frequent issue with triggers like “New File in Folder” inside Shared Drives is skipped files.

Zapier and Make use polling schedules (checking Google Drive every 1 to 15 minutes depending on your subscription tier). If your automated processes drop hundreds of files into a Shared Drive folder simultaneously, the API pagination limit can cause the integration to miss files created within that same second.

• Workaround: If you run high-volume bulk imports, do not rely on standard folder polling triggers. Instead, configure a script or service to push events into a Make or Zapier Custom Webhook, or use Google Drive Push Notifications via Cloud Pub/Sub to ensure every file event is captured.