Notion Context

Notion Context Skill

Gather business context from Notion using SignalPilot's governed Notion tools.

1. Discover Integrations

Call list_notion_integrations. If none exist, skip — Notion context is optional. Do not block the workflow.

Note which integration has a report destination configured — the verify agent will write there. If multiple have report destinations, use the first. If none have one, the verify agent will fall back to a local file.

2. Search All Integrations

Extract keywords from the task instruction — table names, metric names, business terms not defined in YML.

For each integration, search:

notion_search
  integration_name: "<name>"
  query: "<keywords>"

Merge results from all integrations. Track which integration each result came from — you'll need it for fetch calls.

No results across any integration? Try in order:

1. Broader keywords ("daily shop orders" -> "orders")
2. Synonyms ("revenue" -> "sales")
3. Individual terms

If still nothing -> write the context file with No relevant Notion context found. and return.

3. Fetch and Navigate

For each matching page (up to 5 total across all integrations):

notion_fetch_page
  integration_name: "<integration that owns this page>"
  page_id: "<id>"

If the page lists child pages but has no content — it's a container page. Fetch the child pages that look relevant to the task (by title). Meeting notes and transcripts are typically one level down from the container.

If the page has content — extract from it directly.

4. Extract and Tag Context

Scan page content for three categories:

For each item, tag its relevance to the current task:

Discard items with no connection to the task.

For each kept item record:

• Verbatim excerpt (under 200 chars) or paraphrase
• Source page title, ID, and integration name
• Category (DEFINITION / DECISION / CONSTRAINT)
• Relevance (DIRECT / RELATED)

Check for contradictions between items. If two sources disagree, flag both with CONFLICT:. Do NOT silently pick one.

5. Write Context File

Write notion_context.md in the working directory:

# NOTION CONTEXT
# Report Integration: <integration with report destination configured>
# Task: <task summary>
# Sources: <N> pages searched across <M> integrations, <K> items extracted

## DEFINITIONS
- [DEF-1] [DIRECT] "<term>" = <definition>
  Source: <page_title> — https://notion.so/<page_id> (via <integration_name>)

## DECISIONS
- [DEC-1] [DIRECT] <decision statement>
  Source: <page_title> — https://notion.so/<page_id> (via <integration_name>)
- [DEC-2] [RELATED] <decision statement>
  Source: <page_title> — https://notion.so/<page_id> (via <integration_name>)

## CONSTRAINTS
- [CON-1] [DIRECT] <constraint>
  Source: <page_title> — https://notion.so/<page_id> (via <integration_name>)

## CONFLICTS
- <item A> (from <page_A> via <integration_A>) vs <item B> (from <page_B> via <integration_B>)

## SOURCES CONSULTED
- <integration_name>: <page_title> — https://notion.so/<page_id> — <N> items

The # Report Integration: line tells the verify agent where to write the report. Each item tracks which integration it came from.

6. Return to Agent

Return DEFINITIONS, DECISIONS, and CONSTRAINTS to the calling agent. The agent MUST:

• Apply DIRECT items when making grain, join, filter, and column decisions
• Note RELATED items as supporting context
• Write -- NOTION: [DEF-1] <brief reason> comments in SQL for every decision influenced by Notion context. Use the item ID from the context file.
• Flag CONFLICT items and explain which side was chosen

Rules

• NEVER fabricate context. No Notion source = no context item.
• NEVER block the workflow on missing context. It's supplementary.
• NEVER silently resolve conflicts. Flag them.
• Search ALL integrations, not just one.