Lookup
cloud_datastore.lookup
ActionGoogle Cloudconnection required
Calls Datastore REST POST /projects/{project}:lookup.
Look up Datastore entities by key and return them as plain JSON.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Datastore
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id, database_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
7 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
database_id Datastore database id (blank = default; overrides connection). | string | No | — | — | — |
kind Entity kind; the call is refused without it. | string | Yes | — | — | — |
name Key name (string id). Use this or 'id'. | string | No | — | — | — |
id Key numeric id. Use this or 'name'. | string | No | — | — | — |
namespace Namespace (optional). | string | No | — | — | — |
keys Extra keys as JSON [{"kind","name"|"id"}] (optional). | array | No | — | array of object | — |
- At least one of name, id, keys must be set.
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
entities | array | — |
missing | array | — |
count | number | — |
{
"count": 0,
"entities": [],
"missing": []
}Related Google Cloud Datastore nodes
See Lookup run in a workflow.
In a technical demo we add the Google Cloud Datastore connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.