This Week's Sponsor:

Incogni

Put an End to Spam, Scams, and Robocalls on Your iPhone

Posts tagged with "drafts"

Pocket Adds Drafts Sharing→

After an update that added support for Quotebook, Pocket for iOS has been updated today to let users send text to Agile Tortoise’s Drafts.

In the current implementation, the app will send an article’s title and shortened URL if no text is selected; if there is a text selection, Pocket will send quoted text and shortened URL to Drafts. I like it, but I wish there was a setting to send the shared link with its original, non-shortened URL.

I’m very glad Pocket added Drafts integration. In this way, you can tweak my Evernote workflows to, say, append bits of text to a single note.

Permalink

Add Multiple OmniFocus Actions at Once Using Drafts 3.0→

When editing my Drafts 3.0 review last night, I removed this sentence from the Reminders section:

“Again, I don’t use this functionality, but it’ll be interesting to see something like this being tweaked to work with Drafts and Reminders”

Sid O’Neill figured it out right away:

Drafts just updated today to version 3.0. There are a whack of new features but one that I’m most interested in is the new “list in Reminders” action. It makes it easy to add multiple actions to Omnifocus without requiring Pythonista.

I forgot Daniel Jalkut had a script to monitor Reminders and add todos to OmniFocus for Mac. If you’re like me, you know you’ll try to make this work with a Mac server and modified default sync times.

Permalink

Drafts 3 Review: Better iOS Automation and Workflows

Drafts3

Drafts3

In just a little more than a year, Agile Tortoise’s Drafts has gone from being a quick notepad for small bits of text to a full-featured solution for launching apps, using web services, and chaining multiple apps together – always with a focus on text. With version 2.5, released in January, developer Greg Pierce expanded upon Drafts’ existing support for URL schemes to let users build their own actions and share them with others; in the process, he also updated Drafts to handle advanced operations such as customizable Dropbox write access, strftime timestamps, and deeper x-callback-url support.

Drafts 3.0, released today, is a major update that refines several aspects of version 2.5 and brings powerful new features such as Evernote and Message actions, better action and draft management, tighter Reminders integration, and a way to backup and restore entire sets of actions.

I have been testing Drafts 3.0 for the past month, and, even more than Drafts 2.5, it has become an essential part of my daily workflow.

Read more

Linked Posts with Drafts and Poster

When we announced a new format for linked posts last week, I hadn’t set up a proper workflow to create linked posts on the iPhone and iPad. Driven by annoyance, I put together a Drafts action and a bookmarklet to help me post links to WordPress with or without additional text and quotes.

Our linked posts use a custom field to link back to the original source and format the clickable titles that you see on the site. Tom Witkin’s Poster is my default app to publish posts on MacStories from iOS, and, fortunately, it has support for calling and assigning values to custom fields from the URL scheme. On the other hand, Agile Tortoise’s Drafts, my favorite app to chain multiple actions together, can launch custom URL actions differentiating between the first line of a note and everything else after it. That seemed like a good opportunity to separate my source URL from any possible text I wanted to add to a linked post. Read more

Send Multiple Tasks To OmniFocus Mail Drop At Once With Drafts and Pythonista→

Send Multiple Tasks To OmniFocus Mail Drop At Once With Drafts and Pythonista

Nice workflow by Nathan Henrie to send multiple tasks to OmniFocus at once using Mail Drop, Drafts, and Pythonista:

I’ve also recently started playing with Pythonista, and I came across a Python script written by the dev himself that creates a little SMTP server and sends email directly from Pythonista. Between the two, I found it pretty easy — even for a beginner like me — to put together a combined Drafts / Pythonista workflow that makes for a superior way to import a bunch of tasks to OmniFocus at once (aka “brain dump”).

The Python part is based on the same script I covered in November to send emails through Pythonista; Nathan added a clever Drafts integration by splitting multiple lines (from the draft) into separate email messages sent to your Mail Drop address. Make sure to check out his video to see the workflow in action; I have started using it myself and I like how fast tasks go from Drafts onto OmniFocus via email (I have configured the script with my Gmail address using 2-step verification).

I have become a big fan of OmniFocus Mail Drop. It’s been extremely fast and reliable in my experience, and it works well with Drafts’ email actions.

Permalink

Create and Share Evernote Notes With Pythonista On iOS

I use Evernote on a daily basis, but there’s no easy and quick way to create new notes and receive their shared URLs on iOS. While I tend to prefer plain text files, Evernote notes are quite useful when I need to share rich text (containing formatting and inline images) with someone else. Sharing via the official Evernote app takes too long[1], and I don’t like the UI of other Evernote clients.

Yesterday, Pythonista developer Ole Zorn posted an installer script for the Python Evernote SDK. By putting together all the necessary dependencies, he created an installer script that will create an “evernote-sdk” sub-folder in Pythonista 1.3; with that, you’ll be able to access the entire Evernote API to create and manage notes – all while taking advantage of the uniqe iOS-related features of Pythonista.

Inspired by Ole’s demoes and the snippets posted by Brett Kelly in the past weeks, I created a script that does exactly what I need: it lets me enter text to save it in an Evernote note that will be shared publicly. If triggered by an app like Drafts or Launch Center Pro, the script will take the text sent by those apps. If formatted in Markdown, the text will be converted to HTML before saving it to Evernote. Read more

Chaining Tweetbot, Pythonista, Drafts, and iMessage for URLs

DraftsMessages

DraftsMessages

Last night, Tweetbot for iOS was updated with support for the Twitter 1.1 API, which, among various requirements, includes the need of linking a tweet’s timestamp – the date and time when it was sent – to its unique URL on twitter.com. In Tweetbot, you can now open the tweet detail view and tap on the timestamp to automatically open the Twitter website in your default browser; in terms of interaction, I like this change because it lets me open tweets in Google Chrome with just one tap.

In thinking about the update last night, I realized that:

  • My team and I use iMessage for daily communication;
  • The majority of URLs we share are Twitter URLs;
  • We all use Tweetbot on iOS and OS X;
  • Easier browser access means easier bookmarklet triggering;
  • Drafts can access iMessage.

And I concluded that:

  • I could chain every piece of the puzzle together;
  • Hopefully somebody else will find it useful and adapt the workflow to other similar scenarios.

Therefore, I created a browser bookmarklet, a Python script, and a Drafts action to automate the entire process and demonstrate how you can convert Twitter URLs to tweetbot:// URLs and send text from Pythonista to Drafts.

As usual, I am posting the following workflow as a proof of concept that you can modify and adapt to your needs. For instance, you can change the action that is triggered in Drafts, the x-success parameter that will be triggered, or the way Twitter links are converted to Tweetbot-specific URLs.

Read more

Alex Guyot Chains 5 Apps with Drafts→

Alex Guyot Chains 5 Apps with Drafts

As I expected, people have started experimenting with chaining apps and services using Drafts, and Alex Guyot quickly beat me in chaining 5 apps. From his explanation of the workflow:

Follow the bookmark in Chrome and it will take the URL of the webpage you are on, send it to Drafts as a draft, upload it to Dropbox, send it to Due (where you choose a reminder time for it to remind you), take you back to Drafts, send you to Instapaper (Where you choose to save the link to Instapaper), then send you back to Chrome.

He also posted a quick video showing the workflow in action on his iPad. I like how, unlike me, he chained each action as an x-success parameter of the previous one.

As I’ve argued on multiple occasions here on the site, URL schemes are certainly a stopgap solution to a problem – better inter-app communication on iOS – that I wish Apple will tackle in the near future. However, that doesn’t mean people can’t get real work done with URL schemes and apps today. Looking ahead, I can only imagine new possibilities of iOS automation based on URL schemes that, however, abstract the need of manually building URLs from the end user’s workflow – using a more Automator-like interface to visually represent actions. And, who knows, perhaps in a future version of iOS “switching” between apps won’t even be required anymore, as “parts” of other apps will be linked to each other using something like XPC.

Permalink

Chaining Multiple Apps Together with Drafts

A few weeks ago, I took a look at the automation possibilities opened by Drafts, Agile Tortoise’s multi-purpose text app. In the article, I mentioned how a bug prevented Drafts from “linking to itself” more than once:

Therefore, my idea for cross-posting was: I can link to Drafts itself, and if the first action is successful, I can link to Drafts itself again. Essentially, I wanted to leverage the built-in App.net and Twitter actions to avoid the use of any third-party app. Unfortunately, there’s a bug in the current version of Drafts that doesn’t make that kind of action work.

With an update to Drafts released yesterday, Greg Pierce has brought various improvements to the app, including support for more customizable timestamps and dates using strftime, date and time tags for file names and URL actions, and a new way to encode strings with curly brackets.

Seemingly minor, the option to more easily URL encode strings is actually a very welcome addition: like in the latest Mr. Reader, instead of forcing the user to encode a URL into a longer string, you can simply put a URL inside {{ }} and let Drafts take care of encoding it. It means I can now experiment with building more complex workflows that contain actions for more external apps and, more importantly, for “sequential” tasks in Drafts itself. Easier encoding means we construct URLs that will tell Drafts “do this, and then do that” in a single workflow.

Those who follow me on Twitter know that I’ve been trying since yesterday to see how many apps I could chain together in a workflow, mainly out of curiosity and as a “proof” of concept. First, I tweeted about a Mr. Reader -> Drafts -> Poster workflow that would take selected text from an article, convert its Markdown to HTML, and then send it to Poster; the workflow consisted of three apps chained together, but I knew I could try to accomplish something a bit more ambitious. I kept on experimenting with Drafts URLs, and eventually I managed to build a single workflow with 3 apps and 4 different tasks involved. I’m posting it here for two reasons: a) I believe it’s a quite useful workflow; and b) it can serve as an example of what Drafts can do when you understand how to properly link multiple apps together. Read more