Feature request OR question: Automation (shortcuts) on iOS

Features
1

I am aware that most Joplin users are likely Android users.

For me, the power of Joplin would be truly unleashed if I could automate it using iOS shortcuts. Like automatically creating journals, storing data, retrieving data.

Shortcuts is a (not so) powerful macro/scripting language for iOS (and macOS): Shortcuts (Apple) - Wikipedia. It's basically like Tasker under Android, just much much worse.

Nevertheless, some good automation is possible and a huge amount of actions are possible for the integrated Apple Notes app. Like Append to Note, Create Note, Delete Note, Find Notes, Open Note, Pin Notes, Show Notes in Folder, Show Quick Note, Change Notes Settings, Add/Remove Tags from Note, Create/Delete/Open Tag etc.

This way, the Notes app can be used as a powerful data storage but also journals can be created automatically. Some ideas:

  • Whenever I use ApplePay, transaction details are automatically stored
  • Whenever I enter/leave office it is automatically stored
  • I could have an automation to track my baby's food by just asking a basic question and a full record with date/time and location would be automatically created.

Every app can expose "Actions" that are then available as actions from Shortcuts.

Is there any chance this could be added to the iOS version(s)?

Alternatively: Are there already ways to automate Joplin from iOS that I am not aware of?

2

Might be not related, but I have a setup for Windows and iPhone where whatever I dictate to my IPhone using shortcut gets synced to specific notebook on Joplin Desktop and I have also a separate note in that notebook that visualizes all dictated items pending review.

This requires a couple of cents per request to OpenAI for speech-to-text recognition, but it just works.

3

Yeah I think that cannot really replace proper Shortcuts support :-/

Having said that, can you share more details on this? Maybe it can work as a possible hack until (hopefully :blush: ) Shortcut support will come some time.

4

Please check this thread. I've described the design of the solution, but haven't posted the exact implementation steps yet.