New file in Google Drive
Emit newly created files in the selected Google Drive folder. Direct children only; existing files moved into the folder are not new files.
Ready-made Workflow
Connect Drive and BigQuery using a Google account registered for BigQuery OAuth testing. Select a dedicated Drive folder and an existing table with a compatible schema. Use the same Google Cloud project in Project ID, Configuration → Destination table, and Job reference. After the first poll, upload a new UTF-8 CSV up to 5 MiB with one header row. FastHook downloads the File and submits an append job with an ID derived from the Drive file. Check the job status in BigQuery to confirm the load.
What gets copied
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Emit newly created files in the selected Google Drive folder. Direct children only; existing files moved into the folder are not new files.
Continue only when the configured conditions match the incoming record.
Download a binary Drive file as inline Base64 URL data or a secure stored-file reference.
Load an authorized File into a BigQuery table using a multipart load job.
Before activation
Connect your own Google Drive account and review the provider settings used by this Workflow.
Connect your own Google BigQuery account and review the provider settings used by this Workflow.
Questions
No. FastHook creates a disconnected Draft. Connect your own Google Drive, Google BigQuery accounts before activation.
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.