Import Google Drive Videos with Zapier

Use Zapier to detect a new file in a controlled Google Drive folder, then call a trusted backend that validates the event and starts a supported DynTube URL or server upload. Keeping DynTube credentials on your server prevents them from being copied into a browser, shared Zap, or third-party log.

Before building the Zap

• Choose the destination DynTube project and verify its processing settings.
• Create a dedicated Drive folder and service identity with only required access.
• Prepare a backend endpoint that authenticates Zapier and keeps the DynTube API key server-side.
• Decide how you will de-duplicate retries and map Drive file IDs to DynTube video IDs.

Configure the Google Drive trigger

1. Select Google Drive as the trigger app and choose the new-file event appropriate to the folder.
2. Connect the intended Google account with the narrowest practical permissions.
3. Select the dedicated source folder.
4. Test with a real video and confirm the event includes a stable Drive file ID, name, MIME type, size, and an authorized download reference.

Send the event to your backend

1. Use Webhooks by Zapier to POST the Drive file metadata to your HTTPS endpoint.
2. Add your own webhook authentication secret and verify it on the server.
3. Reject unexpected MIME types, oversized sources, duplicate Drive IDs, and unknown destination projects.
4. Have the backend obtain or stream the file and call the current DynTube upload contract.
5. Persist the DynTube upload or video identifier before returning success to Zapier.

A remote URL must remain reachable for the entire DynTube fetch. Google Drive sharing pages are not necessarily direct media URLs, and temporary links can expire. If a stable authorized fetch cannot be guaranteed, stream the file through your server or another supported ingestion worker.

Make retries safe

Use the Drive file ID as the external idempotency key. After a timeout, query your stored mapping or DynTube state before uploading the same file again. Record transfer and processing as separate states, and only mark the automation complete after publication succeeds.

Monitor the workflow

• Alert on repeated Zap or backend failures.
• Keep sanitized request IDs, not credentials or full signed URLs.
• Review processing errors in DynTube and preserve the original Drive file for retry.
• Test one-file, duplicate-event, expired-link, unsupported-file, and capacity-limit cases before enabling the folder for a team.