What You'll Build
A workflow that lets you query, update, and create Notion pages or database
entries from natural-language prompts. Generate PRDs, sprint tasks, meeting
notes, or status reports automatically – perfect for individual developers
and cross-functional teams.
What You’ll Learn
This guide teaches you to:- Use natural language to connect to the Notion API directly with Continue CLI for powerful automation
- Configure Notion API access with proper permissions and security
- Run prompts in both TUI (interactive) and headless modes
- Create automated workflows that generate docs, manage tasks, and sync data
Prerequisites
Before starting, ensure you have:- Continue CLI installed (
npm i -g @continuedev/cli) - A Notion workspace with Editor (or higher) access
- Node.js 18+ installed locally
- Continue account with Hub access
Create Notion Integration & Get API Key
- Go to Notion Integrations
- Click + New integration → give it a name (e.g. “Continue Integration”)
- Select your workspace
- Under Content Capabilities, enable:
- ✅ Read content
- ✅ Update content
- ✅ Insert content
- Under Comment Capabilities, enable:
- ✅ Read comments
- ✅ Insert comments
- Under User Capabilities, select:
- ✅ Read user information including email addresses
- Click Submit and copy the Internal Integration Secret (starts with
secret_)
This token is your
NOTION_API_KEY.
Keep it safe – you won’t be able to view it again.- In Notion, open each database or top-level page you want accessible → Share → Invite your new integration → Full access.
Running Continue CLI with Notion API
🚀 Choose Your Interface
Continue CLI offers two powerful modes for Notion automation:
TUI mode for interactive workflows and Headless mode for automated scripts.
- 🖥️ TUI Mode (Interactive)
- 🤖 Headless Mode (Automated)
API Connection Notes
API Connection Notes
- Environment variable
NOTION_API_KEYmust be set before running Continue CLI - Continue automatically uses the API key to authenticate with Notion
- No need for manual curl commands - just reference “the API key stored in this session”
- For complex workflows, Continue maintains the API connection throughout
- Consider creating aliases or scripts for frequently used prompts
Quick Start Example
Working example that demonstrates the power of Continue with Notion API:📊 Weekly Sprint Summary
This exact command has been tested and works:What this does:
- Connects to your Notion workspace using the API key
- Analyzes your sprint data
- Calculates completion metrics
- Creates a comprehensive retrospective with visualizations
Example Prompts & Workflows
With the Notion API configured, you can use natural language prompts to automate your workspace. Here are examples for both TUI and headless modes:API Documentation
TUI Mode:Headless Mode:
Sprint Planning from Code
Headless Mode (Automated):
Changelog from PRs
Daily Standup Automation
Advanced Workflows
Notion + GitHub
Requires GitHub repository access. To add GitHub access, update your integration settings.
Test Coverage Report
Blog Post Review
Weekly Report Generation
Security Best Practices
Next Steps
- Create a GitHub Actions workflow to automate changelog generation on releases
- Build a daily standup bot that runs every morning and posts to Slack
- Set up database templates in Notion for consistent formatting
- Explore batch operations to update multiple pages efficiently
- Implement error handling for API rate limits and network issues
Troubleshooting
Common Issues and Solutions
Common Issues and Solutions
API Key Not Found:
- Ensure
NOTION_API_KEYis exported in your current shell session - Check for typos in the environment variable name
- Verify the key starts with
secret_
- Share the specific database with your integration in Notion
- Ensure the integration has the correct permissions (Read, Write, Insert)
- Verify Continue CLI has internet access
- Check network connectivity to api.notion.com
- Ensure your Notion workspace allows API access
- Notion API has rate limits (3 requests per second)
- Implement exponential backoff for automated scripts
- Consider batching operations when possible