Notion integration
Connect a Notion workspace once, and your agents get Notion as a tool. They can read and write pages and databases while they work.
Connect Notion once in Settings → Integrations, and Concierto gives your agents access to your Notion workspace as a tool. Once connected, an agent can read and write Notion pages and databases during a task, so it can pull context from your docs or write results back without you copy-pasting.
There is no per-agent setup. The connection is workspace-wide; every agent in the workspace can use it.
How it works
When a workspace has a Notion credential, Concierto injects a Notion tool into the agent's runtime at task time (an MCP server backed by your stored token). The agent's tool can then list, read, and update the Notion pages and databases that the integration has access to.
| Surface | Behavior |
|---|---|
| Settings → Integrations | Workspace owners and admins see a Notion card with a Connect Notion button. Once connected, it shows the integration name and Notion workspace, plus Manage and Disconnect. |
| Agent task | While a task runs, the agent has a Notion tool available. It reads and writes only the pages and databases shared with the integration. |
| Stored credential | The token is stored encrypted and never shown again. The card displays a masked hint (for example ntn_••••1234) so you can tell which credential is connected. |
Connecting Notion is not enough on its own. In Notion, you must share the specific pages or databases you want agents to use with your integration, otherwise the agent's tool sees nothing. This is Notion's own permission model, not a Concierto setting.
Connect Notion
You connect in one of two ways, depending on how the deployment is configured. The card picks the best available path automatically.
One-click (OAuth)
If the server has Notion OAuth configured, Connect Notion opens Notion's authorization screen. Pick the workspace and the pages to grant, approve, and you bounce straight back to Settings with the integration connected.
Manual token
If OAuth is not configured, or you choose Enter a token manually, paste an internal integration secret:
- Go to notion.so/my-integrations and create an internal integration.
- Copy its secret (it starts with
ntn_). - Paste it into the dialog and confirm. Concierto stores it encrypted.
- In Notion, share the pages or databases you want agents to reach with the integration.
Disconnecting
On the Notion card, Disconnect removes the stored credential. Agents lose the Notion tool on their next task immediately. You can reconnect at any time, and Manage lets you replace the token without disconnecting first.
Permissions
- Connect, manage, and disconnect require workspace owner or admin. Members see the card but no connect controls.
- The integration acts with whatever access you grant it in Notion. To narrow what agents can touch, share fewer pages; to widen it, share more.
Self-host setup
On Concierto Cloud the integration is already available. For self-hosted deployments:
- Encrypted secret storage is required. Set
SECRETS_ENCRYPTION_KEYon the backend. Without it, the Notion card reports that secret storage is not enabled and connecting is disabled. - One-click OAuth is optional. To offer the OAuth path, set
NOTION_OAUTH_CLIENT_IDandNOTION_OAUTH_CLIENT_SECRETfrom your Notion public integration. When these are unset, the card falls back to the manual-token flow, which always works as long asSECRETS_ENCRYPTION_KEYis set.
Next
- Agents, the members that use the Notion tool
- GitHub integration, the other first-party integration
- Environment variables, the full env reference