notion skill

[onyx remnant]

i pasted in the notion 'Internal integration secret' and saved it, but agent is saying she doesn't have the .env file

[harsh sapphire]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[rare roost]

OpenClaw doesn’t magically get the Notion “Internal integration secret” just because you pasted it somewhere — it has to be available to the Gateway process as an env var.

What to do:

1. Figure out which env var name the Notion skill expects (common ones are NOTION_API_KEY or NOTION_TOKEN).
   Easiest: run openclaw skills check and it will usually say “missing env var …”.

2. Put it in an env file that OpenClaw actually loads. Per docs, OpenClaw reads env vars from the parent process plus:

   • .env in the current working directory
   • ~/.openclaw/.env as a global fallback
     Source: https://docs.openclaw.ai/gateway/configuration#environment-variables

   So on the gateway host, create/edit:
   ~/.openclaw/.env

   and add a line like:
   NOTION_API_KEY=secret_xxxxx (use whatever key name your skill expects)

3. Restart the gateway (env var changes won’t reliably hot-reload):
   openclaw gateway restart

If it’s still complaining “no .env file”, paste the exact message (especially if it includes a path), plus the output of openclaw skills check — that will tell us whether it’s looking for .env in the wrong folder vs just missing the env var.

[onyx remnant]

Ready to use:
📦 healthcheck
📝 notion
📦 skill-creator
💬 slack
🌤️ weather

[rare roost]

That openclaw skills check output means the Notion skill prompt is installed and eligible — but it doesn’t mean the Notion token is actually available at runtime.

Also: you don’t need a .env file specifically. That’s just one way to provide env vars.

Fix (pick one)

Option A (recommended): global env file

1. On the gateway host, create/edit: ~/.openclaw/.env
2. Add the token using the env var name your skill expects (most commonly):
   • NOTION_API_KEY=secret_... (this is the Notion “Internal integration secret”)
3. Restart the gateway: openclaw gateway restart

Option B: put it in config (no .env file at all)
In ~/.openclaw/openclaw.json add:

{
  env: {
    NOTION_API_KEY: "secret_..."
    // (or equivalently: vars: { NOTION_API_KEY: "secret_..." })
  }
}

Docs on env precedence + the config env block:
https://docs.openclaw.ai/help/environment

Quick sanity check

After doing A or B, ask the agent to run (via exec) something like printenv | rg NOTION or echo $NOTION_API_KEY to confirm the token is actually visible.

If you paste the exact line where the agent complains about “no .env file” (sometimes it includes the path it’s looking in), I can tell you which of the above it expects.

[onyx remnant]

nvm, i guess it just takes a bit to set in