Google Parallelstore
Google CloudOAuth 2.0Connection test available
Parallelstore (Google OAuth2).
OCNORA ships 6 typed Google Parallelstore 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 Parallelstore
- 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 Parallelstore
Operations, grouped by what they do to your data.
Create and send 1
Read and search 3
Update 1
Delete and cancel 1
A sample Google Parallelstore workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Parallelstore trigger is needed.
- 2Export Dataparallelstore.export_dataCopies data from Parallelstore to Cloud Storage.
- 3Create Instanceparallelstore.create_instanceCreates a Parallelstore instance in a given project and location.
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 6
- Create InstanceCreates a Parallelstore instance in a given project and location.parallelstore.create_instance
- Delete InstanceDeletes a single instance.parallelstore.delete_instance
- Export DataCopies data from Parallelstore to Cloud Storage.parallelstore.export_data
- Get InstanceGets details of a single instance.parallelstore.get_instance
- List InstancesLists all instances in a given project and location.parallelstore.list_instances
- Update InstanceUpdates the parameters of a single instance.parallelstore.update_instance
Google Parallelstore questions
- How does OCNORA authenticate with Google Parallelstore?
- 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 Parallelstore?
- 6 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Parallelstore operation I need is not listed?
- Where Google Parallelstore 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 Parallelstore?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Parallelstore 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 Parallelstore 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.