<!-- Clearly explain the need for these changes: -->
we met some reality when merging into the docs site but this fixes it
### Changes 🏗️
updates paths, adds some guides
<!-- Concisely describe all of the changes made in this pull request:
-->
update to match reality
### Checklist 📋
#### For code changes:
- [x] I have clearly listed my changes in the PR description
- [x] I have made a test plan
- [x] I have tested my changes according to the test plan:
<!-- Put your test plan here: -->
- [x] deploy it and validate
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> Aligns block integrations documentation with GitBook.
>
> - Changes generator default output to
`docs/integrations/block-integrations` and writes overview `README.md`
and `SUMMARY.md` at `docs/integrations/`
> - Adds GitBook frontmatter and hint syntax to overview; prefixes block
links with `block-integrations/`
> - Introduces `generate_summary_md` to build GitBook navigation
(including optional `guides/`)
> - Preserves per-block manual sections and adds optional `extras` +
file-level `additional_content`
> - Updates sync checker to validate parent `README.md` and `SUMMARY.md`
> - Rewrites `docs/integrations/README.md` with GitBook frontmatter and
updated links; adds `docs/integrations/SUMMARY.md`
> - Adds new guides: `guides/llm-providers.md`,
`guides/voice-providers.md`
>
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
fdb7ff8111. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com>
Co-authored-by: bobby.gaffin <bobby.gaffin@agpt.co>
2.2 KiB
Notion Read Database
Blocks for querying and reading data from Notion databases.
Notion Read Database
What it is
Query a Notion database with optional filtering and sorting, returning structured entries.
How it works
This block queries a Notion database using the Notion API. It retrieves entries with optional filtering by property values and sorting. The block requires your Notion integration to have access to the database.
Results include all property values for each entry, the entry IDs for further operations, and the total count. The database connection must be shared with your integration from Notion.
Inputs
| Input | Description | Type | Required |
|---|---|---|---|
| database_id | Notion database ID. Must be accessible by the connected integration. | str | Yes |
| filter_property | Property name to filter by (e.g., 'Status', 'Priority') | str | No |
| filter_value | Value to filter for in the specified property | str | No |
| sort_property | Property name to sort by | str | No |
| sort_direction | Sort direction: 'ascending' or 'descending' | str | No |
| limit | Maximum number of entries to retrieve | int | No |
Outputs
| Output | Description | Type |
|---|---|---|
| error | Error message if the operation failed | str |
| entries | List of database entries with their properties. | List[Dict[str, Any]] |
| entry | Individual database entry (yields one per entry found). | Dict[str, Any] |
| entry_ids | List of entry IDs for batch operations. | List[str] |
| entry_id | Individual entry ID (yields one per entry found). | str |
| count | Number of entries retrieved. | int |
| database_title | Title of the database. | str |
Possible use case
Task Management: Query a Notion task database to find items with a specific status or assigned to a particular person.
Content Pipeline: Read entries from a content calendar database to identify posts scheduled for today or this week.
CRM Sync: Fetch customer records from a Notion database to sync with other systems or trigger workflows.