First Integrations

Module 5: First Integrations

Your vault is a good knowledge base. But a co-operating system needs to know what’s happening in your world — not just what you’ve written about it.

This module connects two external data sources to your vault: email and calendar. When Claude can see your commitments and your incoming information, the answers it gives you become much more useful.

The Integration Mindset

The goal is to pull information into the vault — not to scatter it across multiple apps and try to bridge them at query time.

When you ask Claude “What do I need to prepare for this week?”, you want it reading your actual calendar entries and flagging action items from relevant emails. That only works if those things are in the vault when Claude reads it.

The other principle: don’t over-integrate. You don’t need every email in your vault. You need the ones that contain tasks, decisions, or context relevant to your projects. A fire hose of raw email creates noise, not signal.

Start with one integration. Get it working. See how it feels. Add the next one only when you’re clear it will help.

Email to Inbox

You want action-worthy emails to land in your vault automatically. There are a few ways to do this:

The simple approach — create a shortcut or keyboard macro that lets you forward any email to a new inbox note. Manual, but instant, and zero setup. If an email needs action, you forward the content to your vault immediately.

Automation tools — Zapier, Make, and n8n can all watch your email and create vault notes when certain conditions are met. A popular pattern: tag an email “To Vault” in Gmail, and an automation creates an inbox note with the subject line, sender, and body. Setup takes an hour. After that it’s invisible.

n8n specifically — if you’re already running n8n (or willing to), it has native Obsidian support. You can build a flow that monitors an email label and creates structured notes with exactly the fields you want.

Choose the approach that matches your technical comfort level. The manual shortcut approach is perfectly valid — the important thing is having a method, not having the most automated one.

Calendar Awareness

Your calendar is one of the most useful things Claude can know about. When it knows your commitments, it can tell you what to prepare, flag conflicts, and help you plan realistically instead of optimistically.

The simplest integration: create a weekly “Calendar Note” each Monday. Open your calendar, copy the week’s events into a note in your vault (02 Projects/Week of 2026-03-23 works well), and Claude can reference it for the whole week.

A more automated approach: if you use Fantastical or BusyCal on Mac, you can use AppleScript to export your day’s events to a vault note automatically. Claude Code can even run this script for you — ask it to “create today’s schedule note from my calendar.”

The goal isn’t a perfect sync — it’s Claude having enough context to be useful when you ask about your time.

Try this prompt once your calendar note is in place:

“Based on my schedule this week, what should I prepare for and when?”

Claude will read your calendar note and your project notes and give you a grounded plan. That’s the integration paying off.

Before moving on:

• At least one integration connected (email or calendar)
• One piece of external data has landed in your vault automatically or manually
• Claude has answered a question using that external data

---

This module evolves as your system does.