All Collections
Task Integrations
Google Tasks Integration
Use natural language in the Google Task integration
Use natural language in the Google Task integration
You can use natural language expressions to create Reclaim Tasks via Google Tasks.
Henry Shapiro avatar
Written by Henry Shapiro
Updated over a week ago

The Google Task integration supports natural language to create Tasks. In addition to being a fast way to add Tasks to Reclaim, one benefit of using natural language is that you can express options for the Task that are not natively supported by Google Tasks.

The general syntax for Google Tasks is as follows, and should be entered into the Title field of Google Tasks: TITLE ([DURATION] [DUE_DATE] [NOT_BEFORE] [TYPE])

The TITLE is required, and the additional text in the parenthesis is optional fine-tuning of the Task. Refer to Tasks overview for a description of each field.

Once synced, Reclaim will automatically strip out other parameters besides the title, so your calendar events and Google Tasks won't have a lot of extra words on them when they're placed on your calendar.

Examples

  • To create a work task for "Build slide deck" for four hours by next Friday, you would enter Build slide deck (for 4h due next Friday)

  • To create a personal task for "Mow the lawn" for one hour (default) by this Sunday, you would type Mow the lawn (type personal due sunday)

  • To create a work task for "Get back to CEO" for 30m by September 21st, not to be started before September 15th, you would type Get back to CEO (for 30m due sept 21 not before sept 15)


Updating existing Tasks

While the TITLE and DUE DATE can be directly edited using Google Tasks, you have to edit the title using natural language to update the DURATION, TYPE, or NOT BEFORE date because those features do not exist in Google Tasks.

For example, if you decide you need two hours instead of the default one hour for a Task, add (for 2h) to the end of the title. In about one minute, you'll see that text disappear and your schedule adjusted accordingly.


Related articles

Did this answer your question?