Obsidian Web Clipper Share Template

General
1

Anyone who uses Obsidian, I created a JSON template for the Obsidian Web Clipper specifically for extracting and documenting content from a shared Pocket transcript URL. There’s definitely room for improvement here (preserving MD formatting), but I figured I’d share. This should be a quick and easy solution until there’s an API, plugin, or direct integration with Obsidian!

This variation is best used with the Summary tab selected of the share webview.

{
	"schemaVersion": "0.1.0",
	"name": "Pocket Transcript",
	"behavior": "create",
	"noteContentFormat": "---\n{{selector:div.summary-markdown}}",
	"properties": [
		{
			"name": "date",
			"value": "{{date|date:\\\"YYYY-MM-DD\\\"}}",
			"type": "date"
		},
		{
			"name": "description",
			"value": "{{selector:p.desktop-recording-description}}",
			"type": "text"
		},
		{
			"name": "tags",
			"value": "transcript/pocket",
			"type": "multitext"
		},
		{
			"name": "source",
			"value": "{{url}}",
			"type": "multitext"
		},
		{
			"name": "speakers",
			"value": "",
			"type": "multitext"
		}	
],
	"triggers": [
		"https://share.heypocket.com/"
	],
	"noteNameFormat": "{{date|date:\"YYYY-MM-DD\"}} {{selector:h1.desktop-recording-title}}",
	"path": "Bookmarks"
}
3 Likes
2

This is awesome! Thanks for sharing!

3

I just received mine yesterday. Ultimately I want all of my transcripts to go into Obsidian. Is there a way to have all transcripts be saved into Obsidian by default (sounds like not), or otherwise to designate an accessible output folder? Or otherwise, is there a way to export transcripts in bulk - or is the only option to individually share/export each transcript separately, if one wants to save/use transcripts outside the Pocket app? Thanks!

1 Like
4

Definitely an area where more development is necessary. As of right now, without reverse engineering, there is no way to do any of these things. API access would enable an Obsidian plugin, but there’s a hundred ways that this integration could look. I’d be curious to here more how you think the ideal workflow would look.

Post on https://feedback.heypocket.com/ and link it here, we can upvote it.

1 Like
5

Thanks for the reply! Yes, I am using a “second brain” type setup with Claude Code parked in my library of Obsidian files, so for me the question is how I can get the transcript data out of the Pocket app and into a shared folder that can be picked up by Obsidian. (Easiest for me would be to export transcript as a .md into the Obsidian iOS app.)

My ideal workflow is that I use my Pocket device to make a dozen or so recordings a day, some of just a few seconds in length (“Need to get back to A about XYZ”), some longer. And the goal would be that as soon as I end each recording, the recording is transcribed and the transcriptions are saved to a shared folder (best of all would be if it could be saved to Obsidian by default - but otherwise something like a synced version of Pocket, or DropBox, iCloud etc.).

Sounds like this functionality is not here at present (i.e., no way to sync outputs through a Cloud/web version of Pocket or control where outputs are saved) – so my best bet in the current environment would be if there was a way to export recordings in bulk rather than one at a time.

It is possible at present to export single conversation transcripts to another app (including Obsidian), but is tedious to do – especially compared to something like superwhisper that will copy a transcript to my clipboard automatically.

Thanks again for the reply!

2 Likes
6

That sounds like an extremely cool set up.

1 Like
7

yeah, my thought is export from the app into an iCloud Drive folder on your phone via the “Save to Files” action in iOS. Then you can setup a watcher/integration on that folder which pushes to Obsidian. Something like Zapier can probably do it, or if you mount that folder locally on a computer which runs 24/7 you can setup something local to act on the folder.

Google AI mode response:

A direct integration to automate a workflow between iCloud Drive and Obsidian via Zapier is not possible because Apple does not offer an official Zapier integration for iCloud Drive. However, you can use workarounds with a third-party app or Obsidian’s own sync options to bridge the connection.

Option 1: Use a supported third-party cloud service

For a Windows and Apple cross-platform solution, you can use a different cloud service that both Zapier and Obsidian officially support.

  1. Use a cloud service with Zapier integration: Set up your Zapier workflow to start with a trigger from a cloud storage service that both Obsidian and Zapier can connect to, such as Dropbox, OneDrive, or Google Drive.

  2. Use the service as your vault location: Store your Obsidian vault in the folder for that cloud service on all your devices. Obsidian notes are just plain files, so you can point your vault to a folder synced by Dropbox or OneDrive.

  3. Use Zapier to send files: Create a Zapier workflow that sends new files from your iCloud Drive to the trigger folder for the other cloud service.

  4. Open your vault in Obsidian: Set up Obsidian on each device to use the vault in your new, cross-platform cloud storage folder.

Option 2: Use an Obsidian community plugin

Another method is to use a community plugin within Obsidian that can connect to other services and be triggered by webhooks, which Zapier can handle.

  1. Install the “Post Webhook” plugin: Go to Obsidian’s Community Plugins and install “Post Webhook”.

  2. Create a Zapier webhook: Set up a Zapier webhook that receives data from the plugin. This will require some advanced configuration.

  3. Use webhooks to send data: Configure the Obsidian plugin to send new note content via a webhook to Zapier. Zapier could then use this to trigger other actions. Note that this is typically a one-way workflow.

  4. Bridge the gap with Shortcuts or Automator: To get files from iCloud, you would still need to use Apple’s Shortcuts (on iOS/iPadOS) or Automator (on macOS) to monitor iCloud Drive and trigger the webhook or send data to Zapier.

Option 3: Ditch Zapier for an Apple-centric workflow

If your workflow is entirely within the Apple ecosystem and you only need to automate moving files, you can use Shortcuts without needing Zapier.

  1. Create a folder action: Use macOS Automator or the Shortcuts app to create a folder action. This can watch your iCloud Drive folder for new files.

  2. Move the new files: Set up the action to copy or move any new files it finds to your Obsidian vault’s folder.

  3. Sync within Obsidian: Since your vault is on iCloud Drive, Obsidian will automatically sync the new note across all your devices.

The most reliable and simple method

For syncing an Obsidian vault across devices, the most simple and officially supported method is to use iCloud Drive directly for your vault location, provided you only use Apple devices. This completely removes the need for a complex Zapier or third-party workflow.

  • Create a new vault in Obsidian and select the option to “Store in iCloud” on your iOS or macOS device.

  • Obsidian will manage the syncing process via iCloud Drive, ensuring your notes are up-to-date across your Apple devices without requiring a complex external automation.

  • For best results, disable “Optimize Mac Storage” in your iCloud settings to prevent files from being offloaded.

8

Thanks for these thoughts! Yes, different ways I could do it – easiest of all is just to export the summaries as .md files and save them directly to the Obsidian app in iOS, which syncs with my desktop (I’m using Obsidian Sync). The friction comes in needing to go in to the Pocket app and export each one individually - takes a lot more touches than my previous status quo of just using superwhisper transcription with my phone and copy/pasting the output into Obsidian each time.

I was hoping Pocket would be able to sync/store things in a place that I could access from outside my phone (or allow for batch exporting) - so at least for now seems like I’m stuck with the old way. But I love the form factor though! So hopefully one day there will be a bit more portability on the data side.

9

@loxoto Seems like some great ideas! I would encourage you to create these on feedback.heypocket.com