Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Notion" |
| 4 | description: "Public support knowledge for Notion." |
| 5 | category: "auth-config" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-07-16T00:00:00Z" |
| 8 | tags: |
| 9 | - "notion" |
| 10 | --- |
| 11 | # Notion |
| 12 | |
| 13 | ## Use `NOTION_RETRIEVE_PAGE` instead of deprecated/invalid `NOTION_GET_PAGE` |
| 14 | |
| 15 | `NOTION_GET_PAGE` is not the current valid slug. Use `NOTION_RETRIEVE_PAGE`, and verify available Notion tools from the marketplace/tool listing. |
| 16 | |
| 17 | ## Use the current Notion page and data-source update triggers |
| 18 | |
| 19 | The current Notion catalog includes separate triggers for page creation, page |
| 20 | content updates, page property updates, and data-source schema updates. Choose |
| 21 | the trigger that matches the event rather than expecting a page-created trigger |
| 22 | to fire for edits. Fetch the current trigger catalog before implementation and |
| 23 | use the exact returned slug. |
| 24 | |
| 25 | ## Notion page/database access is granted per integration, not per Composio auth config token |
| 26 | |
| 27 | Notion does not model access as normal OAuth scopes. Page/database access is granted per Notion integration/OAuth client ID through Notion “Capabilities” and workspace grants. If multiple Composio auth configs use the same underlying Notion integration, page authorization can overlap. |
| 28 | |
| 29 | ## Specifying a different auth config affects get/use lookup, not existing Notion token refresh |
| 30 | |
| 31 | Existing connected accounts under a different auth config continue to refresh and work. Specifying an auth config affects which connection get/use functions look for; it does not rewrite refresh behavior for already-valid connected accounts. |
| 32 | |
| 33 | ## Notion 401 can be caused by invalid refresh token after user/admin revokes integration |
| 34 | |
| 35 | A Notion refresh failure with “Invalid refresh token” is usually a token revocation issue. Common causes are the user disconnecting the integration in Notion settings or a workspace admin removing/blocking the integration. |
| 36 | |
| 37 | ## Use `NOTION_FETCH_DATA`, not `NOTION_FETCH_NOTION_DATA` |
| 38 | |
| 39 | `NOTION_FETCH_NOTION_DATA` is not valid. Use `NOTION_FETCH_DATA` instead. |
| 40 | |
| 41 | ## Large unfiltered Notion responses can hurt agent quality |
| 42 | |
| 43 | Large response payloads and overly complex structures can degrade agent behavior. Prefer narrower fetches/filters where available and track product improvements for simpler response structures. |