banana-sync-to-notion

Sync local Markdown files to Notion as nested pages with formatting.

16|2|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/TreyDong/banana-skills --skill banana-sync-to-notion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: banana-sync-to-notion
Source: https://github.com/TreyDong/banana-skills/tree/main/skills/banana-sync-to-notion
Command: npx skills add https://github.com/TreyDong/banana-skills --skill banana-sync-to-notion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Notion users and teams want to keep Markdown notes, docs, and project docs in sync with a Notion workspace while preserving folder structure and Markdown formatting, enabling seamless backup, migration, and collaboration.

Core Features & Use Cases

  • Recursive directory sync that preserves the original file hierarchy as nested Notion pages.
  • Full Markdown support: bold, italic, code, links, tables, and callouts are converted to native Notion blocks.
  • Automatic emoji icons based on filenames to visually organize content.
  • Incremental sync by skipping pages that already exist with the same title to avoid duplicates.
  • Relative link handling to connect inter-file references within Notion pages.
  • Notion API token and root page configuration via a .env file for secure deployments.

Quick Start

Configure a Notion integration by setting NOTION_TOKEN and NOTION_ROOT_PAGE_ID in a .env file, then run npm run sync:notion from the skill directory.

Frequently Asked Questions about banana-sync-to-notion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync local Markdown files to Notion while preserving directory structure?

To sync Markdown to Notion while preserving directory structure, configure a Notion API token and root page ID in a .env file. The sync converts nested local folders into navigable Notion pages, maintaining your original file hierarchy for a structured knowledge base.

Can I migrate Markdown documentation to Notion without losing formatting like tables and callouts?

Yes, migrating Markdown documentation to Notion preserves formatting by converting bold, italic, code, links, tables, and callouts into native Notion blocks. This ensures your documentation retains its original visual structure during the migration process.

Does Notion API sync support incremental updates to avoid duplicating pages?

Notion API sync supports incremental updates by skipping pages that already exist with the same title. This prevents duplicate content during ongoing synchronization of your Markdown files across nested folders and pages.

How are relative links between Markdown files handled when backing up to Notion?

Relative link handling connects inter-file references within Notion pages during the backup process. This ensures that links pointing to other local Markdown files are accurately mapped to their corresponding Notion pages.

What do I need to set up before running a Markdown to Notion sync?

Before running a Markdown to Notion sync, you need to create a Notion integration and configure two environment variables: NOTION_TOKEN and NOTION_ROOT_PAGE_ID in a .env file. After setup, execute the sync command from the skill directory.