n8n ran. Make completed the scenario. Your AI agent replied. But Obsidian is still empty. Sound familiar?
Webhooks for Obsidian
Any service with HTTP POST → notes in your vault. Use for free or self-host.
In brief
How It Works
Your service
n8n, Make, script or bot — sends an HTTP POST request with content
Our server
Receives content, delivers or stores for up to 30 days
Your Obsidian
Plugin creates a note automatically in the right folder
Your service
n8n, Make, script or bot — sends an HTTP POST request with content
Our server
Receives content, delivers or stores for up to 30 days
Your Obsidian
Plugin creates a note automatically in the right folder
Output
.md Notes in the Right Folder
Details
Why It's Reliable
No Duplicates
Plugin confirms receipt of each note. Network glitch? Redelivery won't create a duplicate.
Your Data is Yours
Transfer over HTTPS. Delivery queue encrypted with AES-256. After delivery is confirmed — data is deleted from the server.
Auto-Reconnect
Lost internet? Plugin restores the connection and picks up everything accumulated while offline.
Self-Host in 2 Commands
Docker-compose, Supabase. All code on GitHub. Don't want to depend on our server — deploy your own.
FAQ
Questions & Answers
Does Telegram work?
Not directly. Telegram doesn't send webhooks to arbitrary URLs. You need a bot (a simple Python script) or an n8n/Make scenario that forwards messages to our server. Ready-made example on the «How It Works» page.
Are there limits?
One webhook — up to 10 MB of text. Data is stored on the server for up to 30 days. Text only: Markdown, plain text, JSON. No images or PDFs.
Where is data stored?
On the server — only the delivery queue (text + metadata). After delivery is confirmed by the plugin — data is deleted. Your vault contents are never stored on the server. Hosted version: server in Germany, database on Supabase (EU). Self-host: wherever you deploy.
Can I connect multiple vaults?
Yes. Create a separate key pair for each vault — each one gets its own webhook URL and delivery stream. You can also use multiple keys to separate different services: if one key is compromised, revoke only that one.
What data do you collect?
Landing page: anonymous pageviews via Umami (self-hosted). No session recording, no personal data. Server: your email (for authentication), webhook delivery queue (encrypted AES-256, deleted after delivery confirmed). Plugin: collects nothing. Zero analytics, zero telemetry. We don't sell data. All code is open source — verify yourself.
Is this related to obsidian-webhooks by @trashhalo?
Yes. This project was inspired by obsidian-webhooks by @trashhalo — the original proof of concept that showed webhooks + Obsidian is a great idea. We rebuilt it from scratch as a full self-hosted solution with encryption, authentication, exactly-once delivery, and a managed hosting option.
Stop Copying Manually
Set up your source once — the plugin creates notes in your vault from there. Open source. Use for free on our server or self-host your own.
→ Get API Keys