Google Cloud Storage for Firebase
The Cloud Storage for Firebase API enables programmatic management of Cloud Storage buckets for use in Firebase projects (Google OAuth2).
OCNORA ships 4 typed Google Cloud Storage for Firebase 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 Cloud Storage for Firebase
- 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 Cloud Storage for Firebase
Operations, grouped by what they do to your data.
Create and send 1
Read and search 2
Delete and cancel 1
A sample Google Cloud Storage for Firebase workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Storage for Firebase trigger is needed.
- 2Get Bucketfirebase_storage.get_bucketGets a single linked storage bucket.
- 3Add Firebasefirebase_storage.add_firebaseLinks a Google Cloud Storage bucket to a Firebase project.
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 4
- Add FirebaseLinks a Google Cloud Storage bucket to a Firebase project.firebase_storage.add_firebase
- Delete Default BucketUnlinks and deletes the default bucket.firebase_storage.delete_default_bucket
- Get BucketGets a single linked storage bucket.firebase_storage.get_bucket
- List BucketsLists the linked storage buckets for a project.firebase_storage.list_buckets
Google Cloud Storage for Firebase questions
- How does OCNORA authenticate with Google Cloud Storage for Firebase?
- 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 Cloud Storage for Firebase?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Cloud Storage for Firebase operation I need is not listed?
- Where Google Cloud Storage for Firebase 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 Cloud Storage for Firebase?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Cloud Storage for Firebase 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.
More in Files & storage
See your first Google Cloud Storage for Firebase 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.