Drop Files, Auto-Import —
Inbox Folder Integration

Not every note starts inside an app. Meeting transcripts land in Downloads. Scripts generate reports. CI pipelines spit out logs. Claspt's Inbox folder lets you drop any .md file into a watched directory and have it appear in your vault — indexed, encrypted, and version-tracked — without writing a single line of code.

How It Works

Every Claspt vault includes a watched inbox directory at ~/Claspt/.inbox/. The moment a .md file appears in that folder, Claspt picks it up and processes it:

1. Detection. Claspt watches the .inbox/ directory for new files using native filesystem events — no polling, no delays.
2. Import. The file is read, parsed, and moved into your vault's folder structure.
3. Indexing. The content is added to the full-text search engine (tantivy) so it's instantly searchable.
4. Version tracking. The import is auto-committed to Git with a descriptive commit message.
5. Cleanup. The original file is removed from .inbox/ after successful ingestion.

That's it. No API tokens, no CLI flags, no configuration. Drop a file, and it's in your vault.

Smart Routing with YAML Frontmatter

By default, imported files land in a general "Inbox" folder inside your vault. But you can control exactly where they go by adding YAML frontmatter to the dropped file:

---
title: Staging Deploy Report
folder: Work/DevOps/Reports
tags: [deploy, staging, march-2026]
---

# Staging Deploy Report

Deployed commit a3f7c2d to staging at 14:32 UTC.
All health checks passed.

Claspt reads the frontmatter, creates the folder if it doesn't exist, applies the tags, and uses the title for the page name. Without frontmatter, the filename becomes the title and the file goes straight to Inbox.

Automatic Secret Encryption

If a dropped file contains Claspt secret blocks, they are automatically encrypted on ingestion using the same AES-256-GCM encryption as any other page. This means you can generate files with secret syntax from external tools and have them encrypted the moment they hit the inbox.

---
title: Rotated API Keys
folder: Credentials/Production
tags: [api-keys, rotation, automated]
---

# Rotated API Keys

Last rotation: March 4, 2026.

:::secret template="api-key" label="Stripe Live Key"
service: Stripe
key: sk_live_new_rotated_value_here
:::

The plaintext secret block is encrypted before it touches disk in the vault. The original file in .inbox/ is securely deleted after import. At no point does an unencrypted secret persist in your vault directory.

Works with Automation Tools

The inbox folder is a plain directory on your filesystem. Any tool that can write a file can feed your vault. Here are some common setups:

Hazel (macOS)

Set up a Hazel rule to watch your Downloads folder for .md files matching a naming pattern and move them to ~/Claspt/.inbox/. Notes from other apps, exported documents, and meeting transcripts flow into your vault automatically.

Watchman or fswatch

# Watch a shared directory and copy .md files to Claspt inbox
fswatch -0 ~/Dropbox/shared-notes/ | while read -d "" file; do
  [[ "$file" == *.md ]] && cp "$file" ~/Claspt/.inbox/
done

Cron Jobs

# Every hour, generate a status report in the vault
0 * * * * /usr/local/bin/generate-status-report.sh \
  > ~/Claspt/.inbox/server-status.md

Drag and Drop

The simplest approach — open Finder, drag a .md file into ~/Claspt/.inbox/, and it appears in your vault within seconds.

Use Cases

Capture Notes from Other Apps

Export from Bear, iA Writer, Notion, or any markdown-capable app. Drop the .md export into the inbox folder. Your notes are now encrypted, version-tracked, and searchable inside Claspt.

Automated Credential Rotation

#!/bin/bash
# Rotate an API key and drop it
# into the vault via inbox folder

NEW_KEY="$(openssl rand -hex 32)"
TODAY="$(date +%F)"

# Copy template and inject new key
cp template.md ~/Claspt/.inbox/rotation.md
sed -i "s/PLACEHOLDER/$NEW_KEY/" \
  ~/Claspt/.inbox/rotation.md

echo "Key rotated and stored in vault"

The script writes a file with a secret block. Claspt picks it up, encrypts the secret, indexes the page, and commits to Git — all without the script needing to know anything about Claspt's API or CLI.

CI/CD Pipeline Outputs

Configure your CI pipeline to write build reports, test results, or deploy logs as .md files to the inbox directory on a shared machine. Every build artifact becomes a searchable, versioned vault page.

# In your CI pipeline's post-deploy step
# Generate a deploy report as markdown
# and drop it into the vault inbox

./scripts/generate-deploy-report.sh \
  --commit abc123 \
  --branch main \
  --env production \
  --output ~/Claspt/.inbox/deploy-abc123.md

# Claspt auto-imports, indexes, and
# version-tracks the deploy report

Combine with Other Integrations

The inbox folder is one of four integration surfaces in Claspt, alongside the local HTTP API, the CLI tool, and the MCP Server. They all work together:

• CLI writes to inbox. Use claspt commands in scripts that also drop files into .inbox/ for bulk imports.
• Scripts drop files. Automation scripts that don't need the CLI's precision can write raw .md files to the inbox for simple fire-and-forget ingestion.
• AI tools generate notes. Claude, Cursor, or Windsurf can generate markdown files via the MCP Server, or you can have them write directly to the inbox folder.

The inbox folder is the lowest-friction integration point. No authentication, no API tokens, no HTTP requests — just a file in a directory.

Free Across All Tiers

The inbox folder, like the API, CLI, and MCP Server, is included in every Claspt plan — including the free tier. There are no subscription gates on developer tooling. Download Claspt, and every integration surface is available from day one.