Obsidian × Shortcuts troubleshooting

Your Shortcut isn't writing to Obsidian

Most of the time this isn't a bug — it's that two different routes exist and they fail in different places. Obsidian on iPhone offers built-in Shortcuts actions and the older obsidian:// URL scheme. Identify which one you're on first, then jump to your symptom.

By AI ATAKA · Published

SHORT ANSWER

There are two routes. (1) Obsidian's built-in Shortcuts actions (mobile 1.11 and later; can append to a note without opening the app), and (2) the obsidian:// URL scheme (called via "Open URL"; brings Obsidian to the foreground). Truncated text, unexpected new notes and wrong-vault writes are almost always route 2 — URL construction problems. "The action doesn't appear" is route 1, usually just an outdated Obsidian. And "it fails from Apple Watch" can't be fixed on either route, because Obsidian has no watchOS app.

Step one: which route are you on?

Open your shortcut and look at the actions inside. An action carrying the Obsidian icon means route 1; an "Open URL" action holding a obsidian://… string means route 2. Most tutorials online predate 1.11 and describe route 2, which is why the steps you find often don't match what you see on screen.

Aspect 1. Built-in actions 2. obsidian:// URL scheme
How it's called Search "Obsidian" in the action picker Pass obsidian://new?... to "Open URL"
Version needed Obsidian mobile 1.11+ (public release Jan 2026) Available in older versions too
Does the app open? Capture actions write without opening it Obsidian comes to the foreground
Choosing the target Pick it in the action's fields You write the path into the URL yourself
Truncation / mangling Rare — no URL in the path Common, from missing encoding
From Apple Watch Not possible Not possible
CHECK THIS FIRST

If the built-in actions are missing, an outdated Obsidian is usually the whole story. Update it in the App Store, then launch Obsidian once and open your vault. This single step resolves the most common case on this page.

JUMP TO YOUR SYMPTOM
  1. No Obsidian actions in the Shortcuts app
  2. Obsidian opens in the foreground every time
  3. The note body gets cut off or mangled
  4. A new note appears instead of an append
  5. It lands somewhere other than the daily note
  6. Wrong vault, or the vault isn't found
  7. It fails when run from Apple Watch
  8. Fails offline, or won't run while locked

Fixes by symptom

ROUTE 1 · BUILT-IN ACTIONS

No Obsidian actions show up in the Shortcuts app

CauseBuilt-in Shortcuts actions arrived in Obsidian mobile 1.11 (early access December 2025, public January 2026). Older builds simply don't have them. Right after an install or update, iOS can also take a little while to register an app's actions.

Fix

  1. Update Obsidian to the latest version in the App Store.
  2. Launch Obsidian once and open your vault.
  3. Reopen the Shortcuts app and search "Obsidian" in the action picker.
  4. Still nothing? Fall back to route 2 — an "Open URL" action holding obsidian://.
ROUTE 2 · URL SCHEME

Obsidian opens in the foreground every time

CauseThis is by design, not a bug. obsidian:// works by launching Obsidian and handing it the URL to process, so the app has to come forward. "Append without opening" is not achievable through the URL scheme at all. Tutorials that say "Obsidian flashes open, just ignore it" are accepting that constraint.

FixIf you don't want the app to surface, switch to route 1's capture actions. Since 1.11 they append to a note without bringing Obsidian forward — decisive if you want this to run while the phone is locked or in your pocket. Note that route 1's "open note" style actions still open the app, since displaying it is the point.

ROUTE 2 · URL SCHEME

The note body gets cut off or mangled

CauseYour text is embedded in a URL, so URL delimiters are being interpreted as delimiters. # means "fragment starts here", so everything after it is discarded. & starts a new parameter, and + can decode to a space. Any Markdown heading (## Heading) or tag (#idea) triggers it — which is why short notes seem fine and longer ones break.

Fix

  1. Insert a "URL Encode" action on the body text before it goes into the URL.
  2. Encode the vault name and file name too if they contain spaces or non-ASCII characters.
  3. If you write tags and headings routinely, move to route 1, where this class of bug can't occur.
ROUTE 2 · URL SCHEME

A new note appears instead of an append

Causeobsidian://new creates a note — that's its job. Appending to an existing note only happens when you say so explicitly. Without that, a same-named note can be duplicated under a new name or have its contents replaced. "It worked yesterday but made a new file today" usually just means the date rolled over and the target note no longer existed.

FixAdd the parameter that requests an append. Confirm the exact parameter name — and what happens when the target note doesn't exist — in the official Obsidian URI documentation, since this has varied across versions. On route 1 you just pick append or prepend in the action's settings; there's no URL to build.

BOTH ROUTES

It lands somewhere other than the daily note

CauseIf you've customised the daily note's date format (default YYYY-MM-DD) or its folder, the path your shortcut builds won't match. The classic case: Obsidian expects Journal/2026-08-11.md while the shortcut creates 2026-08-11.md at the vault root. Nothing errors — you just get the hardest failure to notice: it wrote successfully, somewhere you aren't looking.

Fix

  1. Check Settings → Daily notes for the date format and the new file location.
  2. Match your shortcut's date format to it exactly.
  3. If a folder is configured, pass the full path including the folder, not just the file name.
  4. Search the vault for stray same-named notes created in the wrong place.

The full daily-note setup is covered in appending to your Obsidian daily note without opening your iPhone.

ROUTE 2 · URL SCHEME

Wrong vault, or the vault isn't found

CauseWith more than one vault and no vault specified, the target becomes whichever vault was open last. Even if you normally use one, opening a test vault once is enough to switch it. And if the vault name contains spaces or non-ASCII characters and isn't encoded, resolution fails outright.

FixAlways name the vault explicitly in the URL, and URL-encode that value as well. If you ever rename a vault, remember to update the shortcut — this is a classic silent breakage.

BOTH ROUTES · NOT FIXABLE IN SETTINGS

It fails when run from Apple Watch

CauseObsidian has no watchOS app. Neither the app nor your vault files exist on the watch. A shortcut running on the watch can't invoke actions from an app that isn't installed there, nor open a URL scheme aimed at it — so it fails even with your iPhone right next to you. This is structural, not a setting.

FixThere is currently no way to write to Obsidian from the watch alone. The workable path is an app that ships a watch app and does the vault write on the iPhone side. The reasoning and the alternatives are compared in why you can't send to Obsidian from Apple Watch.

BOTH ROUTES

Fails offline, or won't run while locked

CauseTwo separate problems that look alike. Failing offline usually means the vault's files aren't actually on the device — only in the cloud. Failing while locked is route 2 needing to bring the app forward, which a locked device won't complete.

Fix

  1. Keep the vault in iCloud Drive or On My iPhone so the files exist locally.
  2. To run reliably while locked, use a route that completes without foregrounding an app — route 1's append actions, or a capture app built on App Intents.
  3. Add a notification or sound at the end of the shortcut so failures don't pass unnoticed.

Three limits neither route removes

The fixes above resolve most cases. But "send to Obsidian via a Shortcut" carries three weaknesses no setting removes. Decide knowingly whether to live with them or change the design.

⌚ Nothing from the wrist
With no watchOS app, the watch can't be an entry point. Ideas that arrive while walking or cooking don't get captured on this route.
🔇 Failures are silent
A wrong path or missing encoding rarely raises an error. You find out that a note vanished weeks later, when you go looking for it.
📁 The vault must be on the device
The write target is a local file. A device without the vault — or one whose sync hasn't caught up — can't be written to.
🧰 You own the repairs
Renaming a vault, reshuffling folders, an OS update — each can break the shortcut quietly. What you build, you maintain.

A different design: let an app own the delivery

If those limits matter to you, there's an alternative: stop hand-building the delivery and make it the app's job. Simple Memo sends each note to your own inbox by email and, at the same time, appends it to your vault folder in iCloud Drive as - HH:mm note. No community plugin, no shortcut to maintain.

⌚ Capture from Apple Watch
Speak into the watch app and the paired iPhone performs the vault write. The watch never writes to the vault itself.
🗣️ Voice-only capture
"Hey Siri, save with Simple Memo" completes without looking at the screen. It runs through App Intents, so the app stays in the background.
📬 A second copy in your inbox
Even if the vault write isn't what you expected, the same text is in your email. Silent loss becomes structurally unlikely.
✈️ Offline-safe
The vault append is local, so it works with no signal. The email waits in an encrypted outbox and sends itself when you're back online.
TO BE PRECISE

This is not an official Obsidian app or plugin; it's an independent app built by Yurica Inc. The target must be a vault folder in iCloud Drive or On My iPhone, reachable from the Files app. Vaults that live only in Obsidian Sync may not appear in the folder picker, in which case the app falls back to the URL scheme. Obsidian is a trademark of Dynalist Inc.

Get out of the shortcut-maintenance business

Free to download. Obsidian setup takes about a minute — you pick the folder once.

Download on the App Store

FAQ

Should I use the built-in actions or the URL scheme?
If you can run 1.11 or later, prefer the built-in actions. Removing the URL construction step structurally eliminates the three most common failures: truncated bodies, wrong vaults and mismatched paths. The URL scheme still earns its place for operations the built-in actions don't cover, or on older versions.
Can I just tell Siri to note something in Obsidian?
Obsidian 1.11 added Siri-triggered capture, so supported phrases work. If Siri doesn't respond, first check that Siri is enabled for that shortcut in the Shortcuts app. Be aware that phrasing like "note this in…" is easily interpreted as a command for the built-in Notes app and can land somewhere you didn't intend.
How do I know for sure whether a shortcut failed?
Adding a "Show Notification" action at the end is the simplest option, but it only tells you the shortcut ran to completion. A write to the wrong path still reports success, so periodically search the vault for notes appearing where you didn't expect. An app whose destination is fixed by configuration removes the need for that audit entirely.
My automation keeps asking for confirmation
Automations have a setting for whether to ask before running. When it's on, every run needs a tap. Whether you can turn it off depends on the trigger type, so choose a trigger that permits unattended runs, such as a time of day or start of charging. Note that anything requiring the app to come forward still won't complete while locked, even with confirmation disabled.
Does Simple Memo need me to build a shortcut?
No. Turn on Obsidian integration in the app's settings, pick your vault folder once, and every note you send is appended to your daily note or a fixed inbox note from then on. No URL to assemble, no date format to match, no vault name to specify. The Obsidian integration page walks through the setup.

Related pages

Obsidian integration Append to your daily note Why Apple Watch can't send Voice notes with Siri Apple Watch × Obsidian 6 ways to send to Obsidian Compared with iOS Shortcuts FAQ

References

Related content