Ask questions across your Notion workspace
A chat agent that answers questions from your Notion workspace.
- chat
Act as
- hmacverified
- knowledge-answerer
Daily limit
- knowledge-answerer
- $5.00
- knowledge
answerer-pool
- knowledge-answerer-model
notion
- redact-ssn-from-pagesresponse
What this template gives you
Interface
A chat window, in your browser
Use the included interface to send a request to this template.
Budget
$5.00 per day
knowledge-answerer is capped at $5.00 per day.
Gateway
knowledge gateway
This template sends its requests through knowledge gateway, where its access rules and limits apply.
Model
knowledge-answerer-model
This template uses knowledge-answerer-model through the answerer-pool pool.
Content
redact-ssn-from-pages inspects the notion response
Redact US SSN patterns out of Notion page content
Usage
Hand this template to an AI agent to set up this template
Node.js and npm to run npx.
Dome CLI, installed with brew install dome-systems/tap/dome, then signed in with dome auth login.
Docker Compose to run the companion app locally.
- 1
Create a sandbox workspace
dome sandbox provision --scope workspaceUse a sandbox while trying a template. Provisioning does not switch your active context.
- 2
Switch to the sandbox workspace
dome context sync dome context list dome context use sandbox-<sandbox-name>Replace <sandbox-name> with the sandbox name returned when provisioning it.
- 3
Pull the template
npx @domesystems/templates pull dome-systems/ai-agent-for-notion@0.1.1 --dir ai-agent-for-notionDownloads this immutable release and verifies its digest.
- 4
Run the template
npx @domesystems/templates up --dir ai-agent-for-notionImports it into Dome and starts the companion app.
Dome import variables
npx @domesystems/templates up imports the template into Dome and prompts for required values. For unattended runs, set them as DOME_IMPORT_VAR_… environment variables.
Required values
DOME_IMPORT_VAR_anthropic_api_keyDOME_IMPORT_VAR_actas_hmac_secret
Runtime environment
These variables are required to run the agent. During pull, .env.example is copied to .env when available. If they’re missing, npx @domesystems/templates up retrieves them from Dome and saves them in .env. Pass --provision to refresh them.
# The container holds exactly one secret.
#
# Tool credentials went into Dome when dome import ran and live behind the gateway.
# The provider key lives with the Broker. Neither is here, and neither should be.
# Revealed once after import: dome import outputs <job-id>
DOME_TOKEN=
# The gateway ROOT — not a bare host, and not the /mcp path.
# Copy the "Gateway URL" from the command above. The container derives
# /mcp for tools and /v1/messages for models from it.
DOME_GATEWAY_URL=
# The second secret, and the only one an identity-enabled blueprint adds.
# The container signs the act-as header with it; the gateway verifies the
# signature before it will believe who the request claims to be. Without
# that, anyone holding the agent token could claim to be anyone.
# Must match the actas_hmac_secret supplied to dome import.
ACTAS_HMAC_SECRET=Agent instructions
No agent instructions file is included in this release.