Google Storage Transfer
Transfers data from external data sources to a Google Cloud Storage bucket or between Google Cloud Storage buckets (Google OAuth2).
OCNORA ships 8 typed Google Storage Transfer operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Storage Transfer
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Storage Transfer
Operations, grouped by what they do to your data.
Create and send 2
Update 1
Delete and cancel 1
A sample Google Storage Transfer workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Storage Transfer trigger is needed.
- 2Get Transfer Jobstorage_transfer.get_transfer_jobGets a transfer job.
- 3Create Transfer Jobstorage_transfer.create_transfer_jobCreates a transfer job that runs periodically.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 8
- Create Transfer JobCreates a transfer job that runs periodically.storage_transfer.create_transfer_job
- Delete Transfer JobDeletes a transfer job.storage_transfer.delete_transfer_job
- Get Transfer JobGets a transfer job.storage_transfer.get_transfer_job
- Get Transfer OperationGets the latest state of a long-running operation.storage_transfer.get_transfer_operation
- List Transfer JobsLists transfer jobs.storage_transfer.list_transfer_jobs
- List Transfer OperationsLists transfer operations. Operations are ordered by their creation time in reverse chronological order.storage_transfer.list_transfer_operations
- Run Transfer JobStarts a new operation for the specified transfer job. A TransferJob has a maximum of one active TransferOperation.storage_transfer.run_transfer_job
- Update Transfer JobUpdates a transfer job.storage_transfer.update_transfer_job
Google Storage Transfer questions
- How does OCNORA authenticate with Google Storage Transfer?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Storage Transfer?
- 8 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Storage Transfer operation I need is not listed?
- Where Google Storage Transfer has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Storage Transfer?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Storage Transfer calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Storage Transfer workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.