> 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/append_to_page.md).

# Notion Append To Page

Blocks for adding content to pages that already exist in Notion.

## Notion Append To Page

### What it is

Add content to the end of an existing Notion page. Supports markdown content.

### How it works

This block adds content to the end of an existing page through the Notion API. The content can be markdown, which is converted to Notion blocks the same way the Create Page block converts it: headings, bulleted and numbered lists, code blocks, quotes, dividers and paragraphs.

Notion takes at most 100 blocks per request, so longer content is sent in several requests, in order. The block outputs the IDs of the new blocks in page order. A line longer than Notion's 2,000-character limit for a run of text is split into several runs within the same block. If a later request fails, the block outputs only the error, which says how many blocks were added and gives the ID of the last one, so nothing wired to the block's IDs runs on a partial append. The failed request's blocks may or may not have reached the page, so check it before retrying.

### Inputs

| Input    | Description                                                                                                | Type | Required |
| -------- | ---------------------------------------------------------------------------------------------------------- | ---- | -------- |
| page\_id | ID of the page to add content to. Must be accessible by the connected integration.                         | str  | Yes      |
| content  | Content to add at the end of the page. Can be plain text or markdown - will be converted to Notion blocks. | str  | Yes      |

### Outputs

| Output     | Description                                         | Type       |
| ---------- | --------------------------------------------------- | ---------- |
| error      | Error message if the operation failed               | str        |
| block\_ids | IDs of the blocks added to the page, in page order. | List\[str] |

### Possible use case

**Running Logs**: Add each day's summary to the bottom of a shared log page.

**Meeting Notes**: Append action items to a meeting page once a transcript has been processed.

**Research Collection**: Add findings to a page as a workflow gathers them, without rewriting what is already there.

***


---

# 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/append_to_page.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.