> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/embedding/embed-in-business-apps/notion.md).

# Notion

[Notion](https://www.notion.so/) is a great place to organise your workplace knowledge in a single place. It's perfect to document and explain internal processes as well as tracking common objectives, such as [OKRs](https://en.wikipedia.org/wiki/OKR).

By integrating with Notion, Whaly is giving you the ability to embed reports directly within your Notion pages so that you can track your KPIs directly within your everyday tool without having to log to Whaly each time.

## Embed a Whaly report/question in a Notion page

1. On Whaly 🐳, generate a sharing link named "Notion" without a password for the report you wish to embed. [You can learn more here.](/workspace/sharing-and-collaboration/share-a-report-by-link.md)
2. On Notion, open the page in which you wish to embed your report and type `/` to list the blocks that you can integrate within Notion. Select the "**Embed**" block type.
3. In the "**Embed link**" input, paste the public sharing link of your report. 
4. Click on the "**Embed link**" button to validate.

![](https://34758050-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MC1g4I2_CgXd0qAq1P7%2Fuploads%2FfrE8u7pa4EU4Mlpjljmb%2Fimage.png?alt=media\&token=bc6c29e4-48ff-4de0-b2a1-9a515626369a)

4\. You can now resize your Whaly report so that it fits nicely in your notion document. 👌

And then, you're good to go 🤘 You can start tracking your numbers directly within your Notion documents and attach your real numbers to your OKRs definition for example 🤩


---

# 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://docs.whaly.io/embedding/embed-in-business-apps/notion.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.