I have been using Things 3 for a little while now as my main Task Manager, and I think this is sticking for me. I love being able to plan my days with their default sections, and the power it has in both organization and automation is something I cherish every time I use it.
One thing that I missed when I switched over the Things from Omnifocus 3 is the availability of project templates for Omnifocus. I had a ton of Taskpaper templates for common projects I would create. Things like podcast episodes, blog posts, and other regular projects were easy to create in Omnifocus with the tap of a button.
Things 3 didn’t have anything like that until they updated to version 3.4 allowing for x-callback-url schemes. This feature has been around for a bit now but I never got around to using it as a means to solve my problems with project templates. That is, until I came across the Drafts 5 action Send to Things.
What it is
Send to Things by user @eichtyler is something that solved my problems with project templates in Cultured Code’s task manager. It made my life easy to just write out my lists and then make it the way I wanted.
The way it works is by using a custom syntax to differentiate items in your list from to-do items to deadlines, headings, etc. so when you are finally ready to send it over to Things 3 it is formatted the way you want.
One tool I loved in addition to this actions was the Send to Things Syntax action by Tim Nahumck. This allows you to tap on the action to prompt a pop-up showing you all the syntax built into the Send to Things action. It came in handy a number of times for me as I was getting acclimated to writing out my projects correctly. Here’s what Nahumck’s action shows when you open it:
Here is the syntax for Send to Things: # New Project @ Existing Project > Note #tag ## Heading :when date/time !deadline Todo - checklist item
There are a number of items in here that I’d like to go over with this to help you to understand the power of what you can do with this action.
How it Works
Learning new syntax can be difficult and time consuming, but a large amount of these items are using Markdown syntax in a way where the script in this Drafts Action will parse out things based on the characters before it.
One impressive thing about this action is that depending on whether you want it in a project or just a list of items to your inbox you can differentiate that by whether or not you use a Project heading.
I have broken it down into these two scenarios to help understand the differences.
When you are wanting to either make a template or realize when making a list of actions to send to things that it is better off as a project all you need to do is make a Project header. This is just like a Heading in Markdown with a single “#” character followed by a space. Anything after that space is what the project name will be called. In this case I copied the template from the Drafts Action Directory so the project is called “Project 1.”
You may notice in the image that there is also a “Project 2” heading, which is exactly what you may think. If you use a new heading you are able to make another project and all the items below it will then be put in the second project as It is under the second heading.
If you want to add a note to the project that is a simple quote syntax in markdown with a “>” character followed by a space. As you can see in the template if you make a new line with the syntax that new line carries over to the notes in the Project.
When you want to use either a start date or a deadline the syntax on these aren’t just simple symbols. These are arguably the most deviant from traditional Markdown syntax, making it a little more difficult to understand.
If you want to use a start date, meaning that until this date your project will be in the Upcoming area, you use the syntax “:when” followed by a space. From there you can use natural language input such as “tomorrow” in this template, making it much easier to differentiate when these items are taking place over the date picker. You can also use things like “next Monday” as well when writing your dates.
The same goes for the deadline, only the syntax necessary to make that work is “!deadline” followed by a space. Just input what ever date you want after that and the deadline will carry over when you send it to Things 3.
Finally, if you want to add a task item you just need to make a new line and enter in the name of the task. There are no special characters or syntax necessary for task items. Which is the smart move as you can add syntax in later if you so choose, but the main point of this action is to quickly lay out the items you want to send to Things, and if you needed a special character or something to mark it as a task item your efficiency would drop dramatically. In this template you can see the task items named “Todo 1” “Todo 2” and so on.
Now that you have your projects all set and ready to go you can now send it to Things via the Drafts action. This is what you get when you use the default template on the Drafts Action for sending as a new project.
Items into Inbox
If you aren’t looking to make a new project, and instead just want to send something to Things Inbox to organize later it is even easier.
As you can see the syntax used is the same, the only addition is comments for to-do items. As you can see in the template, they are solely for organizing your thoughts when writing them and will be ignored when you send it to Things. It is a great way to put everything in your mind on to the screen and figure it out once your head is emptied and you have everything laid out. It is also great if you plan to keep this note as a template for future items.
You will also see the absence of Project headings, which brings a good point that you can actually combine these two templates and have the items above the first project heading go to the Inbox and the rest go to their respective Projects. Once you have everything in there that you want sent to Things you are ready to run the action. This is what you will see with the default template on the Drafts Action for inbox items.
Problems with it
One thing that I can not seem to get to work properly is the use of tags. I have tried existing tags and new tags in these templates but none of them seem to follow into Things. I am not sure if this is me doing something wrong or something that needs to change in the script. Either way, if you have a fix for this let me know either via email or on Twitter.
All in all this action has made things like projects, templates, and all around task management much easier for me. I love Things 3 and their addition to a Desktop-Class Productivity for iPad in version 3.6 has made inputting tasks easier than ever, but something about being able to input my task whilst writing in Drafts makes things really gel. I no longer have to switch modes, and instead just need to use this syntax in a new note and with a simple swipe and tap I can send it to Things 3 and continue with the work I was doing previous.
There is something to be said about not having to open a task management app every time you want to add something to it. It allows for you to stay focused on the task at hand and avoid being distracted with anything that may pop out at you in your task list.
This action allows for that and makes adding the important meta-data you want a cinch. Try this out today, and if you want something to help you remember the syntax get Nahumck’s supplementary action as well. Additionally you can read his review of Drafts 5 on MacStories as well if you aren’t sure what Drafts 5 is and what to learn more.
Give these actions a shot and see if this can solve any of your problems with task management in Things 3, I know It did for me.