Thank you for showing me this, I hadn’t seen it before since iOS buries new apps in the share sheet. This will be very useful and gets me almost everything I need, besides one use case I’ll describe below.
Sure, since I am familiar with OmniFocus I will use their implementation as an example.
Drafts replaces the content in between the double brackets, then opens the resulting URL. https://actions.getdrafts.com/a/1RI
OmniFocus has a URL at omnifocus:///add that takes parameters passed to it to create a new task in the Inbox using the contents of those variables that Drafts filled in. Your share sheet accomplishes this just fine, but I hope it explains the basic functionality that a URL scheme can provide.
My specific use case is to send each line typed as individual Inbox items. This is very useful for doing a brain dump; just type it all out line by line, then use this URL scheme to create an Inbox item out of each line. Here’s a Drafts script to build an array of each line to be pushed to OmniFocus: https://actions.getdrafts.com/a/1DD
And OmniFocus has a URL at
omnifocus:///paste that takes the array, and creates new Inbox items out of each value. This, specifically, is the piece I am requesting that you consider implementing.
I am not a developer so please take my advice with a grain of salt, but I think the simplest implementation of this would be a URL scheme like
everdo:///import?content=. You could decide on a known line-break character, so all content up to that character would be one Inbox item and repeat until there’s no more content.
Curious to hear your thoughts on this. The ability to add a new Inbox item per line of text is pretty crucial to my workflow and is the one thing I can’t seem to figure out with Everdo. I am, of course, open to other ideas to accomplish this as well.
With a URL scheme in place on the macos app, I imagine one could setup their own email account in Mail.app with a rule like “from me to me” or “contains certain character in subject line” that appends the mail body to
everdo:///import?content= and opens the resulting URL.
You make a very good point that the email would either have to be in plain text format, or some sort of parsing would need to happen before the result is opened.