---
# System prepended metadata

title: Clawdbot Self Summary

---

#    Tools and Scripts I Have Access To + Work Summary

## Available Tools
#### Notion Integration
• *add_notion_env.sh*: Script to set up Notion environment variables
• *get_notion_db.py*: Fetch data from Notion databases
• *check_notion_query.py*: Test and validate Notion queries
• *debug_notion*.py*: Multiple debug scripts for Notion API integration
• *final_notion_test.py*: Test creating entries in Notion with correct schema
#### Research Automation
• *start_research_*.py*: Various scripts to initiate research tasks
• *process_queue_fixed.py*: Process jobs in a research queue
• *notify_research_complete.py*: Alert when research is complete
#### MCP (Model Context Protocol) Tools
• *mcporter*: CLI for interacting with various API services  
• Linear integration (187 tools)
• GitHub integration (26 tools)
• Search capabilities
#### Browser and Node Tools
• Clawdbot browser control
• Node canvas capabilities
• Nodes discovery and control
## Work Completed
#### Template Architecture Implementation
• Created Linear issue UC-55 documenting the template architecture recommendation
• Detailed a hybrid approach combining independent repositories (from templates) with Vercel deployment
• Outlined advantages including campaign isolation, simplified automation, and clean development environment
#### Vercel Deployment Configuration (UC-37)
• Updated Linear issue with comprehensive deployment instructions
• Added detailed comments explaining shared subdomain implementation
• Described how to set up Vercel to ensure all campaign sites appear under the correct slug
• Configured GitHub CI/CD pipeline integration
• Provided technical implementation details for vercel.json and next.config.js
## Documentation and Summaries
• Summarized the Clawdbot Automated Marketing Flow from Notion
• Documented the three-phase process:  1. Development & Deployment (PM → PRD → Clawdbot → GitHub → Vercel)
  2. Marketing & Acquisition (Ads → Campaign site)
  3. User Journey (Visit site → Complete quiz → Download app → Sync data)
## Technical Implementation Notes
• Explained repository architecture (independent repos from templates)
• Detailed deployment strategy (shared domain with unique paths)
• Documented automation benefits (time savings, consistency)
• Created configuration guides for Next.js and Vercel settings
## Current Focus Areas
• Streamlining the automation process between Notion PRDs and GitHub templates
• Ensuring reliable deployment to Vercel with proper domain configuration
• Creating a seamless end-to-end flow from marketing campaign conception to user acquisition