> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tekma.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Send a capture to Notion

> Connect a Notion database, choose its data source, and create a report page with supported properties.

Notion delivery creates a page in a database/data source from a saved capture. A workspace owner connects the database. Members use the configured destination; the database must be shared with the exact Notion OAuth connection or internal integration used by Tekma.

## Requirements and connection

Use **Continue to Notion** when OAuth is enabled, or **Use a token instead** with an internal integration secret. Before saving, share the target database with that connection and grant content read and insert capabilities. You need a workspace owner to configure the integration and capture edit permission to send. The connection field is **Database ID**. **Title property** is an optional compatibility setting in the form; current metadata discovery identifies the title property by its Notion type.

1. Open **Settings → Integrations** and choose **Connect** next to Notion.
2. Choose **Continue to Notion**, or choose **Use a token instead** and enter the integration secret.
3. Enter **Database ID**, optionally enter **Title property**, and choose **Connect Notion**. Tekma checks database access and capabilities.
4. Confirm the row shows **Connected**. Use **Manage** to save a new database while retaining an existing authorization.

## Send a page

1. Open a saved capture and choose **Send to app → Notion**.
2. Wait for **Loading preview…** and review the database, data source, page title and private capture link. If the database exposes multiple data sources, select the intended one; a database ID alone does not choose between them.
3. Use **Edit visible properties** to choose supported values. Tekma supports a title, rich text, number, checkbox, select, multi-select, status, date-only, HTTPS URL, email, and phone properties. People, relations, files, and computed properties are unavailable.
4. Add context if needed and choose **Send to Notion**. Nothing is created while you are only reviewing the preview.
5. Open the returned page in Notion and verify its data source, title, properties, and body. If delivery is not confirmed, inspect Notion before retrying.

| Field                 | Supported values                                                           |
| --------------------- | -------------------------------------------------------------------------- |
| Database/data source  | Connected database; explicit data-source choice when multiple are exposed  |
| Title                 | The discovered Notion title property                                       |
| Text/value properties | Rich text, number, checkbox                                                |
| Option properties     | Existing select, multi-select, and status options                          |
| Date/link/contact     | Date-only, HTTPS URL, email, phone                                         |
| Unsupported           | People, relations, files, formulas, rollups, and other computed properties |

The page body includes saved report text, sanitized source URL, capture kind and a private Tekma link. Tekma does not embed the recording, screenshots, comments, or diagnostic payloads, and a Notion reader does not automatically receive Tekma access. Tekma confirms the created page and ordered body paragraphs; it refuses an oversized body rather than silently truncating it.

## Troubleshooting

If the database or title property cannot load, share the database with the exact connection and verify content read/insert capabilities. Refresh the preview after editing the Notion schema. A property can be visible yet unavailable when it is computed or a people/relation type. If several data sources appear, select one explicitly. Search Notion by title before retrying an ambiguous response.