By now, you're probably already aware that you can create a long chain of custom URL actions in Drafts that involve other apps that support x-callback-url. Theoretically, you can create these chains for as long as they fit the purpose. Nevertheless, when you start to involve three or more actions, you might be wondering which action to begin with.
Here's a sample workflow that some of us may be doing quite frequently: sharing an article that we find interesting to as many outlets as possible.
- We may tweet about it, and
- We may post it on App.net, and
- We may save it to Instapaper because it's at least three pages long, and
- We may want to return to Chrome to continue reading, or use Chrome to return to Tweetbot or Riposte.
We know it's possible to do all of the above, especially since all of the apps involved here support x-callback-url. Yet, when you start coding your actions, you might be wondering where to start. Based on my experience in writing many long chains of actions in Drafts, here are some guidelines that you can use when designing your chain.