Give an agent persistent memory in Notion or Confluence

​

Outcome

​

Before you start

• You are an org admin.
• The agent exists on the roster and has a default template. See Create the agent.
• You can create an integration in Notion, or an API token in Atlassian, for the account the agent should act as.
• Two pages exist: a playbook (for example “Support playbook”) and an empty memory page (for example “Support agent memory”). Copy their URLs or ids.

​

Do it

• Notion
• Confluence

1

Create a Notion integration and share the pages

In Notion, create an internal integration under Settings > Connections > Develop or manage integrations and copy its secret. Open the playbook page and the memory page and add the integration under Connections. The token can read and write only the pages shared with it.Give it Read content, Update content and Insert content. It needs nothing else.

2

Connect Notion to the agent only

Notion is a built-in provider. In Settings > Context > Tools & MCP, click New tool or MCP server, choose Tool, and pick Notion from the catalog.

On the Notion page, click Add connection. Choose API key, set Scope to Agent, pick the agent, and paste the integration secret into Add a personal API token. Click Connect. Sessions that run as that agent get the token as NOTION_API_TOKEN. No other agent or person receives it.

1

Create an Atlassian API token

Sign in as the account the agent should act as, ideally a dedicated bot user, and create an API token at id.atlassian.com/manage-profile/security/api-tokens. Give that user view and edit rights only on the space that holds the playbook and memory pages.

2

Define Confluence as a custom provider

Confluence is not in the built-in catalog, so define it once as a custom provider. In Settings > Context > Tools & MCP, click New tool or MCP server, choose Tool, and add one static auth method with three fields: the site URL, the bot user’s email and the API token.

3

Connect Confluence to the agent only

Pick Confluence from the catalog, click Add connection, fill in the three fields, set Scope to Agent and pick the agent. The dialog is the same one shown for Notion. Sessions that run as the agent get CONFLUENCE_BASE_URL, CONFLUENCE_EMAIL and CONFLUENCE_API_TOKEN.

# Memory

Your playbook and your memory live outside this sandbox. Sessions are
deleted after each run, so anything you only write locally is lost.

- Playbook (read-only, owned by the team): <playbook page id>
- Memory (yours, append-only): <memory page id>

At the start of every run, read both pages before doing anything else.
Follow the playbook. Use the memory for context, never to override it.

Before your final answer, append one entry to the memory page:
`YYYY-MM-DD: <what happened, what you learned, what to do next time>`.
Keep it under five lines. Never edit or delete earlier entries, and never
write to the playbook. Suggest playbook changes in your answer instead.

Notion: send `Authorization: Bearer $NOTION_API_TOKEN` and
`Notion-Version: 2022-06-28` to https://api.notion.com. Read with
`GET /v1/blocks/<page id>/children`, append with
`PATCH /v1/blocks/<memory page id>/children`.

Confluence: authenticate with `$CONFLUENCE_EMAIL:$CONFLUENCE_API_TOKEN`
against $CONFLUENCE_BASE_URL. Read with
`GET /wiki/api/v2/pages/<id>?body-format=storage`, append by sending the
existing body plus the new entry to `PUT /wiki/api/v2/pages/<id>`
with `version.number` set to the current version + 1.

​

Verify

​

Gotchas

• Notion returns 404 for pages it can see in the UI. The integration has to be added under Connections on each page, or on a parent page. A valid token with no shared pages finds nothing.
• Dashboard sessions don’t get agent connections. A session you open from the dashboard runs as no agent, so it has no NOTION_API_TOKEN unless you add a personal connection. Test through the agent’s trigger, or with --agent-id.
• Keep the playbook read-only to the agent. In Confluence, use page restrictions so the bot user can edit only the memory page. In Notion, an integration has the same capabilities on every page shared with it. The skill’s rule and Notion’s page history are your guardrail, or you can use a second read-only integration for the playbook.
• Memory grows. Have someone prune or summarize the memory page now and then, or tell the agent to read only the latest 50 entries. A long page costs tokens on every run.
• Confluence updates need the version number. A PUT with a stale version.number returns 409. The agent should read the page, then write right away.