Google Cloud Datastore
Look up, query and upsert entities in Google Cloud Datastore (Google OAuth2).
OCNORA ships 4 typed Google Cloud Datastore 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 Datastore
- 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 Datastore
Operations, grouped by what they do to your data.
A sample Google Cloud Datastore workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Datastore trigger is needed.
- 2Lookupcloud_datastore.lookupLook up Datastore entities by key and return them as plain JSON.
- 3Delete Entitycloud_datastore.deleteDelete a Datastore entity by key.
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
- Delete EntityDelete a Datastore entity by key.cloud_datastore.delete
- LookupLook up Datastore entities by key and return them as plain JSON.cloud_datastore.lookup
- Run QueryRun a GQL query against Datastore and return plain entities.cloud_datastore.run_query
- Upsert EntityCreate or overwrite a Datastore entity from plain JSON properties.cloud_datastore.upsert
Google Cloud Datastore questions
- How does OCNORA authenticate with Google Cloud Datastore?
- 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 Datastore?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Cloud Datastore operation I need is not listed?
- Where Google Cloud Datastore 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 Datastore?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Cloud Datastore 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 Cloud Datastore 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.