Batch Update
google_slides.batch_update
ActionBusiness appsconnection required
Calls the Google Slides API POST /v1/presentations/{id}:batchUpdate.
Add slides, insert text, place images — every Slides write.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Slides
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 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 |
|---|---|---|---|---|---|
presentation_id The deck to write to. Supports {{ }}. | string | Yes | — | — | — |
requests A Slides requests array, e.g. [{"createSlide": {"slideLayoutReference": {"predefinedLayout": "TITLE_AND_BODY"}}}]. Accepts a JSON string or an array from an upstream step. | array | Yes | — | ≥ 1 characters; array of object | — |
revision_id Optional. The revision this write assumes; Slides rejects the batch rather than applying it over someone else's edit. | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
presentation_id The deck that was written to. | string | — |
url Editor link to the deck. | string | — |
replies One reply per request, in order, as Slides sent it. | array | — |
reply_count How many replies came back. | number | — |
object_ids Ids Slides minted for this batch (createSlide, createImage, createTable...), in reply order — address them in the next step. | array | — |
revision_id The deck's revision after the write. | string | — |
{
"object_ids": [],
"ok": false,
"presentation_id": "",
"replies": [],
"reply_count": 0,
"revision_id": "",
"url": ""
}Related Google Slides nodes
See Batch Update run in a workflow.
In a technical demo we add the Google Slides connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.