Short answer: Drop the "Notion → Update Page" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Page ID page_id | string | Required | Notion page ID — a UUID with hyphens. Copy from the page URL (last segment, format the 32 hex chars as 8-4-4-4-12). |
Properties (JSON) properties | string | Required | Properties to update as a JSON object. Only include properties you want to change. |
Archive Page archived | options | Optional | Set to Yes to move the page to trash |
{"page_id": "e.g. a1b2c3d4-e5f6-7890-abcd-ef1234567890","properties": "{\"Status\": {\"select\": {\"name\": \"Done\"}}, \"Priority\": {\"select\": {\"name\": \"High\"}}}","archived": "{{trigger.archived}}"}
{"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890","object": "page","properties": {"Status": {"select": {"name": "Done"}}},"last_edited_time": "2025-01-15T12:00:00.000Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.