Hello All!
I’m looking for guidance—or proposing a feature—around a Hookmark workflow that improves cross-platform and multi-user interoperability, particularly when working with Daylite and Dropbox.
✱ The goal
When creating a Hookmark link to a file, I’d like Hookmark (or a script) to generate and paste a single, structured block of text that includes multiple ways to access the same file:
-
Native Hookmark link (ideal on macOS with Hookmark installed)
-
Markdown link using the file title as anchor text
-
Direct Dropbox URL, clearly labeled
✱ Our setup (important context)
-
We use Dropbox (not iCloud Drive) to sync Hookmark link files in a shared, multi-user firm environment.
-
All users have access to the same shared Dropbox folder containing the Hookmark links, so links must remain stable across users and devices.
✱ Formatting constraints
Our output/paste targets vary:
-
Some destinations support rich text or Markdown (e.g., certain Daylite notes or emails).
-
Others allow plain text only, especially in mobile or integration contexts.
✱ Ideally, the output would be dynamic/contextual, but at a minimum should:
-
Look very organized when the output allows for Rich Text
-
Be clean and readable as plain text if necessary, and
-
Enhance gracefully when rich text or Markdown is supported.
✱ Example output
-
File: Document Title
-
Hookmark: hook://…
-
Markdown: [Document Title](…)
-
Dropbox: -https:// Dropbox,etc
-
Even in plain-text-only fields, this remains understandable and usable.
✱ Questions / request
-
Is this achievable today via a Hookmark script or integration?
-
Are there recommended patterns for:
-
Extracting the Hookmark link
-
Extracting the contextual Markdown link
-
Extracting the underlying Dropbox URL
-
Emitting all of the above as a single, paste-ready block that works in both rich-text and plain-text contexts?
-
If not currently possible, I’d like to suggest this as a feature request: a built-in action (or scriptable hook) that outputs multiple link representations for a single file, optimized for shared, cross-platform workflows.
This would be a huge help for our particular workflow and it could significantly improve reliability when linking files inside CRMs, emails, and other collaborative systems.
Thanks!
Austin Elliott