Upsert Entity
cloud_datastore.upsert
ActionGoogle Cloudconnection required
Calls Datastore REST POST /projects/{project}:commit (NON_TRANSACTIONAL upsert).
Create or overwrite a Datastore entity from plain JSON properties.
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, 2 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 | — | — | — |
properties Entity properties as plain JSON; the whole entity is overwritten, so send every property you want kept. | object | Yes | — | ≥ 1 characters | {"count":1,"title":"Hello"} |
- At least one of name, id must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"properties": {
"count": 1,
"title": "Hello"
}
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
key | object | — |
{
"key": {},
"ok": false
}Related Google Cloud Datastore nodes
See Upsert Entity 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.