> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/update_page_properties.md).

# Notion Update Page Properties

Blocks for changing pages that already exist in Notion workspaces and databases.

## Notion Update Page Properties

### What it is

Update an existing Notion page's properties, its title among them, its icon or cover, or whether it is in the trash. The page's content is left as it is.

### How it works

This block updates an existing page through the Notion API. It can rename the page, set its properties, change its emoji icon or cover image, and move it to the trash or restore it, all in one request. The page must be shared with your integration. It leaves the page's content as it is; the Notion Append To Page block adds content to the end of a page.

Properties are named as they appear in the database, and each value is written as the type that property already has: a name for a select or status, a list of names for a multi-select, a date string for a date, and so on. The block reads the page first to learn those types. Before anything is written, it refuses a property the page does not have, a read-only one such as a formula, and a value for a people, relation or files property. A null value clears the property and unchecks a checkbox, but a status goes back to its default option if it has one.

### Inputs

| Input       | Description                                                                                                                                                                                      | Type            | Required |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------- | -------- |
| page\_id    | ID of the page to update. Must be accessible by the connected integration.                                                                                                                       | str             | Yes      |
| title       | New title for the page                                                                                                                                                                           | str             | No       |
| properties  | Properties to set by name (e.g., {'Status': 'Done', 'Tags': \['urgent']}). Each value is written as the type the property already has; null clears it, or resets a status to its default option. | Dict\[str, Any] | No       |
| icon\_emoji | Emoji to use as the page icon (e.g., '📄', '🚀')                                                                                                                                                 | str             | No       |
| cover\_url  | URL of an image to use as the page cover                                                                                                                                                         | str             | No       |
| in\_trash   | True moves the page to the trash, False restores it. Leave empty to keep it where it is.                                                                                                         | bool            | No       |

### Outputs

| Output    | Description                           | Type |
| --------- | ------------------------------------- | ---- |
| error     | Error message if the operation failed | str  |
| page\_id  | ID of the updated page.               | str  |
| page\_url | URL of the updated page.              | str  |

### Possible use case

**Task Status Sync**: Mark a task page as Done in a Notion database when the matching issue closes in another system.

**Content Workflow**: Move a draft through Review and Published by setting its Status property as each step finishes.

**Cleanup**: Move pages that a workflow no longer needs to the trash, where they can still be restored.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agpt.co/docs/integrations/block-integrations/update_page_properties.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.