Append Block Children
notion.append_block_children
ActionBusiness appsconnection required
Calls the Notion API with the connection's credentials.
Append blocks to the end of a page or a container block.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Notion
- Secret shape
- the integration token, or {"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 |
|---|---|---|---|---|---|
block_id Id of the page or container block to append to. | string | Yes | — | — | — |
children Notion block objects to append, at least one and at most 100 per call. | array | Yes | — | ≥ 1 characters; array of object | — |
after Id of an existing child to insert behind, instead of appending at the end. | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when Notion accepted the blocks. | boolean | true |
results The block objects Notion created. | array | — |
count How many blocks were created. | number | — |
{
"count": 0,
"ok": true,
"results": []
}Notes
- A page is itself a block: pass the page id as 'block_id' to add content to the page body.
- Notion accepts at most 100 blocks and two levels of nesting per call.
- 'after' is the insertion parameter for the pinned 2022-06-28 API version; later versions replaced it with 'position'.
See Append Block Children run in a workflow.
In a technical demo we add the Notion connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.