Obsidian is a manual tool by default. You open it, create a file, write in it. That’s fine for personal note-taking. For an operator who wants to capture structured notes from multiple sources automatically — research inputs, reader questions, content ideas — the manual workflow doesn’t scale.

Connecting Claude and Make to Obsidian’s file system turns it into a destination for structured AI-generated notes. The inputs can come from anywhere: a form submission, a Telegram message, an RSS feed, a weekly research prompt. The output is a properly formatted Obsidian note waiting in your vault.

Quick Answer: Make can write files to Obsidian via the filesystem (if your vault is synced to a location Make can reach — Dropbox, Google Drive, or a server path). Claude generates structured note content from your inputs. The pipeline: trigger event → Make sends input to Claude API → Claude returns structured markdown → Make writes the file to your vault location. Total setup time: 1–2 hours.

How the integration works

Obsidian doesn’t have a native API that external tools can call. What it has is a folder — your vault — that syncs via Obsidian Sync, Dropbox, Google Drive, or a local path.

The integration strategy: write .md files directly to the vault folder. When the file appears in the watched folder, Obsidian picks it up immediately (or on the next sync). No plugin required for the write operation.

For this to work, your vault needs to be in a location Make can write to:

  • Dropbox or Google Drive: Make has native integrations. Write a file to the synced folder → Obsidian picks it up when the sync runs.
  • Local vault only (no sync): You’d need a server or script that Make can reach, which adds complexity. Easier to use Dropbox or Google Drive sync for this integration.

Building the Make workflow

Trigger

Choose the trigger that matches your use case:

  • Webhook: Triggered by a form, Telegram message, or any system that can send a POST request
  • Schedule: Runs at a fixed time (e.g., every morning, generate a daily research brief)
  • RSS/Feed: Triggered by new items in an RSS feed you’re monitoring
  • Gmail/Email: Triggered by specific emails matching a filter

Claude API call

Add an HTTP module in Make. Configure it as a POST request to the Anthropic API:

URL: https://api.anthropic.com/v1/messages
Method: POST
Headers:
  x-api-key: [your Anthropic API key from Make's secrets]
  anthropic-version: 2023-06-01
  content-type: application/json
Body:
{
  "model": "claude-haiku-4-5-20251001",
  "max_tokens": 1024,
  "messages": [
    {
      "role": "user",
      "content": "Create a structured Obsidian note from the following input. Include: a title (using # heading), a date field, a summary section, key points as bullets, and a tags field at the bottom.\n\nInput: {{trigger_data}}"
    }
  ]
}

Replace {{trigger_data}} with the relevant field from your trigger (the form submission text, the article summary, the email body).

Claude Haiku is sufficient for note generation — fast, cheap, and accurate enough for structured markdown output. Reserve Sonnet or Opus for tasks requiring deeper reasoning.

Write to Obsidian vault

Add a Dropbox “Create/Update a File” module (or Google Drive “Upload a File” module):

  • File path: /Obsidian/[your vault]/Inbox/{{date_formatted}}-{{slug}}.md
  • File content: The content field from the Claude API response (the text value from the response JSON)

Use Make’s date/time formatting to generate the filename: {{now; format: YYYY-MM-DD}}-note.md creates a daily-stamped note.

The file lands in an Inbox folder in your vault. From there, you process it manually in Obsidian — add links, move to the right folder, extend with your own notes.

Practical automation templates

Daily research brief

Trigger: Schedule — every morning at 7:00 AM Input: A fixed list of topics you want Claude to summarize: “Latest developments in AI agent frameworks, OpenRouter updates, content automation tools” Output: A daily note titled YYYY-MM-DD Research Brief.md with a structured summary of each topic

Useful for operators who want to start each day with a briefing on their niche without manually searching.

Reader question capture

Trigger: Webhook from a Typeform or Tally form Input: The reader’s question and their email address Output: An Obsidian note with the question, a suggested answer outline from Claude, and a tag for #reader-questions

Useful for capturing audience questions and preparing content responses in batches.

Content idea from RSS

Trigger: New item in an RSS feed from industry publications Input: Article title and summary Output: Obsidian note with: article title, link, 3-bullet summary, and a “Content angle” section where Claude suggests how this could inspire a blog post

Useful for content operators who want a passive stream of curated research notes from sources they trust.

Handling the Obsidian sync delay

If your vault syncs via Dropbox or Google Drive, there’s a short delay (usually under 60 seconds) between Make writing the file and Obsidian seeing it. This is acceptable for all async workflows.

If you’re using Obsidian Sync (Obsidian’s own paid sync service), Make can’t write to it directly — Obsidian Sync uses proprietary encryption. Use Dropbox or Google Drive instead.

Keeping the vault organized

Automated notes land in an Inbox folder. Process them weekly:

  • Read each note
  • Add internal links to related notes
  • Move to the appropriate folder
  • Delete if not useful

The inbox folder is the buffer. The processing step is where human judgment adds the context that automation can’t — which notes are actually worth keeping and how they connect to your existing knowledge.

For the broader Obsidian + Claude workflow, see how to build a personal knowledge system with Obsidian and Claude. For automation platform comparison, the n8n vs Make guide covers when to use each. The Make program page covers affiliate details.

Frequently Asked Questions

Can I use n8n instead of Make for this workflow? Yes — n8n supports all the same integration points. The workflow design is identical; the interface differs. If you’re already on n8n, build this there. If you don’t have a preference, Make is easier for this specific workflow.

Do I need the Obsidian API plugin? No — the Local REST API plugin exists for some integrations, but it requires Obsidian to be running and accessible. The file-write approach via Dropbox/Google Drive is simpler and more reliable for fully automated workflows.

What file format should automated notes use? Standard Obsidian markdown with YAML frontmatter. Include at minimum: date, tags, and source fields in the frontmatter. This makes notes searchable and filterable with Dataview.

Can Make overwrite an existing note? Yes — if you use the same filename, Make will overwrite the existing file. Use date-and-timestamp-based filenames to avoid accidental overwrites: YYYY-MM-DD-HHmm-topic.md.

Build your Obsidian automation system

If you’re exploring Obsidian for structured knowledge management alongside automation tools, the Obsidian tool page covers setup decisions and the automation integration options worth knowing about.