Hook integration scripts v.142 now available — Updated Apple Notes, Drafts and Bookends integration

Releases
1

Version 142 of Hook integration’s scripts is now available with updated support for Apple Notes, Drafts, and Bookends apps.

Hook-created Apple Notes now get links you can use on your iPad and iPhone !

The Hook to New Apple Notes command now inserts a hyperlink back to the source context (resource) in which you created the note. For example, if you create a link from the Hook – Find without searching website to a new Apple Note, the note’s name (in Big Sur) will be a hyperlink: Hook – Find without searching — rather than just a plain text label.

This gives you an extra way to navigate from the new note to the source item.

Benefit: This provides a link that you can also use on iPad and iPhone ! (As long as the target of the link is reachable on those devices.)

This is analogous to how Hook to New > OmniFocus already works, where it has proven to be quite popular.

We intend to adapt integration with other apps to behave in this way too – as long as they have sufficient automation. (Caveat emptor: merely UI-scriptable apps, like Ulysses, lack automation and won’t have this feature).

macOS 10.14 and macOS 10.15 lack a feature of Big Sur, so in their cases new notes have a plain text name followed by (on a new line) a hyperlink back to the source.

Hook Pro users who don’t like having a hyperlink in their Apple Notes can customize the integration: Hook > Preferences > Script Editor tab > Notes entry.

See Using Hook with Apple Notes – Hook.

Drafts automation: New Note

Hook to New > Drafts now uses Drafts automation, rather than UI scripting. This requires versions of Drafts that support automation.

Hook to New in Drafts now adds a “Hook” tag to the new drafts. This is configurable.

See Using Hook with Drafts for more information.

We will continue to update Hook’s integration with Drafts to take advantage of its automation. In particular, we aim to rid Hook’s Draft’s Get Address script of UI scripting in favor of Draft’s automation.

Bookends integration

In Bookends the bibliographical reference manager, Hook now also supports Reveal File in Finder even when the URL scheme is bookends://.

See Using Hook with Bookends Reference Manager by Sonny Software – Hook.

Gratitude

We are very grateful to Greg Pierce of Agile Tortoise for continuing to enhance Drafts automation, which is leveraged by Hook.

Thanks also to forum members who discussed this integration.

How to get the updated integration

Hook’s automatic software update (if enabled) automatically updates Hook’s integration scripts without you needing to relaunch Hook. Using Hook’s Check for App Updates and Update Scripts command also updates the scripts, without you needing to relaunch Hook.

We also bundle Hook’s integration scripts with the Hook installer itself, of course. But Hook’s app updates are less frequent than the pure integration updates. We will soon release a version of Hook that includes bug fixes and the latest integrations (Apple Notes and Obsidian).

1 Like
2

Interesting issue with the Drafts integration, @LucB. The assigned tag of “Hook” is a cool idea, just what I wanted for Workspace management. But it appears that Drafts always lowercases tag names. If you assign a draft a “Robert” tag, it converts it to “robert.” This is problematic because in Workspace Management, asking to filter the list by “Hook” results in a list of “hook” tag, of which there are none.

While I’d prefer that Drafts leave capitalization as the user specifies, the simple answer for Hook, it would seem, is to modify the auto-applied tag to a lowercase version in the integration automation. Indeed, when I tried modifying the Hook to New script myself, it did resolve the issue.

– Robert

2 Likes
3

interesting. I thought I had successfully applied the filter. Apparently not. Will do. THanks for letting us know.

1 Like
4

We haven’t been able to reproduce the problem. But we don’t use Drafts ourselves for production purposes (yet), just for testing. So we might be missing something. So we made it lowercase in v. 143 of the integration scripts, which we released this afternoon (2020-12-20 PT).